Installing an EAR file or WAR files



If your computer is already running a J2EE application server, the installation wizard creates an EAR file or WAR files, which you deploy using application-server-specific tools.

The ColdFusion J2EE configuration must run from an expanded directory structure. Different J2EE application servers have different functionality with regard to deployment and an expanded directory structure, as follows:

Deploy compressed archive to working directory On some J2EE application servers (such as IBM WebSphere), the deployment process expands the EAR/WAR file into a working directory and, from that point forward, the expanded directory is considered to be the application. For these application servers, you deploy the compressed EAR/WAR file and work in the resulting directory structure. For more information, see ColdFusion J2EE deployment and configuration.

Deploy expanded archive as working directory
On other application servers (such as JRun 4 and BEA WebLogic), the deployment process expands the EAR/WAR file into a temporary directory and (conceptually), the compressed EAR/WAR file is still considered to be the application. For these application servers, expand the EAR/WAR file manually, and then deploy the expanded directory structure, which becomes your working directory. For more information, see ColdFusion J2EE deployment and configuration.

    Installing an EAR file or WAR files in Windows

    You can install the ColdFusion J2EE configuration in Windows. If you are updating an existing deployment of ColdFusion MX, ColdFusion MX 6.1, or ColdFusion MX 7 for J2EE, see Updating from an earlier version for J2EE before you continue.

    Note: The Windows installer requires a computer that supports at least 256 colors.

    Install ColdFusion in Windows (J2EE configuration)

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

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

    3. Review the Installation considerations for Windows and Installation considerations for all platforms.

    4. Determine and record environment information, as described in Preparing to install using the J2EE configuration.

    5. Determine the answers to the questions in the section Gathering information necessary to install the J2EE configuration

    6. Close any applications that are currently running on your computer.

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

    8. If the installation wizard does not start automatically when you insert the DVD, locate the setup.exe file 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-90-win.exe) and double-click it.

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

    10. Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see ColdFusion J2EE deployment and configuration.

    11. Open the ColdFusion Administrator to run the Configuration wizard.

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

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

    14. If using JRun, add the Log4J-1.2.12.jar file to the JRun server classpath (C:\Jrun4\servers\lib). By default, it is in the ColdFusion classpath(C:\JRun4\servers\CF9\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib).

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

    16. Code 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.

      • filename: The directory path and file to display. The path is relative to the cfusion-war directory.

        For example, to display a CFM file located at C:\JRun4\servers\myserver\cfusion-ear\cfusion-war\eisapp\index.cfm using the built-in JRun web server and a context root of cf9, specify the URL as http://localhost:8100/cf9/eisapp/index.cfm.

    Installing an EAR file or WAR files in UNIX

    You can install the ColdFusion J2EE configuration in UNIX. If you are updating an existing deployment of ColdFusion MX, ColdFusion MX 6.1, or ColdFusion MX 7 for J2EE, see Updating from an earlier version for J2EE before you continue.

    Install ColdFusion in UNIX (J2EE configuration)

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

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

    3. Review the Installation considerations for UNIX and Installation considerations for all platforms.

    4. Determine and record environment information, as described in Preparing to install using the J2EE configuration.

    5. Determine the answers to the questions in the section Gathering information necessary to install the J2EE configuration.

    6. Log in as root.

    7. 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 J2EE configuration platforms:

      • coldfusion-90-lin.bin - To install on Linux.

      • coldfusion-90-sol.bin - To install on Solaris.

      • coldfusion-90-other.jar - To install on a UNIX platform other than Solaris or Linux.

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

    9. Start the installation with the following command:

      ./<filename> -i console

      The installation program starts.

      To use the coldfusion-90-other.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):

      java_home/bin/java -jar coldfusion-90-other.jar -i console
      Note: To run the UNIX installer in GUI mode, type ./<filename> -i gui.

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

      Note: For security reasons, it is crucial that you do not use root for the run-time user. Instead, use a nonprivileged user that does not have a login shell, such as the default user account nobody, which exists for this type of situation.

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

      For more information, see ColdFusion J2EE deployment and configuration.

      Note: If you deployed the rds.war file, and an error message indicates that RDS is not installed or not enabled, edit the rds.properties file to match the ColdFusion context root, restart the application server, and re-open the ColdFusion Administrator.

    12. Open the ColdFusion Administrator to run the Configuration wizard.

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

    14. If using JRun, add the Log4J-1.2.12.jar file to the JRun server classpath. By default it is in the ColdFusion classpath.

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

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

      • filename: The directory path and file to display. The path is relative to the cfusion-war directory.

        For example, to display a CFM file located at /opt/jrun4/servers/myserver/cfusion-ear/cfusion-war/eisapp/index.cfm using the built-in JRun web server and a context root of cfusion, you specify the URL as http://localhost:8100/cfusion/eisapp/index.cfm.

    Installing an EAR file or WAR files in Mac OS X

    You can install the ColdFusion J2EE configuration for Mac OS X. If you are updating an existing deployment of ColdFusion 8 for J2EE, see Updating from an earlier version for J2EE before you continue.

    Install ColdFusion in Mac OS X (J2EE configuration)

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

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

    3. Review the Installation considerations for UNIX and Installation considerations for all platforms.

    4. Determine and record environment information, as described in Preparing to install using the J2EE configuration.

    5. Determine the answers to the questions in the section Gathering information necessary to install the J2EE configuration.

    6. Log in as root.

    7. 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 J2EE configuration platforms:

      • coldfusion-90-osx.zip - To install in Mac OS X.

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

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

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

      Note: For security reasons, it is crucial that you do not use root for the runtime user. Instead, use a nonprivileged user that does not have a login shell, such as the default user account nobody, which exists for this type of situation.

    11. Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see ColdFusion J2EE deployment and configuration.

      Note: If you deployed the rds.war file, and an error message indicates that RDS is not installed or not enabled, edit the rds.properties file to match the ColdFusion context root, restart the application server, and reopen the ColdFusion Administrator.

    12. Open the ColdFusion Administrator to run the Configuration wizard.

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

    14. If using JRun, add the Log4J-1.2.12.jar file to the JRun server classpath. By default it is in the ColdFusion classpath.

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

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

      • filename The directory path and file to display. The path is relative to the cfusion-war directory.

        For example, to display a CFM file located at /opt/jrun4/servers/myserver/cfusion-ear/cfusion-war/eisapp/index.cfm using the built-in JRun web server and a context root of cfusion, you specify the URL as http://localhost:8100/cfusion/eisapp/index.cfm.