Table of Contents
Advertisement
Before planning your migration, make sure that you understand the ColdFusion MX
configuration options:
Server configuration
J2EE server. This configuration most closely resembles the ColdFusion MX base release and other
releases prior to ColdFusion MX, such as ColdFusion 5 and ColdFusion 4.5. This was formerly
known as the stand-alone configuration.
Multiserver configuration (Enterprise Edition only)
ColdFusion MX 7 in a separate JRun server instance. This configuration supports server instance
creation and ColdFusion deployment in the ColdFusion MX Administrator and lets you manage
ColdFusion MX 7 deployments on multiple JRun servers.
J2EE configuration (Enterprise Edition only)
application running on a Java 2 Enterprise Edition (J2EE) application server, either using the
bundled license of JRun or using a third-party J2EE server, such as IBM WebSphere or BEA
WebLogic. When you use the J2EE configuration, you can deploy ColdFusion MX 7 multiple
times on a single computer.
Planning your migration
To facilitate the migration process, Macromedia recommends that you develop a migration
strategy. Because every application is different, you must tailor your own migration strategy to
meet your environment's needs. This section contains two possible migration strategies, following
a discussion of web server differences in ColdFusion MX.
Web server considerations
ColdFusion 5 has a simple relationship with the web server:
•
To install ColdFusion, you must have a web server (such as IIS, iPlanet, or Apache) running on
the same computer as ColdFusion.
•
The ColdFusion Administrator is located beneath the web root in a directory named CFIDE;
CFM pages are located either within the web root or in a virtual directory that is accessible to
the web server.
•
The ColdFusion stub, a web-server specific module that is always configured as part of a
ColdFusion 5 installation, uses extension mappings to route CFM pages to the ColdFusion
application server.
ColdFusion MX provides a web server connector (similar to the ColdFusion stub), which also
uses extension mappings to route CFM pages to ColdFusion MX. However, because both the
ColdFusion stub and the ColdFusion MX web server connector process CFM files, you cannot
configure a web server to handle both ColdFusion 5 and ColdFusion MX.
If you must use a ColdFusion 5 application on the same computer that contains ColdFusion MX,
you can access ColdFusion MX pages through the built-in web server. The built-in web server is
an all-Java, HTTP 1.0 server that is not intended for use in a production environment. However,
the built-in web server is particularly useful when ColdFusion 5 and ColdFusion MX
applications must co-exist on the same computer until you complete the migration process.
6
Chapter 1: Migrating Applications from ColdFusion 5
Lets you install one instance of ColdFusion MX 7 with an embedded
Installs JRun and automatically deploys
Lets you deploy ColdFusion MX 7 as a Java
Advertisement
Table of Contents
