Planning your migration
7
When running in the server configuration, ColdFusion MX uses the built-in web server,
as follows:
•
The ColdFusion MX Administrator is located under the
cf_root
/wwwroot directory in a
directory named CFIDE; CFM pages are located within the
cf_root
/wwwroot directory.
•
To access pages through the built-in web server, specify port 8500 in the URL, as the following
example shows:
http://localhost:8500/CFIDE/administrator/index.cfm
Tip:
If you upgrade to ColdFusion MX 7 and are already using the built-in web server, the installer
selects a different port number (typically 8501).
When running ColdFusion MX 7 in the multiserver configuration, ColdFusion MX uses the
built-in web server, as follows:
•
The ColdFusion MX Administrator is located under the
jrun_root
/servers/coldfusion/cfusion-
ear/cfusion-war directory in a directory named CFIDE; CFM pages are located within the
jrun_root
/servers/coldfusion/cfusion-ear/cfusion-war directory.
•
To access pages through the built-in web server, specify port 8300 in the URL, as the following
example shows:
http://localhost:8300/CFIDE/administrator/index.cfm
When running in the J2EE configuration, you use the web server capabilities of the underlying
J2EE application server.
If you are using the built-in web server, you must switch to the web server connector before
moving to production. You do this by running the Web Server Configuration Tool, as explained
in
Installing and Using ColdFusion MX
and
Configuring and Administering ColdFusion MX
.
Migration strategy using external web server
If your site has a highly controlled environment with separate development, testing, staging, and
production servers, you can migrate to ColdFusion MX on a testing server before moving to
production. Adapt the following suggested steps to fit your needs:
1.
Study the ColdFusion MX Migration section of the Macromedia website
(
www.macromedia.com/go/cfmxmigration
) and this migration guide to anticipate the
compatibility issues that might affect your system.
2.
Copy your existing ColdFusion 5 application to a test computer that contains a web server.
3.
Redefine data sources to access a test database. You should not run tests against a production
database.
4.
Ensure that your ColdFusion 5 application is functioning properly on the test computer before
upgrading it to ColdFusion MX.