View comments | RSS feed

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:

Accessing an Oracle 8.1.7 database

If you use the Macromedia Oracle driver (or the equivalent DataDirect driver) to access an Oracle 8.1.7 database, then your server will fail during any repetitive SQL operation against this database; for example, when you loop over a cfquery block.

To remedy this, do one of the following:

Accessing COM objects (Windows only)

This section describes how to enable Component Object Model (COM) support in Windows after installing ColdFusion MX.

To enable COM support:

  1. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  2. Open the original file for editing and add the following on a single, long line:
    SET PATH=%PATH%;%WAS_HOME%\installedApps\%WAS_NODE%\Macromedia ColdFusion MX.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin;%WAS_HOME%\
    installedApps\%WAS_NODE%\Macromedia ColdFusion MX.ear\cfusion.war\
    WEB-INF\cfusion\jintegra\bin\international
    
  3. Save the file and restart your computer.

Enabling charting and graphing

This section describes how to configure your application server to use ColdFusion MX charting and graphing (cfchart, cfchartdata, and cfchartseries tags).

To enable charting and graphing:

  1. Open the WebSphere Administrative Console.
  2. In the left navigation bar, select Node_name > Servers > Application Servers.
  3. Select your J2EE application server; for example, Server1.
  4. On the Configuration tab of the Application server page, click the Process Definition link in the Additional Properties box.
  5. On the Process Definition page, click the Java Virtual Machine link in the Additional Properties box.
  6. In the Additional Properties box at the bottom of the page, click the Custom Properties link.
  7. On the Custom Properties page, click New and add a system property, completing the fields as follows:
  8. Click OK to return to the Java Virtual Machine page.
  9. In the General Properties box of the Java Virtual Machine page, type the following in the Boot Classpath field:

    cf_root/WEB-INF/cfusion/lib/webchartsJava2D.jar

  10. Click OK.

Supporting Verity searches

Note:   Verity searching is only supported on Windows, Linux, and Solaris.

To use the Verity search engine and the cfcollection, cfindex, and cfsearch tags, you must enable Verity searching. To do searches in languages other than English, including both European and Asian languages, you must also install language-specific Verity Search Packs.

Enabling searching with Verity

To enable Verity, use the procedure for your operating system to configure the library search path to find the Verity binary files. (The Verity files are in the cf_root\WEB-INF\cfusion\lib directory in Windows, and the cf_root/WEB-INF/cfusion/lib directory on UNIX.)

(Windows) To configure IBM WebSphere Application Server for Verity:

  1. Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.
  2. Open the original file for editing and add the following on a single, long line before the line that starts with SET WAS_CLASSPATH:
    SET CFMX_VERITY_PATH=%WAS_HOME%\installedApps\%WAS_NODE%\
    Macromedia ColdFusion MX.ear\cfusion.war\WEB-INF\cfusion\lib;
    %WAS_HOME%\installedApps\%WAS_NODE%\Macromedia ColdFusion MX.ear\
    cfusion.war\WEB-INF\cfusion\lib\_nti40\bin
    
  3. Add the CFMX_VERITY _PATH variable to the WAS_CLASSPATH by appending the following text to the path statement:
    ;%CFMX_VERITY _PATH%
    

    The WAS_CLASSPATH line should look similar to the following:

    SET WAS_CLASSPATH=%WAS_HOME%/properties;%WAS_HOME%/lib/bootstrap.jar; %WAS_HOME%/lib/j2ee.jar;%WAS_HOME%/lib/lmproxy.jar;%CFMX_VERITY _PATH%
  4. Save the file and restart your computer.

You can now use Verity in ColdFusion MX.

(UNIX) To configure IBM WebSphere Application Server for Verity:

  1. Make a backup copy of the startServer.sh file, located in the websphere_root/AppServer/bin directory.
  2. Open the original file for editing, and in the PLATFORM case block, just above the LD_LIBRARY_PATH line, add the following entry on a single, long line:

    Note:   The path specifications in these instructions assume you deployed ColdFusion using the standard application name (Macromedia ColdFusion MX) and did not rename the application.

    On Solaris:

    LD_LIBRARY_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/
    Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/
    lib:"$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/
    cfusion.war/WEB-INF/cfusion/lib/_solaris/bin
    

    On Linux:

    CFMX_VERITY_PATH="$WAS_HOME"/installedApps/"$WAS_NODE"/
    Macromedia ColdFusion MX.ear/cfusion.war/WEB-INF/cfusion/
    lib:"$WAS_HOME"/installedApps/"$WAS_NODE"/Macromedia ColdFusion MX.ear/
    cfusion.war/WEB-INF/cfusion/lib/_ilnx21/bin
    
  3. Append the CFMX_VERITY_PATH environment variable to the LD_LIBRARY_PATH entry. The resulting line should be similar to the following:
       LD_LIBRARY_PATH="$WAS_LIBPATH":$LD_LIBRARY_PATH:$CFMX_VERITY_PATH
    
  4. Save the file and restart WebSphere.

You can now use Verity in ColdFusion MX.

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 WebSphere Administrative Console.

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:

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

To disable the RDS web module:

  1. In the WebSphere Administrative Console, select node_name > Applications > Enterprise Applications.
  2. Stop the Macromedia ColdFusion MX application if it is running.
  3. Click the Macromedia ColdFusion MX Application link to display the Configuration page and select the Local Topologies tab.
  4. Expand the Macromedia_ColdFusion_MX entry in the Applications tree, then expand the Web Module folder and click the rds.war link to display the rds.war configuration page.
  5. Click the Target Mappings link in the Additional Properties box, and click the link to your application server, for example, Server1.
  6. On the Configuration page General Properties box, clear the Enabled check box and click OK.
  7. Click the Save to Master Configuration link at the top of the Target Mappings page and click the Save button on the Save page to save your workspace.
  8. When the configuration has been saved and the main Administrative Console page appears, stop and restart the application server.
  9. Start the ColdFusion Application, if necessary.

The RDS web module is disabled. You can reenable the RDS web module by repeating this procedure and selecting the Enabled check box.

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.

Comments


dgianetti said on Jun 15, 2007 at 10:44 AM :
The section entitled "Enabling searching with Verity" has a couple substantial errors.

1. On the "SET CFMX_VERITY_PATH=%WAS_HOME%\installedApps\%WAS_NODE%\
Macromedia ColdFusion MX.ear\cfusion.war\WEB-INF\cfusionib;
%WAS_HOME%\installedApps\%WAS_NODE%\Macromedia ColdFusion MX.ear\
cfusion.war\WEB-INF\cfusionib\_nti40\bin" line, the Macromedia Coldfusion MX may or may not be the name used to during your installation.

2. In the line, "Add the CFMX_VERITY _PATH variable to the WAS_CLASSPATH by appending the following text to the path statement:
;%CFMX_VERITY _PATH%" it states you should add the line to the WAS_CLASSPATH variable. This is incorrect. You should, instead, add this to the WAS_PATH on the line below.

3. There is a typo in the above line as well. The first set of instructions state you should SET CFMX_VERITY_PATH, then proceeds to append ;%CFMX_VERITY _PATH% to the classpath. There is an extra space between VERITY and _PATH that causes an error.

If you correct all these errors and ensure the name used in the path is actually the name of your application as it is installed, you should be able to start the verity engine.

 

RSS feed | 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_Websphere53.htm