User Guide

ColdFusion MX 7 J2EE deployment and configuration 41
c In cfusion-ear, make a new directory named cfusion-war.
md cfusion-war (mkdir cfusion-war on UNIX)
d Change to the cfusion-war directory and expand the cfusion.war file with the jar
command:
cd cfusion-war
java_root/bin/jar -xvf ../cfusion.war
This expands the cfusion.war file.
e (If rds.war exists) Go up one level to cfusion-ear, make a new directory named rds-war.
cd ..
md rds-war (mkdir rds-war on UNIX)
f (If rds.war exists) Change to the rds-war directory and expand rds.war with the jar
command:
cd rds-war
java_root/bin/jar -xvf ../rds.war
This expands rds.war.
g Go up one level to the cfusion-ear file, and delete the cfusion.war and rds.war files:
cd ..
del cfusion.war (rm cfusion.war on UNIX)
del rds.war (rm rds.war on UNIX)
h Open the cfusion-ear/META-INF/application.xml file in a text editor.
i Change the web-uri element from cfusion.war to cfusion-war (or the name of the directory
that contains the expanded cfusion.war file). Change the
web-uri element for rds.war to
rds-war. A directory name in the
web-uri element cannot contain a dot.
j Save the application.xml file.
3. Deploy ColdFusion MX 7 by copying the cfusion-ear directory structure to the jrun_root/
servers/servername directory. If auto deploy is enabled, JRun 4 either deploys the application
immediately (if the JRun server is running), or when you start the JRun server.
4. Review the server log (jrun_root/logs/servername-event.log) to ensure that ColdFusion MX 7
deployed successfully.
Expanding and deploying WAR files on JRun 4
When you deploy ColdFusion MX 7 as a web application on an existing JRun server, you expand
the cfusion.war file, deploy it, and optionally modify the context root. For complete information
on deploying ColdFusion MX 7 on JRun 4 as a WAR file, see www.macromedia.com/go/
cfmx7_j2eecert.