1. Open a Terminal window (Applications/Utilities/Terminal).
2. Use the cd command to navigate to the directory where you downloaded the ColdFusion MX installer.
3. Use either of the following commands to run the coldfusion-j2ee-java.jar installer. You might have to prefix the java command with the path (or alias) to your JDK bin directory (for example, /Library/Java/Home/bin/java or /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Commands/java, although you can also specify /usr/java).
   • Graphical installation: java -jar coldfusion-j2ee-java.jar -i gui
   • Text-mode installation: java -jar coldfusion-j2ee-java.jar -i console

Answer the questions and select an install directory. Make a note of this directory; you will need to know it later. When prompted to select EAR file or WAR file, select WAR file.

Note: The default target for the ColdFusion MX installer is the /opt directory, which is not visible through the Macintosh Finder. You might want to change the installation directory to one that is visible through Finder; for example, /Applications/CFMXJ2ee.

If the JRun server to which you are deploying ColdFusion MX is running, stop it. You can stop a JRun server through the JRun Launcher, the JRun Management Console (JMC), or the command line. In most cases, you should use the JRun Launcher, which you run by opening a Terminal window, navigating to the jrun_root/bin directory, and typing ./jrun.

If you haven't done so already, open a Terminal window (Applications/Utilities/Terminal), navigate to the cfusion directory, and use the jar utility to uncompress the cfusion.war file:

cd jrun_root/jrun4/servers/server_name/cfusion
jar -xvf cfmx_install_directory/cfusion.war

Note: In these instructions, replace jrun_root with the directory in which you installed JRun 4; for example, /Applications/jrun4. Replace server_name with the name of the server to which you are deploying ColdFusion MX; for example, if you installed ColdFusion MX in the default JRun server, specify default.

Navigate to the CFIDE directory and use the jar utility to uncompress the rds.war file:

cd jrun_root/jrun4/servers/server_name/CFIDE (or cd ../CFIDE)
jar -xvf cfmx_install_directory/rds.war

Start the ColdFusion MX Administrator by opening a browser and going to http://hostname:portnumber/cfusion/CFIDE/administrator (for example, http://127.0.0.1:8100/cfusion/CFIDE/administrator). The startup wizard executes the first time you open the Administrator. For more information on the startup wizard, see the Installing and Using ColdFusion MX for J2EE book.

Note: The startup wizard is a pop-up window. To make sure that the wizard appears, disable any software options that prevent your web browser from displaying pop-up windows.

• hostname - The machine name, IP address, localhost, or 127.0.0.1.
• portnumber - The port number of the JRun web server for the JRun server running ColdFusion MX. For example, the default JRun server's web server uses port 8100. If you are not using the default JRun server, you can determine the web server port used by the JRun server by opening the JMC and viewing the home page.
• filename - The directory path and file to display. The path is relative to the cfusion directory.

For example, to display a CFM file located at /Applications/jrun4/servers/default/cfusion/eisapp/index.cfm, you could specify the URL as http://127.0.0.1:8100/cfusion/eisapp/index.cfm.

1. Open a Terminal window (Applications/Utilities/Terminal).
2. Use the cd command to navigate to the directory where you downloaded the ColdFusion MX installer.
3. Use either of the following commands to run the coldfusion-j2ee-java.jar installer. You might have to prefix the java command with the path (or alias) to your JDK bin directory (for example, /Library/Java/Home/bin/java or /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Commands/java, although you can also specify /usr/java).
   • Graphical installation: java -jar coldfusion-j2ee-java.jar -i gui
   • Text-mode installation: java -jar coldfusion-j2ee-java.jar -i console

Answer the questions and select an install directory. Make a note of this directory; you will need to know it later. When prompted to select EAR file or WAR file, select WAR file.

Note: The default target for the ColdFusion MX installer is the /opt directory, which is not visible through the Macintosh Finder. You might want to change the installation directory to one that is visible through Finder; for example, /Applications/CFMXJ2ee.

Start Tomcat server. Tomcat automatically detects the presence of cfusion.war and CFIDE.war, autodeploys them, and creates expanded cfusion and CFIDE subdirectories. The expanded cfusion directory is the web application root (also called context root) for ColdFusion pages; for example, if you are installing ColdFusion MX in the default JRun server, the directory might be /Applications/Jakarta-4.1.18/webapps/cfusion. The expanded CFIDE directory is the web application root for RDS.

For instructions on starting the server, see your Tomcat documentation. You typically start Tomcat by opening a Terminal window, navigating to the tomcat_root/bin directory, and typing the ./startup command.

Stop Tomcat server.

Rename tomcat_root/webapps/cfusion/WEB-INF/cfusion/lib/tools.jar to something else (for example, tools.old).

Create a shell script to establish the JVM options used when starting up Tomcat. Name this file setenv.sh and save it in the tomcat_root/bin directory.

At Tomcat startup, the catalina.sh file automatically calls this file. This file must set JVM options to enable Sandbox Security, cfchart, and CORBA support (CORBA is optional).

# Establish variables. May differ on your installation.
# JAVA_HOME specifies the Java JDK root directory.
# Macintosh OS X maintains a number of aliases for this directory.
JAVA_HOME="/Library/Java/Home"
# CF_HOME specifies the directory to which ColdFusion MX is deployed.
CF_HOME="/Applications/Tomcat/webapps/cfusion"
CF_WEB_INF=$CF_HOME/WEB-INF

# Establish JVM options
CF_SECURITY_JVM_OPTIONS="-Djava.security.manager -Djava.security.policy=$CF_WEB_INF/cfusion/lib/coldfusion.policy -Djava.security.auth.policy=$CF_WEB_INF/cfusion/lib/neo_jaas.policy"
# Set JVM options for CORBA. Use if vbjorb.jar is not in your JRE's
# lib/ext directory. If used, append $CF_CORBA_JVM_OPTIONS to CF_JVM_OPTIONS
# CF_CORBA_JVM_OPTIONS=-Xbootclasspath/a:"$CF_WEB_INF/lib/vbjorb.jar"
CF_JVM_OPTIONS="$CF_SECURITY_JVM_OPTIONS"

JAVA_OPTS="$CF_JVM_OPTIONS -Xms128m -Xmx256m"

If you deployed the RDS application, you must also set the crossContext attribute to true for the CFIDE web application. You can do this through the Tomcat Administrator or by manually editing the tomcat_install_directory/conf/server.xml file.

To set the crossContext attribute through the Tomcat Administrator, perform the following steps:

1. Restart Tomcat.
2. Open the Tomcat Administrator in a browser (http://servername:8080/admin). If you've never used the Administrator, open the tomcat_root/conf/tomcat-users.xml file in a text editor and define a user in the admin role.
3. Go to Tomcat Server > Service (Tomcat-Standalone) > Host (localhost).
4. Click on Context (/CFIDE).
5. Set the Cross Context property to true.
6. Click Save.
7. Click Commit Changes.

To set the crossContext attribute by editing the server.xml file, perform the following steps:

1. Open the tomcat_root/conf/server.xml file in a text editor.
2. Add the following line under the Engine element:

   <Context className="org.apache.catalina.core.StandardContext"
   cachingAllowed="true" charsetMapperClass="org.apache.catalina.util.CharsetMapper"
   cookies="true" crossContext="true" debug="0" displayName="CFMX RDS Application"
   docBase="tomcat_root/webapps/CFIDE" mapperClass="org.apache.catalina.core.StandardContextMapper"
   path="/CFIDE" privileged="false" reloadable="false" swallowOutput="false"
   useNaming="true" wrapperClass="org.apache.catalina.core.StandardWrapper">
   </Context>

3. Save and close the server.xml file.

Restart the Tomcat server and monitor startup messages to ensure that all configurations were applied successfully.

Start the ColdFusion MX Administrator by opening a browser and going to http://hostname:portnumber/cfusion/CFIDE/administrator (for example, http://127.0.0.1:8080/cfusion/CFIDE/administrator). The startup wizard executes the first time you open the Administrator. For more information on the startup wizard, see the Installing and Using ColdFusion MX for J2EE book.

Note: The startup wizard is a pop-up window. To make sure that the wizard appears, disable any software options that prevent your web browser from displaying pop-up windows.

Code and test ColdFusion MX CFM pages. Store these pages in the cfusion web application root, as described in the "Using ColdFusion MX Applications
with J2EE Application Servers" chapter of the Installing and Using ColdFusion MX for J2EE book. You typically access these pages through the built-in Tomcat web server and use a URL of the form http://hostname:portnumber/cfusion/filename.cfm, as follows:

• hostname - The machine name, IP address, localhost, or 127.0.0.1.
• portnumber - The port number of the Tomcat web server, typically 8080.
• filename - The directory path and file to display. The path is relative to the cfusion directory.

For example, to display a CFM file located at /Applications/Jakarta-4.1.18/webapps/cfusion/eisapp/index.cfm, you could specify the URL as http://127.0.0.1:8080/cfusion/eisapp/index.cfm.