Accessibility
Adobe
Sign in Privacy My Adobe

ColdFusion Support Center

Enabling and Using ColdFusion MX 7 Features on Your J2EE Server

These discussions explain how to use ColdFusion MX 7 features on your Java 2 Enterprise Edition (J2EE) application server:

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

  • cfmx_install_directory - The directory that contains the files extracted by the ColdFusion MX installer; for example, C:\cfmx or /opt/cfmx.
  • appserver_root - The directory that contains your J2EE application server.
  • cf_webapp_root - The directory into which you deployed the ColdFusion MX web application; for example, C:\bea\user_projects\cfmx7wl7domain\cfusion-ear\cfusion-war.
  • java_home - The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.4.2_05.

Enabling JCE for 1.3.x JVMs

The security enhancements in ColdFusion MX 7 require the Java Cryptography Extension (JCE) 1.2.2 in the classpath. JCE is included in version 1.4 and higher Java Virtual Machines (JVMs); however, you must install JCE manually if you are using a 1.3.x JVM.

Download, install, and configure the Java Cryptography Extension (JCE) 1.2.2 by performing the following steps:

  1. Download the JCE installer from the Sun website.
  2. Install the JCE.
  3. Copy all the JAR files in the jce_root/lib directory to the wl_root/jdk/jre/lib/ext directory.

Verity considerations

Using the Verity Search Server

When you install the J2EE configuration on Windows, Solaris, or Linux, you can specify that the Install Wizard automatically install, configure, and start the Verity Search Server (the default directory is ColdFusionSearchService). When the install completes, the Verity Search Server is running.

On Windows, the Install Wizard creates a Windows service, which you use to start and stop the Verity Search Server. In UNIX, you start and stop Verity using the search_server_root/bin/cfmxsearch script.

Installing Verity search packs

ColdFusion MX lets you do Verity searches for languages other than English.

This section describes how to install a Verity Search Pack from the Macromedia website, and how to switch to a different Verity Search Pack.

To install a Verity Search Pack:

  1. If you have not yet registered ColdFusion MX 7, in your browser, go to the following location on the Macromedia website: http://www.macromedia.com/go/verity
  2. Enter your serial number on the Verity Search Packs page and click Submit.
  3. Download the appropriate Verity Search Pack (ZIP file for Windows, TAR file for UNIX), and save it to the cf_root\WEB-INF\cfusion directory in Windows and the cf_root/WEB-INF/cfusion directory on UNIX.
  4. Stop the application server.
  5. Extract the ZIP or TAR file. The files are automatically placed in the appropriate directories.
  6. Restart the application server.

To use a different Verity Search Pack (for example, for English), repeat this procedure for the new Verity Search Pack.

Installing optional components

ColdFusion MX 7 includes optional features that you must install separately:

  • Report Builder (Windows only)
  • Dreamweaver extensions for ColdFusion (Windows and Macintosh only)

When you install ColdFusion MX 7, the installer puts installation programs for the Report Builder and Dreamweaver extension in cf_webapp_root\CFIDE\installers directory.

  • To install the Report Builder, double-click the CFReportBuilderInstaller.exe file.
  • To install the Dreamweaver extensions, double-click the CFMX7DreamweaverExtensions.mxp file.

If you do not install the Verity search service when you install ColdFusion MX 7, you can also install it separately. To do so, follow the instructions in the “Installing the Verity search server separately” section in Installing and Using ColdFusion MX.

Upgrading to ColdFusion MX 7

If you previously deployed ColdFusion MX for J2EE or the ColdFusion MX 6.1 J2EE configuration on your application server, you must also perform the following steps as part of the installation procedure.

Caution: This procedure requires you to undeploy your existing ColdFusion MX application. Make sure to back up all the files and settings that you want to carry over to your updated installation, as described in steps 3 and 4.

  1. Stop the ColdFusion application and RDS application (if it is running).
  2. (Windows only) If you installed the SequelLink ODBC Agent, stop the ColdFusion MX or ColdFusion MX 6.1 ODBC Agent and ODBC Server services before you start the Installation Wizard.
  3. Save your application files by copying them to a backup directory that is not under cf_webapp_root.
  4. Save settings by copying the ColdFusion MX 6.1 files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml to a backup directory.
  5. Undeploy the existing copy of the ColdFusion J2EE application.
  6. If you have not already done so, install the ColdFusion MX 7 EAR file or WAR files.
  7. Deploy ColdFusion MX, using the application-server-specific instructions.
  8. Stop the ColdFusion web application (this may mean stopping the server instance in which ColdFusion MX runs).
  9. Copy the application files in the backup directory that you specified in step 3 back to your cf_webapp_root directory (for example, C:\Program Files\WebSphere\AppServer\installedApps\MYNODE\cfusion.ear\cfusion.war).
  10. Create a directory named cf6settings in the cf_webapp_root/WEB-INF/cfusion/lib directory.
  11. Copy the setting files that you saved in step 4 to the cf_webapp_root/WEB-INF/cfusion/lib/cf6settings directory.
  12. Edit the cf_webapp_root/WEB-INF/cfusion/lib/adminconfig.xml file by setting the value of the runmigrationwizard and the migratecf6 switch to true.
  13. Restart the ColdFusion MX 7 application.
  14. Open the ColdFusion MX Administrator, which automatically runs the Configuration and Settings Migration Wizard.

Enabling CORBA support

ColdFusion MX supports third-party Object Request Brokers (ORBs) through its integration with Borland VisiBroker. However, you must acquire the Common Object Request Broker Architecture (CORBA) software separately from Borland.

This section describes the system requirements for enabling CORBA support, and explains how to deploy and configure VisiBroker to work with ColdFusion MX.

System requirements

You must have the following components installed on your computer before you can make CORBA invocations from ColdFusion MX:

  • Borland VisiBroker 4.5.1 for Java
  • Java Runtime Environment (JRE) 1.2 or later for the VisiBroker Interface Repository

Installing and configuring VisiBroker for CORBA connections

This section describes how to use VisiBroker for CORBA connections.

To install and configure VisiBroker for CORBA connections:

  1. Install VisiBroker on the CORBA server side, if you have not already done so.

    For more information, see the Borland VisiBroker documentation.

  2. Copy the vbjorb.jar file to cf_webapp_root/WEB-INF/lib.
  3. Use your server-specific method to add the following JVM argument:
    -Xbootclasspath/a:cf_webapp_root/WEB-INF/lib/vbjorb.jar
    
  4. Restart the application server.
  5. Configure a VisiBroker connector in ColdFusion MX, as follows:
    1. In the ColdFusion MX Administrator, select Extensions > CORBA Connectors.
    2. On the CORBA Connectors page, click Register CORBA Connector.
    3. On the CORBA Connector page, enter information for the connector.

      The following are values for an example connector:

      Field Value
      ORB Name visibroker
      ORB Class Name coldfusion.runtime.corba.VisibrokerConnector
      Classpath (none)
      ORB Property File cf_webapp_root\WEB-INF\cfusion\lib\vbjorb.properties

      The ORB Property File points to a Java properties file that contains the correct ORB settings for VisiBroker.

      The contents of the vbjorb.properties file look like the following:

      org.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB
      org.omg.CORBA.ORBSingletonClass=com.inprise.vbroker.orb.ORB
      SVCnameroot=namingroot 
      
    4. When you finish editing the page, click Submit.

      The CORBA Connectors page appears.

    5. Select the option button to the left of your new CORBA connector, and click Select ORB Connector.

      This sets the new connector as the default connector.

  6. Prepare your CORBA server side, as follows:
    1. Start your VisiBroker osagent service or process, if it is not already running, by entering the following command:
      osagent
      

      If you must connect to an osagent in another subnetwork, include the following lines in the vbjorb.properties file:

      vbroker.agent.addr=<IP address of computer running OSAGENT>
      vbroker.agent.port=<port> 
      
    2. Start the Interface Repository and load it with the IDL file that you plan to use, by entering an irep command, as in the following example:
      irep myir MyIDLFile.idl 
      
    3. If you plan to use the Naming Service, start it by entering a command, as in the following example:
      nameserv namingroot 
      

      The name of the Naming Service (namingroot in the previous example) must match the value for SVCnameroot in the vbjorb.properties file.

    4. Start VisiBroker on your CORBA server.

      For more information, see the Borland VisiBroker documentation.

    5. Restart your application server for your changes to take effect.

Enabling web services access for Flash Remoting MX

By default, Flash Remoting cannot access ColdFusion MX 7 through web services, so you must manually enable Flash Remoting.

To enable Flash Remoting to access ColdFusion MX 7 through web services:

  1. Open the cf_webapp_root/WEB-INF/gateway-config.xml file in a text editor.
  2. Locate the CFWSAdapter line and remove the comments that surround it:
    <adapter>coldfusion.flash.adapter.CFWSAdapter</adapter> 
  3. Save the file.
  4. Restart ColdFusion.

For more information, see the "Using the Flash Remoting Service" chapter in ColdFusion MX Developer's Guide.

Using a third-party JDBC database driver

ColdFusion MX includes JDBC Type 4 database drivers from DataDirect and MySQL, and JDBC Type 3 database drivers from DataDirect and SQL Link.

To use a JDBC driver that is not included with ColdFusion MX (such as SQLAnywhere or PostgreSQL), you must configure it and add a data source for it.

To use a third-party JDBC database driver:

  1. Copy the JAR file for the database driver to the cf_root\WEB-INF\lib directory in Windows, or to the cf_root/WEB-INF/lib directory on UNIX.
  2. In the ColdFusion MX Administrator, on the Data Sources page, add the JDBC data source by selecting Other from the Driver drop-down list box.

    For more information, see the ColdFusion MX Administrator online Help.

You can now use the third-party JDBC database driver.

Using RDS

If you use Macromedia Dreamweaver MX, HomeSite+, or ColdFusion Studio to develop your applications, Remote Development Services (RDS) lets you access a remote ColdFusion MX server using HTTP. Using RDS, IDE users can securely access remote files and data sources, build SQL queries from these data sources, and debug CFML code. However, to maximize security, do not install RDS on production servers.

Note: ColdFusion MX does not support using RDS if you install multiple instances of ColdFusion MX on a single application server instance.

RDS web modules

When you run ColdFusion MX in the J2EE configuration, RDS support typically requires two web modules:

  • The ColdFusion MX web module
  • The RDS redirector web module, also called the RDS application

The ColdFusion MX web module processes RDS requests, in addition to all requests for ColdFusion pages.

If the ColdFusion MX context root is anything other than /, the redirector web module redirects RDS requests (which always go to the /CFIDE context root) to the ColdFusion MX module. The RDS redirector web module must have the context root /CFIDE, and is normally deployed in the same directory as cf_root.

Note: If you deploy ColdFusion MX at the / context root, you do not need the RDS redirector web module.

The instructions in the application-server-specific pages describe how to install and configure RDS support for your J2EE server. This section provides the following information:

  • How to reconfigure RDS support if you change the ColdFusion MX application context root.
  • How to disable ColdFusion RDS. This information includes a procedure that applies to all J2EE servers. The individual installation chapters provide additional J2EE server-specific information.

Configuring RDS for a new ColdFusion MX context root

If you change the ColdFusion MX context root after you deploy ColdFusion, you must manually reconfigure the RDS redirector web module to specify the correct context root.

To configure the RDS redirector with the correct context root, you must change the rds.properties file, which is located in the root directory of the RDS web module. The RDS web module root directory is typically located in the same directory as the ColdFusion MX context root, cf_root.

The rds.properties file has one line, with the following format:

contextRoot=ColdFusion_context_root 

for example,

contextRoot=cfmx 

When you change the ColdFusion MX application context root, you must change this line to specify the new ColdFusion MX context root. For example, if you change the ColdFusion MX context root from cfmx to ColdFusionMX, change the line to:

contextRoot=ColdFusionMX 

Disabling RDS

If you initially enabled RDS and want to disable it at a later time, you must do the following:

  • If ColdFusion is not located at the / context root, disable or undeploy the RDS redirector web module. (For a description of the module, see "Configuring RDS for a new ColdFusion MX context root".)
  • Disable the ColdFusion MX web module RDS Servlet. Doing so ensures that ColdFusion MX cannot respond to any RDS requests.

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

The procedure for disabling the redirector depends on your application server. For detailed instructions, see the Disabling RDS section on the page for your application server.

The procedure for disabling the RDS Servlet is the same for all application servers.

To disable the RDS servlet:

  1. Back up the ColdFusion web module web.xml file.

    By default, this file is in the cf_webapp_root/WEB-INF directory.

  2. Open the original web.xml file for editing.
  3. Comment out the RDS Servlet definition, as follows:
    <!--
    <servlet id="macromedia_servlet_8789">
      <servlet-name>RDSServlet</servlet-name>
      <display-name>Apache-Axis Servlet</display-name>
      <servlet-class>coldfusion.bootstrap.BootstrapServlet</servlet-class>
      <init-param id="InitParam_103401311065856789">
        <param-name>servlet.class</param-name>
        <param-value>coldfusion.rds.RdsFrontEndServlet</param-value>
      </init-param>
    </servlet>
    -->
    

    Note: Some of the text in the servlet definition might vary.

  4. Comment out the RDS Servlet mapping, as follows:
    <!--
    <servlet-mapping id="macromedia_mapping_5">>
    <servlet-name>RDSServlet</servlet-name>
    <url-pattern>/CFIDE/main/ide.cfm</url-pattern>
    </servlet-mapping>
    -->
    

    Note: The servlet-mapping id value might vary.

  5. Save the file.

RDS is disabled on ColdFusion MX.

Top Support Topics

 

More ColdFusion Topics

Choose a category to see more topics.

Request Support

 

Additional ColdFusion Resources

 

ColdFusion Downloads

 

Outside Resources

 

Feedback

 

Community