Contents > Installing and Using ColdFusion MX > Installing the J2EE Configuration > ColdFusion MX J2EE deployment and configuration > Configuration

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.

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 vbjorb.jar to WEB-INF/cfusion/lib and define the following argument:

    -Xbootclasspath/a:"cf_root/WEB-INF/cfusion/lib/vbjorb.jar"
  

• Charting  Define the following argument (or ensure that WEB-INF/cfusion/lib is in the JVM's classpath):

    -Xbootclasspath/a:$cf_root/WEB-INF/cfusion/lib/webchartsJava2D.jar 
  

  Note: For JDK 1.4.1 and later versions, specify com.gp.java2d.ExHeadlessGraphicsEnvironment instead of com.gp.java2d.ExGraphicsEnvironment.

• Charting (UNIX only) Define the following argument:

  -Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment"
  

  Note: 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_root/WEB-INF/cfusion/lib/coldfusion.policy" 
    -Djava.security.auth.policy="cf_root/WEB-INF/cfusion/lib/neo_jaas.policy"
  

  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/cfmxj2ee-cert.

If the version of tools.jar in your application server's JRE is different from the version of tools.jar in WEB-INF/cfusion/lib, you should rename or delete WEB-INF/cfusion/lib/tools.jar to ensure that your application server's tools.jar file is used.

Contents > Installing and Using ColdFusion MX > Installing the J2EE Configuration > ColdFusion MX J2EE deployment and configuration > Configuration

ColdFusion 9 | ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting

Version 6.1

Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/coldfusion/6.1/htmldocs/instal17.htm

Add Comment