[thelist] Moving from NT to Unix
Jeff
jeff at lists.evolt.org
Sat Sep 2 04:45:36 CDT 2000
chris,
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: Christopher Ditty <CDitty at email.usps.gov>
:
: We are moving some production sites from a
: Windows NT machine to a Unix machine soon.
:
: Can anyone suggest some things that they have noticed
: when do this same thing? These systems are using
: Cold Fusion.
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
not necessarily in order.
things that will be affected irregardless of what platform you're coming
from and what platform you're going to.
1) local paths in files that are absolute
and will no longer be at the same path -
ie d:\wwwroot\yoursite\blah/etc.cfm is now
/usr/local/blah/etc.cfm
2) registering the necessary datasources
3) mappings will need to be registered.
4) whether or not you were running the site on cf
enterprise, utilized some of it's features in your
site, and then whether or not the server you're
moving to not only supports cf enterprise, but
also supports those same features.
5) dependence on other software (macromedia generator,
active pdf, etc) and whether or not it's supported on the
platform you're moving to.
6) making sure the new server has index.cfm set up as
one of the default files.
things that will be affected by going from nt to unix
1) filename case - everything must match. suddenly
all lowercase makes a ton of sense.
2) your application.cfm filename must begin with
A (capital a - Application.cfm).
3) is the database package you're using on nt
supported on the unix server
4) if it is not supported you'll have to construct a
migration path for the data.
5) when migrating data you will potentially run into
issues with column names using reserved words,
incompatible datatypes, incompatible sql,
incompatible queries, incompatible style of relational
integrity, etc.
6) the flavor of unix - solaris, linux, hp-ux.
7) any cfx tags you use on the site will probably not run
on the unix server. they may not be able to be ported.
8) reliance on verity and it's support on unix. this includes
cfcollection, cfsearch, and
9) will need to use an additional attribute (mode) that is
required on unix.
10) learning a whole new set of error messages and what they
mean, especially the ones related to interaction with the
database.
11) use of COM and CORBA via cfobject and their support on unix
12) use of cfreport and the availability of support for that tag via
available of the crystal reports server on unix
13) use of the cfregistry tag.
i'm sure there's more, but that's what i could think of from my experiences
as well as going through the list of cf tags in cfwack.
good luck,
.jeff
name://jeff.howden
game://web.development
http://www.evolt.org/
mailto:jeff at members.evolt.org
14)
More information about the thelist
mailing list