Accessibility

ColdFusion Support Center

Installing and Deploying ColdFusion MX 7 on Other J2EE Application Servers

Macromedia ColdFusion MX 7 supports the following configurations:

  • Server configuration - Lets you install one instance of ColdFusion MX 7 with an embedded Java 2 Enterprise Edition (J2EE) server. This configuration most closely resembles the ColdFusion MX base release and other releases prior to ColdFusion MX, such as ColdFusion 5 and ColdFusion 4.5. This was formerly known as the stand-alone configuration. For information on installing this configuration, see Installing and Using ColdFusion MX.
  • Multiserver configuration (Enterprise and Developer Editions only) - Installs JRun and automatically deploys ColdFusion MX 7 in a separate JRun server instance. For information on installing this configuration, see Installing and Using ColdFusion MX.
  • J2EE configuration (Enterprise and Developer Editions only) - Lets you deploy ColdFusion MX 7 as a Java application running on a Java 2 Enterprise Edition (J2EE) application server, such as JRun 4, IBM WebSphere, or BEA WebLogic. This document provides generic instructions for deploying ColdFusion MX 7 on unsupported J2EE servers.

When you run ColdFusion MX 7 in the J2EE configuration, you use the application server's deployment mechanism to deploy ColdFusion MX on a J2EE 1.3 compliant application server. The Install Wizard lets you install ColdFusion MX as either an enterprise application or a web application.

About this document

This document provides basic instructions for deploying and configuring ColdFusion MX in the J2EE configuration on any J2EE 1.3 compliant application server. It refers to overview information in Installing and Using ColdFusion MX, which is available on LiveDocs (English and Japanese only). Installing and Using ColdFusion MX also includes important information on configuring and uninstalling ColdFusion MX 7.

This document contain general instructions on installing a new copy of ColdFusion MX. For instructions on updating an existing ColdFusion MX deployment to ColdFusion MX 7, and for configuration information that is common to all J2EE servers, see "Enabling and Using ColdFusion MX Features on Your J2EE Server" before continuing.

Conventions in this document

This document uses the following conventions to reference application server and ColdFusion directories:

  • cf_webapp_root - The directory into which you deployed the ColdFusion MX web application; for example, C:\Program Files\Apache Group\Tomcat 4.1\webapps\cfusion.
  • cf_context_root - The web server context root into which you deployed ColdFusion MX; for example, cfusion.
  • java_home - The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.4.1.
  • app_server_root - The directory that contains the application server; for example, C:\Program Files\Apache Group\Tomcat 4.1\.

Installing, deploying, and configuring ColdFusion MX 7

Because you store ColdFusion pages (CFM pages) under the ColdFusion MX context root, ColdFusion MX must run out of an open directory structure. However, not all J2EE application server deployment methods result in a working open directory structure. Most J2EE application servers let you deploy an open directory in WAR or EAR format (that is, the directory structure contains j2eeapp/META-INF/application.xml and webapp/WEB-INF/web.xml files) or deploy by expanding the EAR or WAR file into a working open directory structure. For example, Tomcat autodeploy results in an open directory structure under the webapps directory.

To install ColdFusion MX 7 using EAR or WAR files:

  1. Run the ColdFusion MX 7 Install Wizard after downloading the platform-specific installer:

    • Windows - coldfusion-70-win.exe
    • Linux - coldfusion-70-lin.bin
    • Solaris - coldfusion-70-sol.bin
    • Other platforms - coldfusion-70-other.jar (run with java_home/bin/java -jar coldfusion-70-other.jar -i console)

    These installers are available on the Macromedia website.

  2. Answer the questions. When prompted, do the following:

    1. Select Enterprise Edition, Developer Edition, or Trial, as appropriate.
    2. Select J2EE configuration and either EAR or WAR file, depending on your J2EE server's application deployment method.
    3. Specify whether to install ODBC services (Windows only), Search services, and supporting material.
    4. Specify the installation directories for ColdFusion MX and the Search Service.
    5. If you are deploying using an EAR file, specify the context root. Macromedia recommends the context root /cfusion, but you can deploy cfusion.war at any context root, including /, as supported by your application server.
    6. Select the Java Servlet API 2.3 or later option.
    7. Specify a password for use with the ColdFusion MX Administrator.
    8. (Only if RDS is enabled) Specify a password for use with Remote Development Services (RDS).

      The Install Wizard places the cfusion.ear or cfusion.war and rds.war files in the installation directory.

  3. Do the following, depending on whether you are deploying ColdFusion MX as an EAR file or as WAR files.

    • If you are deploying as an EAR file, follow your application server's configuration procedures to deploy the cfusion.ear file. This deploys both the ColdFusion and RDS web applications. Depending on your application server, you might have to expand the archives and deploy the expanded directory structure.
    • If you are deploying using WAR files, deploy the cfusion.war web application. Macromedia recommends the context root /cfusion, but you can deploy cfusion.war at any context root, including /, as supported by your application server.

      To support RDS, deploy the rds.war web application at the /CFIDE context root. If you install cfusion.war at /, you do not need the RDS web application.

  4. (If using a 1.3.x JVM) Download and install the Java Cryptography Extension (JCE), as described in Enabling JCE for 1.3.x JVMs in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server.
  5. Restart your application server, if necessary, and check the logs to ensure a successful deployment.
  6. Stop your application server.
  7. The ColdFusion MX 7 tools.jar file is compatible with a 1.4.2 level JVM. If your J2EE server uses a different JDK version, rename your cf_webapp_root/WEB-INF/cfusion/lib/tools.jar file to something else (for example, tools.old).
  8. (Windows, Linux, and Solaris) Add ColdFusion MX binary file directories to the JVM argument for the native library path (java.library.path). These directories are as follows:

    ColdFusion MX binaries - cf_webapp_root/WEB_INF/cfusion/lib

    jIntegra binaries (Windows only, COM support) - cf_webapp_root/WEB-INF/cfusion/jintegra/bin and cf_webapp_root/WEB-INF/cfusion/jintegra/bin/international

    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.

  9. 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_webapp_root/WEB-INF/cfusion/lib/vbjorb.jar"

    Charting (1.3.x JVMs only) - For instructions on enabling charting on servers that use a 1.3.x JVM, see cf_webapp_root/WEB-INF/cfusion/charting/java1.3/readme.txt.

    Charting (UNIX only) - Define the following argument:

    -Djava.awt.headless=true

    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"
    

    Additionally, certain application servers require that you disable server-specific policy-file permissions in order to enable the ColdFusion security manager.

  10. If you use RDS, some application servers require that you enable cross-web-application (also called cross-context) communication. For information on enabling cross-context communication, see you application server documentation.
  11. Restart the J2EE Application server and monitor startup messages to ensure that all configurations were applied successfully.
  12. Start the ColdFusion MX Administrator by using a URL of the form http://hostname:portnumber/cf_context_root/CFIDE/administrator/index.cfm, as follows:

    • hostname - The machine name, IP address, localhost, or 127.0.0.1.
    • portnumber - The port number of the web server.

    The ColdFusion MX Administrator runs the Configuration and Settings Migration Wizard before starting.

  13. Code and test ColdFusion MX (CFM) pages. Store these pages in the cfusion web application root directory. For example, to display a CFM file located at /Jakarta-4.1.18/webapps/cfusion/eisapp/index.cfm, you could specify the URL as http://127.0.0.1:8080/cfusion/eisapp/index.cfm.
  14. (Optional, Windows only) Install the Report Builder and Dreamweaver extensions, as described in Installing optional components in Enabling and Using ColdFusion MX 7 Features on Your J2EE Server.

Undeploying ColdFusion MX

To undeploy ColdFusion MX in the J2EE configuration, you use application server-specific undeploy tools and methods.

To undeploy ColdFusion MX in the J2EE configuration:

  1. Remove all ColdFusion MX specifications from the java.args and java.library.path JVM arguments used by your application server.
  2. (Windows only) If you installed ODBC support, remove the ODBC Windows services by navigating to the cf_webapp_root\WEB_INF\cfusion\db\SequeLink Setup directory and executing the RemoveSequeLink.bat file.
  3. If necessary, copy and save CFM pages from the ColdFusion MX web application root.
  4. Undeploy the ColdFusion MX web application, using application server-specific undeploy functionality.
  5. If necessary, restart the application server.

Top Support Topics

 

More ColdFusion Topics

Choose a category to see more topics.

Request Support

 

Additional ColdFusion Resources

 

ColdFusion Downloads

 

Outside Resources

 

Feedback

 

Community