User Guide

ColdFusion MX J2EE deployment and configuration 45
5 Continue with the procedure from the Configuration Wizard step, as described in “Installing
an EAR file or WAR files” on page 39.
Expanding and deploying WAR files on JRun 4
Although it is best to deploy ColdFusion MX as an enterprise application, you can also deploy
ColdFusion MX as a web application. When deploying ColdFusion MX 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 on JRun 4 as a WAR file,
see www.macromedia.com/go/cfmxj2ee-cert.
Configuration
After you deploy the ColdFusion MX application, you define JVM arguments. Each J2EE
application server has a different method of defining JVM arguments. Depending on your server,
you can update variables in a batch file or shell script, define arguments in an administrative
interface, modify the java.library.path JVM argument directly, or modify the system path directly.
You define two types of JVM arguments:
• Platform-specific items for the java.library.path argument.
• Java arguments for the java.args argument.
Note: When running JRun 4, you configure these settings through the Settings panel of the JRun
Management Console (JMC) or by using a text editor to modify the
jrun_root/bin/jvm.config file.
After you deploy the ColdFusion MX for J2EE application, you can run basic ColdFusion pages
and start the ColdFusion MX Administrator. However, certain types of ColdFusion MX
functionality are performed through platform-specific binary files (that is, compiled C++ files,
not Java bytecode), which are provided for Windows, Solaris, and Linux. In addition, some of
these features require server-specific environment settings. The following list includes platform-
specific functionality and the steps you must perform to enable their use:
• Verity Add Verity binary directories to the JVM's native library path
(
java.library.path). The directories are as follows:
WEB-INF/cfusion/lib
WEB-INF/cfusion/lib/
platform/bin (where platform is _nti40, _solaris, or
_ilnx21)
• Verity and C++ CFX support Add WEB-INF/cfusion/lib to the JVM’s classpath.
• COM (Windows only) Add jIntegra binary directories to the JVM’s native library path
(
java.library.path). The directories are as follows:
WEB-INF/cfusion/jintegra/bin
WEB-INF/cfusion/jintegra/bin/international
• Microsoft Access for Unicode database driver and cfreport (Windows only) Add WEB-
INF/cfusion/lib to the JVM’s classpath.
Note: If your J2EE server runs on an operating system other than Windows, Solaris, or Linux, you can
still run ColdFusion MX, but the functionality in the previous list is unavailable. For a complete list of
supported platforms, see “System requirements” on page 10.