Macromedia - ColdFusion MX for J2EE on JRun4

Home / Products / ColdFusion / Support

Installing ColdFusion MX for J2EE on JRun4

Contents
•	Overview
•	Installing, deploying, and configuring ColdFusion MX
•	Other issues

Overview

ColdFusion MX is a J2EE application; the usual method of deploying J2EE applications
is through archive file deployment using EAR or WAR files. The first release of
ColdFusion MX for J2EE, which supported JRun 4, included an installer that did not
use archive file deployment.
Macromedia has completed testing archive file deployment with JRun 4 and now
recommends that you use the standardized deployment method when running
ColdFusion MX for J2EE on JRun 4. Using archive file deployment with JRun 4
provides a flexible and portable solution that also simplifies applying ColdFusion MX
updates.

In addition, archive file deployment has the following advantages:

•	It supports serializable ColdFusion session data, which is required to support session failover in clustered servers.
•	It lets developers and administrators deploy the applications themselves, including deploying multiple instances of ColdFusion MX under different context roots on the same application server.

This page provides instructions on using archive-file deployment of ColdFusionMX for J2EE on JRun 4. It refers to information in the Installing and Using Macromedia ColdFusion MX for J2EE book, which is available on the CD and on LiveDocs (English only).

The remainder of this page describes ColdFusion MX WAR file deployment and configuration on JRun 4. Before continuing, you should read the ColdFusion MX for J2EE Release Notes. You should also read the first and last chapters of Installing and Using ColdFusion MX for J2EE.

Back to Contents

Installing, deploying, and configuring ColdFusion MX

You deploy ColdFusion MX for J2EE on JRun 4 using uncompressed WAR files.

To install ColdFusion MX for J2EE on JRun 4, do the following:

1.	Run the ColdFusion MX for J2EE install procedure, executing the platform-specific installer: Windows - coldfusion-j2ee-win.exe Linux - coldfusion-j2ee-linux.bin Solaris - coldfusion-j2ee-solaris.bin Other platforms - coldfusion-j2ee-java.jar (run with java_home/java -jar coldfusion-j2ee-java.jar -i console) If you purchased the ColdFusion MX for JRun 4 box, you should use disk 2. You can download ColdFusion MX for J2EE installers from the Macromedia website.
2.	Answer the questions and select an install directory. When prompted to select EAR file or WAR file, select WAR file.
3.	Stop the JRun server to which you will deploy ColdFusion MX.
4.	Create a new directory under your server instance named cfusion. This directory will become the context root that the ColdFusion MX is deployed into; for example, /opt/jrun4/servers/default/cfusion.
5.	Create a new directory under your server instance name CFIDE (all uppercase). This directory will become the context root that the RDS application is deployed into; for example, /opt/jrun4/servers/default/CFIDE.
6.	If you have not already done so, open a console window, navigate to the cfusion directory that you created in the previous step, and uncompress the cfusion.war file with the following command (or with WinZip): jar -xvf install_directory/cfusion.war
7.	Navigate to the CFIDE directory and uncompress the rds.war file with the following command: cd ../CFIDE jar -xvf install_directory/rds.war
8.	(UNIX only) Configuring graphing support - Use either of the following methods: Using the JRun Management Console (JMC) - Under Settings, enter the following path in the VM arguments field, replacing default with the name of the server to which you are deploying ColdFusion MX: -Xms32m -Xbootclasspath/a:/jrun_root/servers/default/cfusion/WEB-INF/lib/webchartsJava2D.jar -Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment Ensure that you click Update at the bottom of the Settings page. Modifying the jvm.config file - Using a text editor, modify jrun_root/bin/jvm.config with the following entry for java.args: java.args=-Xmx128M -Xms32m -Xbootclasspath/a:/jrun_root/servers/default/cfusion/WEB-INF/lib/webchartsJava2D.jar -Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment Note: For JDK 1.4.1, specify com.gp.java2d.ExHeadlessGraphicsEnvironment (ColdFusion MX Updater 3 required).
9.	(Windows, Linux, Solaris) Configuring Verity support Windows - Use either of the following methods Using the JRun Management Console (JMC) - Under Settings, enter each of the following paths in the New JNI Library Path field, then click Add: {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_nti40/bin Ensure that you click Update at the bottom of the Settings page. Modifying the jvm.config file - Using a text editor, modify c:/jrun4/bin/jvm.config appending the following entry for java.library.path (all on one line): {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib,{application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_nti40/bin Linux and Solaris - Use either of the following methods: Using the JRun Management Console (JMC) - Under Settings, enter each of the following paths in the New JNI Library Path field, then click Add: {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_ssol26/bin (Solaris only) {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_ilnx21/bin (Linux only) Ensure that you click Update at the bottom of the Settings page. Modifying the jvm.config file - Using a text editor, modify jrun_root/bin/jvm.config appending the following entry for java.library.path (all on one line): {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib,{application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_ssol26/bin (Solaris) {application.home}/servers/default/cfusion/WEB-INF/cfusion/lib,{application.home}/servers/default/cfusion/WEB-INF/cfusion/lib/_ilnx21/bin (Linux)
10.	(Windows only) Configuring COM - Use either of the following methods: Using the JRun Management Console (JMC) - Under Settings, enter each of the following paths in the New JNI Library Path field, then click Add: {application.home}/servers/default/cfusion/WEB-INF/cfusion/jintegra/bin {application.home}/servers/default/cfusion/WEB-INF/cfusion/jintegra/bin/international Ensure that you click Update at the bottom of the Settings page. Modifying the jvm.config file - Using a text editor, modify jrun_root/bin/jvm.config appending the following entry for java.library.path (all on one line): {application.home}/servers/default/cfusion/WEB-INF/cfusion/jintegra/bin,{application.home}/servers/default/cfusion/WEB-INF/cfusion/jintegra/bin/international
11.	Start the JRun server and monitor startup messages to ensure that ColdFusion MX for J2EE deployed properly.
12.	Start the ColdFusion MX Administrator and run the startup wizard by entering the URL for the ColdFusion MX Administrator in a browser. The URL has the following form: http://host:[port]/cf_root/CFIDE/administrator for example: http://localhost:8100/cfusion/CFIDE/administrator When you first access the Administrator, ColdFusion runs the startup wizard. You provide the following information in the wizard to configure ColdFusion MX: Your Administrator password, originally specified when running the installer. Your serial number. If you do not enter a serial number and click Continue in Trial Mode, you can use ColdFusion in a fully featured Trial mode for 30 days. After 30 days without a serial number, ColdFusion runs in Developer mode, which only supports requests from the local host and one remote IP address. If you do not enter a serial number in the wizard, you can supply one later using the Version Information panel of the ColdFusion MX Administrator. Whether to configure RDS support and, if you configure RDS support, the RDS password. To maximize security, do not install RDS on production servers. For more information on RDS, see the LiveDocs discussion, "Using RDS". (Windows only) Whether to install support for ODBC data sources, such as Microsoft Access. If you select Yes, ColdFusion installs an additional database driver and a set of services for connecting to ODBC. The language for online Help in the ColdFusion MX Administrator and sample applications (if installed). Whether to install example applications. For security reasons, Macromedia recommends that you do not install example applications on production servers. Successful login to the Administrator is a confirmation that the install procedure was successful. However, before complete ColdFusion MX functionality is available, you might have to perform additional, site-specific tasks, as described in the following LiveDocs sections: Installing Verity Search Packs for ColdFusion MX Enabling CORBA support Using a third-party JDBC database driver
13.	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 in the Installing and Using ColdFusion MX for J2EE book. You typically access these pages through the JRun 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 JRun web server, typically 8100 for the default JRun server. 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 C:\JRun4\servers\default\cfusion\eisapp\index.cfm, you specify the URL as http://127.0.0.1:8100/cfusion/eisapp/index.cfm.

Back to Contents

Other issues

This section lists issues related to running ColdFusion MX for J2EE on JRun 4. For a complete list of ColdFusion MX for J2EE known issues, go to http://www.macromedia.com/go/cfmxj2ee-known_issues.

Disabling RDS - For security reasons, Macromedia recommends that you disable RDS on a production server. To disable RDS, perform the following steps:
- Disable the ColdFusion MX web module RDS Servlet, as described in the LiveDocs discussion, Using RDS.
- If your ColdFusion MX application context root is not /, delete the RDS web application from the JRun server by stopping the JRun server, deleting the jrun_root\servers\server_name\CFIDE directory, and starting the JRun server.
Note: If RDS is disabled, the Browse Server button does not work in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page).
Undeploying ColdFusion MX for J2EE - Perform the following steps:

Stop the JRun server.
Make a backup copy of the jrun_root/bin/jvm.config file.
Open the jrun_root/bin/jvm.config file in a text editor and remove all ColdFusion MX specifications from the java.args and java.library.path lines.
(Windows only) If you installed ODBC support, remove the ODBC Windows services by navigating to the cf_root\WEB_INF\cfusion\db\SequeLink Setup directory and executing the RemoveSequeLink.bat file.
Delete the jrun_root/servers/server_name/cfusion and jrun_root/servers/server_name/CFIDE directories.
Start the JRun server.

Setting the context root to slash (/) - By setting the context root to /, you do not have to include cfusion in the URL when accessing CFM pages. To set the context root to /, perform the following steps:
1. Stop the JRun server that is running ColdFusion MX.
2. Delete the jrun_root/servers/server_name/default-ear directory and all subdirectories.
3. Start the JRun server that is running ColdFusion MX.
4. Ensure that the admin JRun server is running.
5. Start the JMC (http://localhost:8000).
6. Click the server in the left pane.
7. Click the cfusion Web Application.
8. Change the context path to / (instead of /cfusion).
9. Click Apply.
10. Restart the JRun server that is running ColdFusion MX.

Back to Contents