After you deploy the ColdFusion MX 7 application, you define JVM arguments. Each J2EE application server has a different method for 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:
java.library.path argument
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 7 J2EE configuration, you can run basic ColdFusion pages and start the ColdFusion MX Administrator. However, certain types of ColdFusion MX 7 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:
COM (Windows only) Add the following jIntegra binary directories to the JVM's native library path (java.library.path):
WEB-INF/cfusion/jintegra/bin WEB-INF/cfusion/jintegra/bin/international
Note: If your J2EE server runs on an operating system other than Windows, Solaris, or Linux, you can still run ColdFusion MX 7, but the functionality that is provided through platform-specific binary files is unavailable. For a complete list of supported platforms, see System requirements.
Depending on your operating system, you might have to add the following to the java.args JVM argument:
COM (Windows only) Add the following arguments:
-DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS
CORBA (optional) Copy the vbjorb.jar file to the WEB-INF/cfusion/lib directory and define the following argument:
-Xbootclasspath/a:"cf_webapp_root/WEB-INF/cfusion/lib/vbjorb.jar"
Charting (UNIX only) Define the following argument:
-Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment"
For JDK 1.4.1 and later versions, specify com.gp.java2d.ExHeadlessGraphicsEnvironment instead of com.gp.java2d.ExGraphicsEnvironment.
Security In addition to enabling sandbox security in the ColdFusion MX Administrator, the application server must be running a security manager (java.lang.SecurityManager) and you must define the following JVM arguments:
-Djava.security.manager -Djava.security.policy="cf_webapp_root/WEB-INF/cfusion/lib/coldfusion.policy" -Djava.security.auth.policy="cf_webapp_root/WEB-INF/cfusion/lib/neo_jaas.policy"
Additional setup To use cfregistry on Windows, to use the cfreport tag for Crystal Reports, and to use any C++ CFX custom tags, you must add cfusion/lib to the Java library path. Add the following directory to the JVM's native library path (java.library.path):
WEB-INF/cfusion/lib
Additionally, certain application servers require that you disable server-specific policy-file permissions in order to enable the ColdFusion security manager. For more information, see the application-server-specific instructions at www.macromedia.com/go/cfmx7_j2eecert.
If the version of the tools.jar file in your application server's JRE is different from the version of the tools.jar file in the WEB-INF/cfusion/lib directory, you should rename or delete the WEB-INF/cfusion/lib/tools.jar file to ensure that your application server's tools.jar file is used.