Table of Contents
Advertisement
•
If you don't run the Configuration Wizard, you can run it later by performing the following
steps:
Close the ColdFusion MX Administrator.
a
Open cf_root\WEB-INF\cfusion\lib\adminconfig.xml in a text editor, change
b
runmxmigrationwizard
Restart the ColdFusion MX Administrator.
c
ColdFusion MX J2EE deployment and configuration
The J2EE specification allows application servers to handle compressed and expanded
deployments in a server-dependent manner; each application server has its own deployment and
configuration mechanism, as shown in the following table:
Application server
JRun 4
IBM WebSphere
BEA WebLogic
SunONE Application
Server 7
For basic deployment information, see your J2EE application server documentation. ColdFusion
MX deployment instructions differ for each J2EE application server. For up-to-date information
on deploying ColdFusion MX on a variety of J2EE application servers, see
www.macromedia.com/go/cfmxj2ee-cert.
For more information, see
Deployment
The instructions at www.macromedia.com/go/cfmxj2ee-cert provide detailed, application-server-
specific ColdFusion MX deployment instructions. Depending on your application server, the
instructions describe deployment of an EAR file or WAR files in either a compressed archive or an
expanded directory structure. When deploying ColdFusion MX on an existing version of JRun 4,
you must expand the EAR file or WAR files manually before deployment.
The following procedures describe EAR and WAR deployment on an existing version of JRun 4.
Tip: The instructions for expanding cfusion.ear also apply when deploying ColdFusion MX on BEA
WebLogic.
Expanding and deploying an EAR file on JRun 4
When deploying ColdFusion MX as an enterprise application on an existing JRun server, you
must expand the EAR and the WARs it contains before deployment.
Note: If you are already using the default-ear application and can't delete it, you must use a context
root other than / for cfusion-ear. If you specified / when installing ColdFusion MX 6.1, you can change
it by opening the cfusion-ear/META-INF/application.xml file in a text editor and modifying the
context-root element. After deploying cfusion-ear, you access ColdFusion pages by specifying
hostname:portnumber
http://
and
runsetupwizard
Deployment mechanism
Auto-deploy to server root
IBM WebSphere Administrative
Console
WebLogic Administration Console
asadmin utility
"Deployment" on page 43
contextroot
pagename
/
/
.cfm.
ColdFusion MX J2EE deployment and configuration
to true, as necessary, and save the file.
Expanded or compressed
deployment
Expanded
Compressed
Expanded
Compressed
and
"Configuration" on page
45.
43
Advertisement
Table of Contents
