Install the JEE configuration

Ensure that your operating system meets the system requirements described on the Adobe website at www.adobe.com/go/learn_cfu_cfsysreqs_en.

Read the online version of the Release Notes for any late-breaking information or updates. For more information, see www.adobe.com/go/learn_cfu_releasenote_en.

Review the Installation considerations for Windows and Installation considerations for all platforms sections in the Preparing to Install ColdFusion document.

Determine and record environment information, as described in Preparing to install using the JEE configuration section of this document.

Determine the answers to the questions in the above section Gathering information necessary to install the JEE configuration

Close any applications that are currently running on your computer.

Insert the DVD or download the setup file from the Adobe website.

If the installation wizard does not start automatically when you insert the DVD, locate the appropriate installer on the DVD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion installation executable file (ColdFusion_11_WWEJ_win32.exe (for 32-bit systems)/ColdFusion_11_WWEJ_win64.exe (for 64-bit systems)) and double-click it.

Follow the instructions in the installation wizard, and let it run to completion.

Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see ColdFusion JEE deployment and configuration section of this document.

Open the ColdFusion Administrator to run the Configuration wizard.

To install any other integrated Adobe or third-party technologies, see Installing Integrated Technologies.

Configure and manage your system, as described in Configuring your System.

To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

Code ColdFusion CFM pages.

Read the online version of the Release Notes for any late-breaking information or updates. For more information, see www.adobe.com/go/learn_cfu_releasenote_en.

Ensure that your operating system meets the system requirements described on the Adobe website at www.adobe.com/go/learn_cfu_cfsysreqs_en.

Review the Installation considerations for UNIX and Installation considerations for all platforms sections in the Preparing to Install ColdFusion document.

Determine and record environment information, as described in Preparing to install using the JEE configuration section of this document.

Determine the answers to the questions in the section Gathering information necessary to install the JEE configuration section of this document.

Log in as root.

Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save it to a directory on your local disk. 

The following installation files are those for supported JEE configuration platforms:

Using the cd command, go to the directory with the installation file.

Start the installation with the following command:

The installation program starts. 

To use the ColdFusion_11_WWEJ_java.jar file to install on a UNIX platform other than Solaris or Linux, enter the following command (for more information, see Installation considerations for UNIX in Preparing to Install ColdFusion page of this wiki ):

Follow the prompts, and let the installation program run to completion.

Deploy ColdFusion and configure Java settings, as required by your application server. 

For more information, see ColdFusion JEE deployment and configuration section of this page.

Open the ColdFusion Administrator to run the Configuration wizard.

Configure and manage your system, as described in Configuring your System.

To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

Code and test ColdFusion CFM pages.

Store CFM pages under the web application root (either cfusion-ear/cfusion-war or cfusion-war) and access these pages using a URL of the form http://_hostname_:_portnumber_/_context-root_/_filename_.cfm, as follows:

• hostname: The machine name, IP address, or localhost.
• portnumber: The port number used by your application server's web server.
• contextroot: The context root for the ColdFusion web application. For more information, see Context root section of this page.
• filename: The directory path and file to display. The path is relative to the cfusion-war directory.

Read the online version of the Release Notes for any late-breaking information or updates. For more information, see www.adobe.com/go/learn_cfu_releasenote_en.

Ensure that your operating system meets the system requirements described on the Adobe website at www.adobe.com/go/learn_cfu_cfsysreqs_en.

Review the Installation considerations for UNIX and Installation considerations for all platforms in the Preparing to Install ColdFusion document.

Determine and record environment information, as described in Preparing to install using the JEE configuration section of this page.

Determine the answers to the questions in the section Gathering information necessary to install the JEE configuration section of this page.

Log in as root.

Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save it to a directory on your local disk. 

The following installation files are those for supported JEE configuration platforms:

• ColdFusion_11_WWEJ_osx11.dmg - To install in Mac OS X systems

Start the installation by double-clicking the installation file on the desktop. The file ColdFusion Installer.app is installed in the same directory. Double click this APP file to start the installation in GUI mode.

Follow the prompts, and let the installation program run to completion

Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see ColdFusion JEE deployment and configuration section in this page.

Open the ColdFusion Administrator to run the Configuration wizard.

Configure and manage your system, as described in Configuring your System.

To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

Code and test ColdFusion CFM pages. 

Store CFM pages under the web application root (either cfusion-ear/cfusion-war or cfusion-war) and access these pages using a URL of the form http://_hostname_:_portnumber_/_context-root_/_filename_.cfm, as follows:

• hostname -The machine name, IP address, or localhost.
• portnumber-The port number used by your application server's web server.
• contextroot - The context root for the ColdFusion web application. For more information, see Context root section in this page.
• filename - The directory path and file to display. The path is relative to the cfusion-war directory.

As appropriate for your application server, either stop the ColdFusion application and RDS application (if it is running), or stop the application server before you start the installation wizard.

(Windows only) If you installed the SequelLink ODBC Agent, stop the ODBC services before you start the installation wizard.

Copy application files to a backup directory.

Save settings by copying the files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml to a backup directory.

Before you deploy ColdFusion,  undeploy  the previous ColdFusion application using your application-server-specific  undeploy  functionality.

Deploy ColdFusion as described in Deploying ColdFusion on IBM WebSphere, Deploying ColdFusion on Oracle WebLogic, or Deploying ColdFusion on JBoss Application Server sections of this page.

Create a directory named cf_X_settings (in which X is the earlier version of ColdFusion) in the cf_webapp_root/WEB-INF/cfusion/lib directory.

Copy the backed up settings files to the ColdFusion cfusion/lib/cf_X_settings directory.

Edit the ColdFusion entry in cfusion/lib/ adminconfig .xml file by setting the value of the  runmigrationwizard  and the  migratecf X  (in which X is the earlier version of ColdFusion) switch to true.

Restart the ColdFusion application.

Browse to ColdFusion Administrator to run the migration wizard.

Open a console window, navigate to the directory that contains the EAR file, and make a new directory named cfusion-ear:

Change to the cfusion-ear directory and expand the cfusion.ear file with the jarcommand:

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).

In cfusion-ear, make a new directory named cfusion-war.

Change to the cfusion-war directory and expand the cfusion.war file with the jarcommand:

This expands the cfusion.war file.

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

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

This expands rds.war.

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

Open the cfusion-ear/META-INF/application.xml file in a text editor.

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.

Save the application.xml file. To use LiveCycle Data Services ES, you must be running WebSphere 5.1.1 Business Integration.

Start the IBM WebSphere Application Server, if it is not running.

Open the IBM WebSphere Administrative Console, if it is not running.

Select Applications > Install New Application.

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:\ColdFusion11\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, which enables directory browsing on the server file system.

Leave the Context Root box empty and click Next.

Accept the default values on the second Select Installation Options page, 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.

If you have multiple application servers, select the application server in which to install the ColdFusion application and RDS support, and then click Next.

When the Map Virtual Hosts for Web Modules panel appears, select the virtual host or hosts in which to install the ColdFusion application and Remote Development Services (RDS) support, and then click Next.RDS must be on the same virtual host and port as ColdFusion.

When the Summary panel appears, review the installation configuration, and then click Finish.

When the Application Adobe ColdFusion 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.

Start the enterprise application named Adobe ColdFusion.

Browse to the ColdFusion Administrator to run the Configuration Wizard.

Start the IBM WebSphere Application Server, if it is not running.

Open the IBM WebSphere Administrative Console, if it is not running.

Select Applications > Install New Application.

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:\ColdFusion11\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, which enables directory browsing on the server file system.

Leave the Context Root box empty and click Next.

Accept the default values on the second Select Installation Options page, 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.

Select the cluster on which to install the ColdFusion application and RDS support, and then click Next.

When the Map Virtual Hosts for Web Modules panel appears, select the virtual host or hosts in which to install the ColdFusion application and Remote Development Services (RDS) support, and then click Next.RDS must be on the same virtual host and port as ColdFusion.

When the Summary panel appears, review the installation configuration, and then click Finish.

When the Application Adobe ColdFusion 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.

Start the enterprise application named Adobe ColdFusion.

Browse to the ColdFusion Administrator to run the Configuration Wizard.

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.

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):

Make a backup copy of the setupCmdLine.bat file, located in the websphere_root\AppServer\bin directory.

Open the original file for editing and add the following on a single line before the line that starts with SET WAS_CLASSPATH:

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

Add the CF_APPS_PATH variable to the WAS_CLASSPATH by appending the following text to the path statement:

The WAS_CLASSPATH line should look similar to the following:

Save the file.

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:

Save the file.

Make a backup copy of the setupCmdLine.bat file, which is located in the websphere_root\AppServer\bin directory.

Open the original file and add the following on a single line:

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

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

Open a console window and go to the cf_webapp_root\WEB-INF\cfusion\lib directory.

Register TypeViewer.dll by issuing the following command:

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) and did not rename the application.

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:

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

On Linux:

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

Append the CF_APPS_PATH environment variable to the LD_LIBRARY_PATH entry. The resulting line should be similar to the following:

On Linux:

Save the file and restart your WebSphere Application Server.

Open the WebSphere Administrative Console.

In the left navigation bar, select Node_name > Servers > Application Servers.

Select your JEE application server; for example, Server1.

Under Java and Process Management, select Process Definition.

On the Process Definition page, select Java Virtual Machine in the Additional Properties box.

If you are running ColdFusion 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:

Click OK.

Save the master configuration file.

Stop ColdFusion.

In the WebSphere Administrative Console, select the Applications > Enterprise Applications panel, select the Adobe ColdFusion application, and then click Stop.

Do the following in both the cf_webapp_root\WEB-INF\web.xml and the websphere_root\AppServer\config\cells\NodeName\applications\cf_application_name.ear\ deployments\cf_application_name\cfusion.war\WEB-INF\web.xml files (or the equivalent paths in UNIX). For example, change the following files:

Back up the ColdFusion web module web.xml file (available in either C:\Program Files\WebSphere\AppServer\installedApps_<MY_NODE>\cfusion.ear\cfusion.war\WEB-INF\web.xml or C:\Program Files\WebSphere\AppServer\config\cells_<MY_NODE>\applications\cfusion.ear\deployments\Adobe ColdFusion <version>\cfusion.war\ WEB-INF\web.xml).

Open the original web.xml file for editing.

Comment out the RDS Servlet definition, as follows:

The text in the servlet definition might vary.

Comment out the RDS Servlet mapping, as the following example shows:

The servlet-mapping id value might vary.

Save the file.

Restart the ColdFusion application.

If your ColdFusion application context root is something other than /, disable or undeploythe RDS redirector web module by doing the following:

In the WebSphere Administrative Console, select cell_name > Applications > Enterprise Applications.

Stop the Adobe ColdFusion application if it is running.

Select Adobe ColdFusion Application, select Manage Modules and then select the check box for ColdFusion RDS application, and then click Remove.

Extract the cfusion.war in a folder, for example, cfusion .

Comment the default permissions granted to all domain and provide full permission to [Oracle_Home]\wlserver\server\lib\weblogic.policy file.

Edit startWeblogic.cmd and replace set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%   with set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS% -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl

Start WebLogic from command prompt using [Oracle_Home]\user_projects\domains\base_domain\bin\startWeblogic.cmd.

Deploy the cfusion directory either through WLAdminConsole/deployments/install or by placing it in autodeploy folder of domain created. The exploded war gets deployed and is seen in the WLAdminConsole as well.

Run the ColdFusion installation wizard, choosing the JEE configuration. The installation wizard places the WAR files in the install directory.

Determine the WebLogic domain in which to deploy ColdFusion. Optionally, create a domain.

Because ColdFusion must run from an expanded directory structure, expand the  cfusion .war and rds .war files manually, and expand the web applications by doing the following:

1. Open a console window, navigate to the directory that contains the WAR files, and create a directory for the ColdFusion WAR file (named whatever you want the context root to be) and the RDS WAR file (named CFIDE):

b. Change to the cfusion directory and expand the cfusion.war file with the jar command:

c. Go up one level to the install directory:

Go to the CFIDE directory and expand the rds.war file with the jar command:

Open the weblogic.policy file. On WebLogic 11g, the file is located in the WebLogic_HOME/wlserver_11.0/server/lib/ directory. In a text editor, comment out the restrictive permissions, and add permission java.security.AllPermission; to the default permissions section, as the following example shows:

Deploy the cfusion and CFIDE directory structures using your site-specific WebLogic deployment method.

Ensure that the following jars are in the startup script's classpath.

Review the console messages and server log to ensure that ColdFusion deployed successfully.

Start the ColdFusion Administrator, which runs the Configuration wizard.

To install any other integrated Adobe or third-party technologies, see Installing Integrated Technologies.

Configure and manage your system, as described in Configuring your System.

To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the Resources page of the ColdFusion Administrator.

Locate the startup script for the WebLogic domain, which is typically the startWebLogic cmd file, which is located in the wldomain_root\bin directory.

Make a backup copy of this file.

Open the startup script.

Establish the following basic variables at the beginning of the script:

• CF_WEB_INF

• CF_SHARED_LIB
  
  For example:

Save the startup script and restart the WebLogic Server.

Open the startup script for the WebLogic domain, which is typically the startWebLogic cmd file, which is located in the wldomain_root\bin directory.

Establish the following variables:

• JINTEGRA_PATH
• PRE_CLASSPATH

• PRE_PATH
  
  For example:

Locate the startup script for the WebLogic domain, which is typically the startWebLogic.sh file, which is located in the wldomain_root\bin directory.

Make a backup copy of this file.

Open the startup script.

Establish the following basic variables at the beginning of the script:

• CF_WEB_INF

• CF_SHARED_LIB
  
  For example:

Save the startup script and restart the WebLogic Server.

Open the startup script for the WebLogic domain, which is typically the startWebLogic cmd file, which is located in the wldomain_root\bin directory.

Establish or append to the following variable:

• CF_SECURITY_JVM_OPTIONS
• MEM_ARGS
  
  If you are not using JRockit, append -Xms32m -Xmx512m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line of the startup script. 
  
  If you are using JRockit, append -Xms32m -Xmx512m -Xss64k to the existing MEM_ARGS line of the startup script.
  
  
• JAVA_OPTIONS Append the CF_SECURITY_JVM_OPTIONS variable to the existing JAVA_OPTIONS line of the startup script)
  
  For example:

Save the startup script and restart the WebLogic Server.

Open the startup script for the WebLogic domain, which is typically the startWebLogic.sh file, which is located in the wldomain_root\bin directory.

Establish or append to the following variables:

• CF_SECURITY_JVM_OPTIONS
• CF_GRAPHING_JVM_OPTIONS
• MEM_ARGS
  
  If you are not using JRockit, append -Xms32m -Xmx512m -Xss64k -XX:MaxPermSize=128m to the existing MEM_ARGS line of the startup script. 
  
  If you are using JRockit, append -Xms32m -Xmx512m -Xss64k to the existing MEM_ARGS line of the startup script.
   

• JAVA_OPTIONS Append the CF_SECURITY_JVM_OPTIONS variable to the existing JAVA_OPTIONS line of the startup script)
  
  For example:

Save the startup script and restart the WebLogic Server.

Ensure that the application server and the OC4J instance are running.

Open a Windows command prompt and go to the oracle_root/dcm/bin directory.

Deploy the ColdFusion application by using the command-line tool dcmctl.bat , as follows:

Edit the oracle_root/j2ee/oc4j_instance/config/java2.policy file by adding the following to the end of the file:

Start the ColdFusion Administrator, which runs the Configuration and Settings Migration wizard.

You must perform some configuration steps to enable support for CFX tags written in C++, which binary files that are specific to your operating system.

Connect to Oracle AS 11g using Enterprise Manager.

Go to oc4j_instance/Administration/Server Properties.

Under the Environment Variables category, select Add Environment Variable.

Enter PATH as the name.

Enter $ORACLE_HOME\j2ee\ oc4j_instance\applications\ cf_app\cfusion\WEB-INF\cfusion\lib; as the value.

Ensure that the Append option is selected.

Select Apply.

When the Enterprise Manager prompts you to restart, select the restart option.

Connect to Oracle AS 11g using Enterprise Manager.

Go to oc4j_instance/Administration/Server Properties.

Under the Environment Variables category, select Add Environment Variable.

Enter LD_LIBRARY_PATH as the name.

Enter $ORACLE_HOME/j2ee/oc4j_instance /applications/cf_app /cfusion/WEB-INF/cfusion/lib; as the value.

Ensure that the Append option is selected.

Select Apply.

When the Enterprise Manager prompts you to restart, select the restart option.You must enable Component Object Model (COM) support in Windows after installing ColdFusion to use the cfreport tag with Crystal Reports. It is not required for the ColdFusion Report Builder or any reports that you create with the ColdFusion reporting feature.

In Oracle AS 11g Enterprise Manager, go to oc4j_instance /Administration/Server Properties.

In the Environment Variables category, ensure that the entry PATH exists. If not, follow the instructions to enabling features with operating system-specific binaries.

Add {{$ORACLE_HOME\j2ee\oc4j_instance\applications\cf_app\cfusion\WEB-INF\cfusion\jintegra\bin; $ORACLE_HOME\j2ee\oc4j_instance\applications\cf_app \cfusion\WEB-INF\cfusion\jintegra\bin\international }}as the value.

Ensure that the Append option is enabled.

Select Apply.

When the Enterprise Manager prompts you to restart, select the restart option.

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 cf_webapp_root\WEB-INF\cfusion\lib.

2. Register TypeViewer.dll by issuing the following command:

The following steps configure your application server to useColdFusion charting and graphing on AIX, Linux, and Solaris systems. This step is not required to enable charting and graphing in Windows.

In Oracle AS 11g Enterprise Manager, go to oc4j_instance/Administration/Server Properties.

If the following entry does not exist in the Java Option under the Command Line Options category, add it:

Select Apply.

When the Enterprise Manager prompts you to restart, select the restart option.

In the Oracle AS 11g Enterprise Manager, select oc4j_instance /Applications.

Select Adobe ColdFusion application and select Edit.

In the Administration category, select Advanced Properties.

In the Configuration Files category, select orion-application.xml.

Comment out the RDS web module as the following example shows:

Apply the changes.

Restart the OC4J instance.You can enable the RDS web module by repeating this procedure and selecting the Enabled option.

Set JAVA_HOME to the appropriate JDK.

Install ColdFusion by using the JEE deployment option and selecting to create an EAR file (the default). The installation program creates the cfusion.ear file in the install directory.

Extract the cfusion.ear file into a TEMP_LOCATION\cfusion.ear folder. This step creates cfusion.war and rds.war files and a META-INF folder in the cfusion.ear folder.

In the cfusion.ear folder, extract the cfusion.war and rds.war files into folders named cfusion andrds, respectively.

Delete the compressed cfusion.war and rds.war files.

Rename the cfusion and rds folders to cfusion.war and rds.war, respectively.

Stop JBoss if it is running.

Copy or move the {{TEMP_LOCATION\cfusion.ear }}folder into the {{JBOSS_DEPLOY_DIR }}folder. For JBoss 7, place the exploded ear in the {{JBOSS_HOME/standalone/deployments }}directory and create an empty file cfusion.ear.dodeploy (if your EAR directory name is cfusion.ear.) The resulting directory structure will appear as follows:

(Windows)Edit the JBOSS_HOME\bin\run.bat file for JBoss 5.1 and 6.x and JBOSS_HOME\standalone.bat for JBoss 7.x by doing the following:

1. If not present, add the JVM (-Xmx512m) parameter to JAVA_OPTS.
2. Ensure that the permanent generation heap size is set by adding -XX:MaxPermSize=128m to JAVA_OPTS.Without this parameter, the JVM can generate a java.lang.OutOfMemoryError error.
3. Ensure that the jars available in WEB-INF/flex/jars are in the classpath.
4. Save the run.bat file.

5. Start the server by running the JBOSS_HOME\bin\run.bat file.

(Linux) Edit the JBOSS_HOME/bin/run.conf file by doing the following:

1. In JAVA_OPTS, change -Xmx128m. to -Xmx512m.
2. Add -XX:MaxPermSize=128m to JAVA_OPTS.
3. Save the run.conf file.
4. Start the server by running the JBOSS_HOME/bin/run.sh file. To enable features with operating system-specific binaries, configure ColdFusion. This step 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 (Windows only)
  
  Use the following procedure for your operating system to configure the search paths to find the required binary files. These files are located in the CF_WEBAPP_ROOT\WEB-INF\cfusion\lib directory.

Select the Deployments tab in the console.

Note: The deployment method for applications differ according to whether you are deploying to a standalone server instance or in a managed domain.

 To add the ColdFusion archive, click Add.

On the Create Deployment dialog box, browse to the file you want to deploy, select it, and upload it.

 Edit or verify the deployment name and choose if you want to enable the archive after deployment.

Open the browser and enter http://localhost:8080/cfusion/CFIDE/administrator/index.cfm. This opens the ColdFusion administrator on EAP. The default context root is cfusion.

Copy the cfusion.war file into a temp folder and unzip it.

  Delete the compressed cfusion.war files.

Rename the temp folder to cfusion.war.

The resulting directory structure will appear as follows:

a.      CFIDE

b.      META-INF

c.       WEB-INF

d.      Config.ini

e.      Crossdomain.xml

 Place the cfusion.war folder in {EAP_Install_location}/standalone/deployments.

 Copy or move the {{TEMP_LOCATION\cfusion.war }} folder into the {{JBOSS_DEPLOY_DIR }}folder. Place the exploded war in the {{JBOSS_HOME/standalone/deployments}} directory and create an empty file cfusion.war.dodeploy. A marker file is created in the deployment folder to indicate the successful deployment, and the application is flagged as Enabled in the Management Console. You can see that the archive starts to deploy and when the deployment ends, the name of the text file changes to {name_of_war}.war.deployed.

Start JBoss EAP server.

Enter http://localhost:8080/cfusion/CFIDE/administrator/index.cfm in your browser to launch the ColdFusion administrator.  The default context root is cfusion.

  To view the deployment folders, click System Information and navigate to the Java class path section.

Decompress the cfusion.war file after changing the extension from .war to .zip. Place the contents in a folder called cfusion.war. This cfusion war folder can reside anywhere in the local file system.

To point the Domain Controller server instance to the exploded file, use any of the following three ways:

1. Log in to the EAP management console of the Domain Controller at : http://<EAP-DC-IP>:9990/console/App.html#domain-deployments

• 1. Navigate to the Deployments tab, and click Add.  Switch to the Unmanaged tab in theCreate Deployment window that pops up.
  2. Specify the path to the exploded cfusion.war directory.
  3. Leave the Relative To field blank.
  4. Clear the Is Archive check-box.
  5. Enter cfusion.war in the Name and Runtime Name fields.
• Run the following command in the Domain Controller Management CLI:

/deployment=cfusion.war:add(runtime-name="cfusion.war", content=[{"path"=>"<absolute-path-to-cf-war>\\cfusion.war","archive"=>false}])

• Add the following configuration element to the <deployments> XML element in the domain.xml file of the Domain Controller:

<deployments>

    <deployment name="cfusion.war" runtime-name="cfusion.war">

        <fs-exploded path="<absolute-path-to-exploded-app-war-dir>/cfusion.war"/>

    </deployment>

</deployments>

Make the exploded cfusion.war file available to all the managed server instances at the same path specified for the Domain Controller above. Create the same folder structure and copy the cfusion.war dir to the local file system of all the server instances.

1. Deploy the WAR file by running the following command in the Domain Controller Management CLI:

deploy --name=cfusion.war --all-server-groups

Once the deployment is completed, you can access the ColdFusion application on the various EAP server instances at port offset mentioned in the “Domain > Topology” section in the EAP management console.

Access the ColdFusion administrator console at:

<server-instance-IP>:<8080+offset>/cfusion/CFIDE/administrator

By default, the application context (“cfusion” here) is the name of the deployed WAR file. A successful deployment does not produce any output to the CLI. You can monitor the Domain Controller / Host Controller console to see the deployment process. A successful deployment should start the ColdFusion application.

If you are using ColdFusion-based web-services, copy the version of tools.jar  that the application server uses to the cfusion/lib directory at <cfusion-war>\WEB-INF\cfusion\lib.

Ensure that JBoss Server is stopped.

Edit JBOSS_HOME\bin\run.bat by adding the following:

Edit the run.bat file that is located in the JBOSS_DEPLOY_DIR by doing the following:

1. Locate the following text:

Below this text, insert three lines and paste.

Save the file and start the server.

Ensure that JBoss Server is stopped.

Edit JBOSS_HOME/bin/run.sh by adding the following:

Ensure that JBoss Server is stopped.

Edit JBOSS_HOME\bin\run.bat by adding the following:

Save the file and start ColdFusion.

Stop ColdFusion.

Edit JBOSS_DEPLOY_DIR\cfusion.ear\cfusion.war\WEB-INF\web.xml by commenting out the following:

Go to the line that contains the -Xmx512m parameter.

Change the text: -Dprogram.name=%PROGNAME% to be -Dcoldfusion.disablejsafe=true %JAVA_OPTS%. 

Create a WAR file of ColdFusion application. See deploying section for more information. For example, http://localhost:8080

Open the Tomcat admin console (http://hostname:portnumber) 

Click the Manager app at the right side menu options. Alternatively, you canuse: http://hostname:portnumber/manager/html. 

1. Tomcat Web Application Manager appears. You can see a list of applications already deployed in Tomcat server at the top followed by the WAR file deploy option. 

Click Choose File to browse through your system and choose the WAR file. 

Click Deploy.

Remove all ColdFusion specifications from the java.args and java.library.path JVM arguments used by your application server.

(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.

If necessary, copy and save CFM pages from the ColdFusion web application root.

Undeploy the ColdFusion web application using application-server-specific undeployfunctionality.

On WebLogic, open the WebLogic Administrator., open the WebLogic Administration Console (http://hostname:portnumber/console) and go to domainname > Deployments > Applications. Click the trash can to the right of the ColdFusion application, and then click Yes. Open the startup script for the WebLogic domain and remove ColdFusion-specific entries, as follows:

If necessary, restart the application server.