Installing and Using ColdFusion MX for J2EE
Installing on BEA WebLogic Server 7.0

Enabling specific ColdFusion MX functionality

For some ColdFusion MX functionality to work properly, you must manually configure your application server. This section describes what to do for the following functionality:

• Configuring security settings
• Editing the server startup script
• Enabling WebLogic jCOM support (Windows only)
• Disabling RDS

You must restart the WebLogic Server to enable the changes described in this section.

Configuring security settings

Open the weblogic_root/weblogic700/server/lib/weblogic.policy file in a text editor, comment out the restrictive permissions, and add permission java.security.AllPermission; to the default permissions section, as shown in the following example:

...

// Default permissions that need to be granted to applications at this point
grant {
permission java.security.AllPermission;
/*
permission java.io.SerializablePermission "enableSubstitution";
...
permission java.util.PropertyPermission "*", "read,write";
*/
};
...

These changes take effect when you restart the WebLogic Server.

Editing the server startup script

This section describes how to edit the WebLogic server startup script to enable support for the following functionality:

• COM (Windows only)
• Verity
• Graphing
• Sandbox security

To enable support for Verity, COM, graphing, and sandbox security:

1. Locate the startup script for the WebLogic domain. This is typically wldomain_root/startWebLogic.cmd (Windows) or wldomain_root/startWebLogic.sh (UNIX).
2. Make a backup copy of this file.
3. Open the startup script.
4. Establish the following basic variables at the beginning of the script:
   • CF_WEB_INF
   • CF_SHARED_LIB_DIR

     For example:

     Windows:
     SET CF_WEB_INF=cf_root\%CF_HOME%\WEB-INF
     SET CF_SHARED_LIB_DIR=%CF_WEB_INF%\cfusion\lib
     
     UNIX:
     CF_WEB_INF=cf_root/WEB-INF
     CF_SHARED_LIB_DIR=${CF_WEB_INF}/cfusion/lib
     

5. Enable access to Verity binary files through the following variables:
   • CF_SHARED_LIBS
   • LD_LIBRARY_PATH (UNIX only)

     For example:

     Windows:
     @rem Set up shared library path for CFMX to pick up Verity
     @rem shared libs. Use path syntax - entries separated by a semicolon.
     SET CF_SHARED_LIBS=%CF_SHARED_LIB_DIR%;%CF_SHARED_LIB_DIR%\_nti40\bin
     
     UNIX:
     # Set up shared library path for CFMX to pick up Verity
     # shared libs. Use path syntax - entries separated by colon.
     # Use _solaris/bin for Solaris and _ilnx21/bin for Linus
     # CF_SHARED_LIBS="${CF_SHARED_LIB_DIR}:${CF_SHARED_LIB_DIR}/_solaris/bin"
     CF_SHARED_LIBS="${CF_SHARED_LIB_DIR}:${CF_SHARED_LIB_DIR}/_ilnx21/bin"
     LD_LIBRARY_PATH="${CF_SHARED_LIBS}:${LD_LIBRARY_PATH}"
     

6. (Windows only) Enable ColdFusion MX Jintegra COM support by establishing the following variables:
   • JINTEGRA_PATH
   • PRE_CLASSPATH
   • PRE_PATH

     For example:

     SET JINTEGRA_PATH= %CF_WEB_INF%\cfusion\jintegra\bin; %CF_WEB_INF%\cfusion\jintegra\bin\international
     SET PRE_CLASSPATH=%CF_SHARED_LIB_DIR%\jintegra.jar
     SET PRE_PATH=%CF_SHARED_LIBS%;%JINTEGRA_PATH%
     

   Note:   Alternatively, you can use WebLogic JCOM support instead of ColdFusion MX JIntegra COM support. To use WebLogic JCOM support, see "Enabling WebLogic jCOM support (Windows only)".

7. Enable ColdFusion MX security and graphing support by establishing or appending to the following variables:
   • CF_SECURITY_JVM_OPTIONS
   • CF_GRAPHING_JVM_OPTIONS
   • MEM_ARGS (append -Xms32m -Xmx256m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line of the startup script)
   • JAVA_OPTIONS (append the CF_SECURITY_JVM_OPTIONS and CF_GRAPHING_JVM_OPTIONS variables to the existing JAVA_OPTIONS line of the startup script)

     For example:

     Windows:
     SET CF_SECURITY_JVM_OPTIONS=-Djava.security.manager
     SET CF_GRAPHING_JVM_OPTIONS=
     "-Xbootclasspath/a:%CF_SHARED_LIB_DIR%\webchartsJava2D.jar
     -Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment"
     @rem You must append %CF_SECURITY_JVM_OPTIONS% and %CF_GRAPHING_JVM_OPTIONS% 
     @rem to the existing JAVA_OPTIONS value.
     @rem You must append the following to the existing MEM_ARGS value.
     @rem -Xms32m -Xmx256m -Xss64k -XX:MaxPermSize=128m
     
     UNIX:
     CF_SECURITY_JVM_OPTIONS="-Djava.security.manager"
     CF_GRAPHING_JVM_OPTIONS="\
     -Xbootclasspath/a:${CF_SHARED_LIB_DIR}/webchartsJava2D.jar \
     -Djava.awt.graphicsenv=com.gp.java2d.ExGraphicsEnvironment \
     "
     # You must append ${CF_SECURITY_JVM_OPTIONS} and ${CF_GRAPHING_JVM_OPTIONS}
     # to the existing JAVA_OPTIONS value.
     # JAVA_OPTIONS="default java options ${CF_SECURITY_JVM_OPTIONS} ${CF_GRAPHING_JVM_OPTIONS}"
     # You must append the following to the MEM_ARGS variable coded
     # in the server startup file:
     # "-Xms32m -Xmx256m -Xss64k" -XX:MaxPermSize=128m
     

8. Save the startup script and restart the WebLogic Server.

Enabling WebLogic jCOM support (Windows only)

ColdFusion MX includes Jintegra COM support, which you enable through the WebLogic Server startup script. Alternatively, you can use WebLogic jCOM.

Note:   ColdFusion MX Jintegra COM support uses native mode, which disables COM objects that use DCOM. WebLogic jCOM supports DCOM or native mode, however, ColdFusion MX COM functionality requires native mode.

To use WebLogic jCOM as the ColdFusion MX Java to COM bridge:

1. Omit the COM support step in "Editing the server startup script".
2. Enable jCOM support by opening the WebLogic Administrator, navigating to domainname > Servers > servername > connections >JCOM, and selecting enable COM, enable Native Mode, and Prefetch ENums.
3. Open a console window, navigate to weblogic_root\weblogic700\server\bin, and execute the regjvmcmd tool to register the JVM for COM, as shown in the following example:

   regjvmcmd /native servername
   

Disabling RDS

For security reasons, Macromedia recommends that you disable RDS on a production server. If you install and enable RDS support, you can disable it later in the WebLogic Administrator.

Note:   If RDS is disabled, the Browse Server button does not work in the ColdFusion MX Administrator (for example, on the ColdFusion Mappings page).

To disable RDS, you must do the following:

• Disable RDSServlet in the ColdFusion MX web application.
• If your ColdFusion MX application context root is not /, disable the RDS web application.

For instructions on disabling the RDS Servlet, see "Using RDS". The following procedure describes how to disable the RDS web application.

To disable the RDS web application:

1. Open the WebLogic Administrator.
2. Open the WebLogic Administration Console (http://hostname:portnumber/console) and go to domainname > Deployments > Web Applications.
3. Click on the trash can to the right of the RDS web application.
4. Click Yes.

   The WebLogic Administrator undeploys the web application.

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

Version 6

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

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

Current page: http://livedocs.adobe.com/coldfusion/6/Installing_CFMX_for_J2EE/install_WebLogic3.htm

Add Comment