1. Open a console window, navigate to the directory that contains the EAR file, and make a new directory named cfusion-ear:
   md cfusion-ear (mkdir cfusion-ear on UNIX)
   
   
2. Change to the cfusion-ear directory and expand the cfusion.ear file with the jar command:

   cd cfusion-ear
   java_home/bin/jar -xvf ../cfusion.ear
   

   This expands the cfusion.ear file into cfusion.war and rds.war (rds.war is not included if you specified a context root of / when you ran the installation wizard).

3. In cfusion-ear, make a new directory named cfusion-war.
   md cfusion-war (mkdir cfusion-war on UNIX)
   
   
4. Change to the cfusion-war directory and expand the cfusion.war file with the jar command:

   cd cfusion-war
   java_root/bin/jar -xvf ../cfusion.war
   

   
   

   This expands the cfusion.war file.

5. (If rds.war exists) Go up one level to cfusion-ear, make a new directory named rds-war.

   cd ..
   md rds-war (mkdir rds-war on UNIX)
   

   
   
6. (If rds.war exists) Change to the rds-war directory and expand rds.war with the jar command:

   cd rds-war
   java_root/bin/jar -xvf ../rds.war
   

   
   

   This expands rds.war.

7. Go up one level to the cfusion-ear file, and delete the cfusion.war and rds.war files:

   cd ..
   del cfusion.war (rm cfusion.war on UNIX)
   del rds.war (rm rds.war on UNIX)
   

   
   
8. Open the cfusion-ear/META-INF/application.xml file in a text editor.
9. Change the web-uri element from cfusion.war to cfusion-war (or the name of the directory that contains the expanded cfusion.war file). Change the web-uri element for rds.war to rds-war. A directory name in the web-uri element cannot contain a dot.
10. Save the application.xml file.

On WebSphere ND, deploying multiple application server clones on a single computer is commonly referred to as vertical clustering. Vertical clustering leverages the computer's processing power to obtain a higher level of efficiency; however, if there is total computer failure, no application server instances are available. The applications deployed in a vertical cluster share the same file system. Deploying the multiple application servers on multiple computers is commonly referred as horizontal clustering; it provides the highest level of failover and scaling. The steps you perform to deploy ColdFusion 8 in a clustered environment are the same, regardless of clustering method, because the WebSphere Network Deployment Manager manages the cluster.

To use LiveCycle Data Services ES, you must be running WebSphere 5.1.1 Business Integration.

1. Start the IBM WebSphere Application Server, if it is not running.
2. Open the IBM WebSphere Administrative Console, if it is not running.
3. Select Applications > Install New Application.
4. When the Preparing for the Application Installation page appears, in the text box for the local file system, enter the path to the EAR file that you installed when you installed ColdFusion; for example, C:\ColdFusion8\cfusion.ear.

   If you are running the Administrative console from a browser that is not on the same system on which WebSphere is running, that is, not from localhost, use the Remote file system option ( Server Path on WebSphere 5.1), which enables directory browsing on the server file system.

5. Leave the Context Root box empty and click Next.
6. Accept the default values on the second Select Installation Options page (Preparing for the Application Installation on WebSphere 5.1), if appropriate for your WebSphere configuration, and then click Next.

   WebSphere might display an Application Security Warnings page with a message at the bottom of the page that starts with "ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application." You can ignore this warning.

7. If you have multiple application servers, select the application server in which to install the ColdFusion application and RDS support, and then click Next.
8. If you selected to install LiveCycle Data Services ES , the Map Resource References to resources panel appears. Enter wm/default as the target for the resource wm/MessagingWorkManager.
9. When the Map Virtual Hosts for Web Modules panel appears, select the virtual host or hosts in which to install the ColdFusion 8 application and Remote Development Services (RDS) support, and then click Next.

   RDS must be on the same virtual host and port as ColdFusion 8.

10. When the Summary panel appears, review the installation configuration, and then click Finish.
11. When the Application Adobe ColdFusion 8 Installed Successfully message appears on the Installing page, select Save To Master Configuration, and then select Save on the Save page to save your workspace.

    If you changed the application name from the default, the message uses your application name.

12. Start the enterprise application named Adobe ColdFusion 8.
13. Browse to the ColdFusion Administrator to run the Configuration Wizard.

1. Start the IBM WebSphere Application Server, if it is not running.
2. Open the IBM WebSphere Administrative Console, if it is not running.
3. Select Applications > Install New Application.
4. When the Preparing for the Application Installation page appears, in the text box for the local file system, enter the path to the EAR file that you installed when you installed ColdFusion; for example, C:\ColdFusion8\cfusion.ear.

   If you are running the Administrative console from a browser that is not on the same system on which WebSphere is running, that is, not from localhost, use the Remote file system option ( Server Path on WebSphere 5.1), which enables directory browsing on the server file system.

5. Leave the Context Root box empty and click Next.
6. Accept the default values on the second Select Installation Options page (Preparing for the Application Installation on WebSphere 5.1), if appropriate for your WebSphere configuration, and then click Next.

   WebSphere might display an Application Security Warnings page with a message at the bottom of the page that starts with "ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application." You can ignore this warning.

7. Select the cluster on which to install the ColdFusion application and RDS support, and then click Next.
8. If you selected to install LiveCycle Data Services ES , the Map Resource References to resources panel appears. Enter wm/default as the target for the resource wm/MessagingWorkManager.
9. When the Map Virtual Hosts for Web Modules panel appears, select the virtual host or hosts in which to install the ColdFusion 8 application and Remote Development Services (RDS) support, and then click Next.

   RDS must be on the same virtual host and port as ColdFusion 8.

10. When the Summary panel appears, review the installation configuration, and then click Finish.
11. When the Application Adobe ColdFusion 8 Installed Successfully message appears on the Installing page, select Save To Master Configuration, and then select Save on the Save page to save your workspace.

    If you changed the application name from the default, the message uses your application name.

12. Start the enterprise application named Adobe ColdFusion 8.
13. Browse to the ColdFusion Administrator to run the Configuration Wizard.

1. Do the following to ensure that ColdFusion sandbox security secures Java access to files and network resources:
   1. On the WebSphere Administrative Console Security > Secure Administration panel, ensure that the Java 2 Security option is selected.
   2. Click Apply and then click Save.
2. Add the following lines to the Standard Properties That Can Be Read By Anyone section of the JVM's security policy file, java.policy. (For example, this file can be located in C:\Program Files\WebSphere\AppServer\java\jre\lib\security\java.policy):

   grant {
   permission java.security.AllPermission;
   };
   

   
   

This process is required to support the following features that use binaries that are specific to your operating system:

• CFX tags written in C++
• Microsoft Access driver with Unicode support

You do this by configuring the search paths to find the required binary files, which are located in the cf_webapp_root\WEB-INF\cfusion\lib directory.

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 line before the line that starts with SET WAS_CLASSPATH:
   SET CF_APPS_PATH=cf_webapp_root\WEB-INF\cfusion\lib
   
   

   Replace cf_webapp_root with the path to your web application directory; for example, enter the following:

   SET CF_APPS_PATH=%WAS_HOME%\installedApps\%WAS_CELL%\ Adobe_ColdFusion_8.ear\cfusion.war\WEB-INF\cfusion\lib
   
   
3. Add the CF_APPS_PATH variable to the WAS_CLASSPATH by appending the following text to the path statement:
   ;%CF_APPS_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;%WAS_HOME%/lib/urlprotocols.jar;%CF_APPS_PATH%
   
   
4. Save the file.
5. Add the full path to the cf_webapp_root\WEB-INF\cfusion\lib directory to the WAS_PATH variable in the setupCmdLine.bat file. The WAS_PATH line should look similar to the following:
   SET WAS_PATH=%WAS_HOME%\bin;%JAVA_HOME%\bin;%JAVA_HOME%\jre\bin;%PATH%;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\java\bin;C:/Program Files/IBM/WebSphere MQ/WEMPS\bin;%CF_APPS_PATH%;
   
   
6. Save the file.

You enable Component Object Model (COM) support in Windows after installing ColdFusion 8 so that you can use the cfreport tag with Crystal Reports. COM support is not required for the ColdFusion Report Builder or any reports that you create with the ColdFusion reporting feature.

1. Make a backup copy of the setupCmdLine.bat file, which is located in the websphere_root\AppServer\bin directory.
2. Open the original file and add the following on a single line:
   SET PATH=%PATH%;cf_webapp_root\WEB-INF\cfusion\jintegra\bin;cf_webapp_root\WEB-INF\cfusion\jintegra\bin\international
   
   

   Replace cf_webapp_root with the path to your web application root directory, for example:

   SET PATH=%PATH%;%WAS_HOME%\installedApps\%WAS_CELL%\AdobeColdFusion8.ear\cfusion.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin;%WAS_HOME%\installedApps\%WAS_CELL%\Adobe_ColdFusion_8.ear\cfusion.war\WEB-INF\cfusion\jintegra\bin\international
   
   
3. Save the file.

In some cases, you might also have to do the following to register the Microsoft Type viewer:

1. Open a console window and go to the cf_webapp_root\WEB-INF\cfusion\lib directory.
2. Register TypeViewer.dll by issuing the following command:
   regsvr32 TypeViewer.dll
   
   

This process is required to support CFX tags written in C++ that use binaries that are specific to your operating system.

You must configure the search paths to find the required binary files, which are located in the cf_webapp_root/WEB-INF/cfusion/lib directory.

1. Make a backup copy of the startServer.sh file, which is located in the websphere_root/AppServer/bin directory.

   The path specifications in these instructions assume that you deployed ColdFusion using the standard application name (Adobe ColdFusion 8) and did not rename the application.

2. Open the original file, and in the PLATFORM case block, just above the LD_LIBRARY_PATH or LIBPATH line, add the following entry on a single, long line:

   On Solaris:

   CFMX_APPS_PATH=cf_webapp_root/WEB-INF/cfusion/lib
   
   

   Replace cf_webapp_root with the path to your web application root directory; for example:

   CF_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_CELL"/Adobe_ColdFusion_8.ear/cfusion.war/WEB-INF/cfusion/lib
   
   

   On Linux:

   CF_APPS_PATH=cf_webapp_root/WEB-INF/cfusion/lib
   
   

   Replace cf_webapp_root with the path to your web application root directory; for example:

   CF_APPS_PATH="$WAS_HOME"/installedApps/"$WAS_CELL"/ Adobe_ColdFusion_8.ear/cfusion.war/WEB-INF/cfusion/lib
   
   
3. Append the CF_APPS_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:$CF_APPS_PATH
   
   
4. Save the file and restart your WebSphere Application Server.

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. Under Java and Process Management, select Process Definition.
5. On the Process Definition page, select Java Virtual Machine in the Additional Properties box.
6. If you are running ColdFusion 8 on a system without a monitor, do the following:
   1. In the Additional Properties box at the bottom of the page, select Custom Properties.
   2. On the Custom Properties page, select New and add a system property, completing the fields as follows:
      Name java.awt.headless
      Value true
      
      
7. Click OK.
8. Save the master configuration file.

For security reasons, Adobe recommends that you disable RDS on a production server. If you enable RDS when you install ColdFusion 8, you can disable it at a later time, as the following instructions describe.

If you disable RDS, the following ColdFusion 8 features do not work:

• The Browse Server button in the ColdFusion Administrator (for example, on the ColdFusion Mappings page)
• The Query Builder and charting in the ColdFusion Report Builder