Installing an EAR file or WAR files on UNIX

Installing an EAR file or WAR files on UNIX

This section explains how to install the ColdFusion MX 6.1 J2EE configuration on UNIX. If you are updating an existing deployment of ColdFusion MX for J2EE, see “Updating from ColdFusion MX for J2EE” before continuing.

By default, the ColdFusion MX 6.1 J2EE install places files into the /opt/cfmx directory. To install it into a different directory, you must create that directory before running the installation.

To install ColdFusion MX 6.1 on UNIX (J2EE configuration):

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

2 Make sure that your operating system meets the system requirements described in “System requirements for UNIX”

3 Review the “Installation considerations for UNIX”

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

5 Log in as root.

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

The installation files for supported server configuration platforms are as follows:

■ coldfusion-61-lin.bin

■ coldfusion-61-sol.bin

■ coldfusion-61-other.jar

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

8 Start the installation with the following command:

./<filename>

The installation program starts.

To use coldfusion-61-other.jar 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-61-other.jar

Note: To run the UNIX installer in GUI mode, type ./ -i gui

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

Caution: For security reasons, it is crucial that you do not use root for the runtime user.

After the Pre-Installation Summary, the files are copied to your computer.

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

For more information, see “ColdFusion MX J2EE deployment and configuration”

11 Open the ColdFusion MX Administrator in a browser (http://hostname:portnumber/contextroot/CFIDE/administrator/index.cfm). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.

12 Answer the questions asked by the Configuration Wizard. Completion of the Configuration Wizard and display of the ColdFusion MX Administrator indicate a successful install of ColdFusion MX.

Note: If you deployed the rds.war file, and a Configuration Wizard 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 MX Administrator.

13 Configure and manage your system, as described in Chapter 4, “Configuring Your System,”

14 Code and test ColdFusion MX 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, localhost, or 127.0.0.1.

■ portnumber The port number used by your application server’s web server.

■ contextroot The context root for the ColdFusion MX 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/default/cfusion-ear/cfusionwar/eisapp/index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://127.0.0.1:8100/cfmx/eisapp/index.cfm.

Installing an EAR file or WAR files

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 MX J2EE configuration must run out of 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.

• 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, you must expand the EAR/WAR file manually and then deploy the expanded directory structure, which becomes your working directory. The following discussions provide installation procedures for Windows and UNIX. For more about deployment and configuration, see “ColdFusion MX J2EE deployment and configuration”

Installing an EAR file or WAR files in Windows

This section explains how to install the ColdFusion MX 6.1 J2EE configuration in a Windows platform. If you are updating an existing deployment of ColdFusion MX for J2EE, see “Updating from ColdFusion MX for J2EE” before continuing.

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

To install ColdFusion MX 6.1 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.macromedia.com/go/proddoc_releasenotes.

2 Make sure that your operating system meets the system requirements described in “System requirements”

3 Review the “Installation considerations for Windows”

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

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

6 Insert the CD or download the setup file from the Macromedia website.

7 If the installation wizard does not start automatically when you insert the CD, locate setup.exe on the CD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion MX 6.1 installation executable file (coldfusion-61-win.exe) and double-click it. The installation wizard starts.

8 Follow the instructions in the wizard, and let it run to completion. After the Pre-Installation Summary pane, the files are copied to your computer.

9 Deploy ColdFusion MX 6.1 and configure Java settings, as required by your application server. For more information, see “ColdFusion MX J2EE deployment and configuration”

10 Open the ColdFusion MX Administrator in a browser (http://localhost:portnumber/contextroot/CFIDE/administrator/index.cfm). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.

11 Answer the questions asked by the Configuration Wizard. Completion of the Configuration Wizard and display of the ColdFusion MX Administrator indicate a successful install of ColdFusion MX.

12 Configure and manage your system, as described in Chapter 4, “Configuring Your System,”

13 Code and test ColdFusion MX 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, localhost, or 127.0.0.1.

■ portnumber The port number used by your application server’s web server.

■ contextroot The context root for the ColdFusion MX 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\default\cfusion-ear\cfusionwar\eisapp\index.cfm using the built-in JRun web server and a context root of cfmx, you

specify the URL as http://127.0.0.1:8100/cfmx/eisapp/index.cfm.

Installing an EAR file or WAR files on UNIX

This section explains how to install the ColdFusion MX 6.1 J2EE configuration on UNIX. If you are updating an existing deployment of ColdFusion MX for J2EE, see “Updating from ColdFusion MX for J2EE” before continuing.

By default, the ColdFusion MX 6.1 J2EE install places files into the /opt/cfmx directory. To install it into a different directory, you must create that directory before running the installation.

To install ColdFusion MX 6.1 on UNIX (J2EE configuration):

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

2 Make sure that your operating system meets the system requirements described in “System requirements for UNIX”

3 Review the “Installation considerations for UNIX”

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

5 Log in as root.

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

The installation files for supported server configuration platforms are as follows:

■ coldfusion-61-lin.bin

■ coldfusion-61-sol.bin

■ coldfusion-61-other.jar

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

8 Start the installation with the following command:

./<filename>

The installation program starts. To use coldfusion-61-other.jar 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-61-other.jar

Note: To run the UNIX installer in GUI mode, type ./ -i gui

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

Caution: For security reasons, it is crucial that you do not use root for the runtime user.

After the Pre-Installation Summary, the files are copied to your computer.

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

11 Open the ColdFusion MX Administrator in a browser (http://hostname:portnumber/contextroot/CFIDE/administrator/index.cfm). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.

12 Answer the questions asked by the Configuration Wizard.

Completion of the Configuration Wizard and display of the ColdFusion MX Administrator indicate a successful install of ColdFusion MX.

Note: If you deployed the rds.war file, and a Configuration Wizard 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 MX Administrator.

13 Configure and manage your system, as described in Chapter 4, “Configuring Your System,”

14 Code and test ColdFusion MX 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, localhost, or 127.0.0.1.

■ portnumber The port number used by your application server’s web server.

■ contextroot The context root for the ColdFusion MX 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/default/cfusion-ear/cfusionwar/eisapp/index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://127.0.0.1:8100/cfmx/eisapp/index.cfm.

Installing the J2EE configuration with JRun on UNIX

Installing the J2EE configuration with JRun on UNIX

This section explains how to install Macromedia JRun 4 and the ColdFusion MX 6.1 J2EE configuration on UNIX.

To install the J2EE configuration with JRun on UNIX:

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

2 Ensure that your operating system meets the system requirements described in “System requirements for UNIX”

3 Review the “Installation considerations for UNIX”

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

5 If you plan to configure an external web server, ensure that the web server is running.

6 Log in as root.

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

The installation files for supported server configuration platforms are as follows:

■ coldfusion-61-lin.bin

■ coldfusion-61-sol.bin

■ coldfusion-61-other.jar

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

9 Start the installation with the following command:

./<filename>

The installation program starts.

Note: To run the UNIX installer in GUI mode, type ./ -i gui

10 Follow the instructions in the installation wizard. Make sure that you select Install New Version of ColdFusion MX, then J2EE Configuration (ColdFusion MX with JRun 4).

Tip: The installation wizard disables the ColdFusion MX with JRun 4 option if JRun 4 is already installed on the computer.

Caution: For security reasons, it is crucial that you do not use root for the runtime user.

After the Pre-Installation Summary pane, the files are copied to your computer.

11 Start the JRun cfusion server:

jrun_root/bin/jrun start cfusion

12 If you specified external web server settings when running the installation wizard, run the jrun_root/bin/cfmx-connectors.sh shell script. The script runs the Web Server Configuration Tool, which configures the web server for use with ColdFusion MX. The web server should also be running. If there are problems running this script, review the configuration and bin directory specifications, modify as necessary, and rerun the script. You can also configure your web server using the scripts in jrun_root/bin/connectors, or through java –jar jrun_root/lib/wsconfig.jar, as appropriate.

Note: This step is important, because if you specified the use of an external web server when running the installation wizard, the CFIDE and cfdocs directories are placed under that web server’s root directory, and you must successfully configure the web server before opening the ColdFusion MX Administrator.

13 Open the ColdFusion MX Administrator in a browser, using http://localhost/contextroot/CFIDE/administrator/index.cfm (external web server) or http://localhost:8300/contextroot/CFIDE/administrator/index.cfm (built-in JRun web server). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.

Note: If you are accessing ColdFusion MX 6.1 from a remote computer, use the previous URL with the host name or IP address of the remote computer instead of localhost.

14 Answer the questions asked by the Configuration Wizard.

Completion of the Configuration Wizard and display of the ColdFusion MX Administrator indicates a successful install of ColdFusion MX.

15 Configure and manage your system, as described in Chapter 4, “Configuring Your System,”

16 Code and test ColdFusion MX CFM pages. If you configured an external web server, store CFM pages under your web root directory. If you are using the built-in web server, store CFM pages under the web application root (jrun_root/servers/cfusion/cfusion-ear/cfusion-war) and

access these pages using a URL of the form http://hostname:8300/context-root/filename.cfm, as follows:

■ hostname The machine name, IP address, localhost, or 127.0.0.1.

■ contextroot The context root for the ColdFusion MX 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/cfusion/cfusion-ear/cfusionwar/eisapp/index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://127.0.0.1:8300/cfmx/eisapp/index.cfm.

Installing the J2EE configuration with JRun

Installing the J2EE configuration with JRun

When deploying ColdFusion MX as an enterprise application and installing JRun 4 as part of the installation procedure, the installation wizard performs the following actions:

• Installs JRun 4.

• Creates a JRun server named cfusion (in addition to the default, admin, and samples JRun servers, which are part of the default JRun installation).

• (Windows) Creates and starts Windows services for the admin, default, and cfusion JRun servers.

• Deploys the ColdFusion MX EAR in the JRun cfusion server.

• Configures jrun_root/bin/jvm.config, as appropriate for the platform.

• (Optional) Configures the JRun cfusion server for use with an external web server. In Windows, the installation wizard runs the Web Server Configuration Tool. On UNIX, the installation wizard creates a shell script that you can run to execute the Web Server Configuration Tool with the settings specified in the installation wizard.

Note: The default JRun web server port for the cfusion server is 8300.

Installing the J2EE configuration with JRun in Windows This section explains how to install Macromedia JRun 4 and the ColdFusion MX 6.1 J2EE

configuration in a Windows platform.

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

To install the J2EE configuration with JRun in Windows:

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

2 Make sure that your operating system meets the system requirements described in “System requirements”

3 Review the “Installation considerations for Windows”

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

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

6 If you plan to configure an external web server, ensure that the web server is running.

7 Insert the CD or download the setup file from the Macromedia website.

8 If the installation wizard does not start automatically when you insert the CD, locate setup.exe on the CD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion MX 6.1 installation executable file (coldfusion-61-win.exe) and double-click it. The installation wizard starts.

9 Follow the instructions in the installation wizard. Be sure to start by selecting Install New Version of ColdFusion MX, then J2EE Configuration (ColdFusion MX with JRun 4).

Tip: The installation wizard disables the ColdFusion MX with JRun 4 option if JRun 4 is already

installed on the computer.

After the Pre-Installation Summary pane, the files are copied to your computer.

10 Open the ColdFusion MX Administrator in a browser, using http://localhost/contextroot/CFIDE/administrator/index.cfm (external web server) or http://localhost:8300/contextroot/CFIDE/administrator/index.cfm (built-in JRun web server). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.

Note: If you are accessing ColdFusion MX 6.1 from a remote computer, use the previous URL with the host name or IP address of the remote computer instead of localhost.

11 Answer the questions asked by the Configuration Wizard.

Completion of the Configuration Wizard and display of the ColdFusion MX Administrator indicates a successful install of ColdFusion MX.

12 Configure and manage your system, as described in Chapter 4, “Configuring Your System,”

Tip: If you do not plan on using the default JRun server, you can conserve system resources by opening the Services control panel and setting the Macromedia JRun default server service to Manual or Disabled.

13 Code and test ColdFusion MX CFM pages. If you configured an external web server, store CFM pages under your web root directory. If you are using the built-in web server, store CFM pages under the web application root (jrun_root/servers/cfusion/cfusion-ear/cfusion-war) and access these pages using a URL of the form http://hostname:8300/context-root/filename.cfm, as

follows:

■ hostname The machine name, IP address, localhost, or 127.0.0.1.

■ contextroot The context root for the ColdFusion MX 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\cfusion\cfusion-ear\cfusionwar\eisapp\index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://127.0.0.1:8300/cfmx/eisapp/index.cfm.

J2EE application servers

J2EE application servers

One of the main advantages of ColdFusion MX is that it can be installed as an integrated server (the server configuration) or deployed as a Java application on a standards-based J2EE application server (the J2EE configuration). In addition to greater flexibility, this allows your ColdFusion applications to leverage features of the J2EE architecture, such as support for multiple application instances and multiple-instance clustering.

You can deploy ColdFusion MX in the J2EE configuration using either the bundled copy of Macromedia JRun 4 or a third-party J2EE application server. If you use the bundled version of JRun (recommended), the installation wizard automatically deploys and configures ColdFusion MX 6.1 on its own JRun server. If you choose to use a third-party J2EE application server, the installation wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then deploy using the tools provided by your chosen application server. Choosing EAR or WAR deployment

In the J2EE environment, you deploy applications in one of the following formats:

• Web application Contains the ColdFusion MX application. A web application (also called a WAR) uses a directory structure that contains a WEB-INF/web.xml deployment descriptor, which defines the servlets and context parameters it uses. J2EE application servers can deploy web applications in this directory structures as-is or in compressed WAR files that contain these directory structures. However, ColdFusion MX must run out of an expanded directory structure.

cfusion (cfusion.war)

WEB-INF

web.xml

CFIDE

cfdocs

CFIDE (rds.war)

WEB-INF

web.xml

Cfusion.war contains the ColdFusion MX web application. Rds.war is a web application that redirects requests from /CFIDE to /context-root/CFIDE. It forwards requests to the ColdFusion MX Administrator when ColdFusion MX uses a context root other than /.

• Enterprise application Contains the ColdFusion MX and RDS redirector web applications.

An enterprise application (also called an EAR) uses a directory structure that contains a META-INF/application.xml deployment descriptor, which defines the web applications it contains. J2EE application servers can deploy enterprise applications in these directory structures as-is or in compressed EAR files that contain these directory structures. However, ColdFusion MX must run out of an expanded directory structure.

cfusion-ear

META-INF

application.xml

cfusion-war

WEB-INF

web.xml

CFIDE

cfdocs

rds.war

WEB-INF

web.xml

If your J2EE application server supports enterprise applications, you should install and deploy the

EAR file. For more information, see “Installing an EAR file or WAR files”

Note: The instructions in this chapter apply to the ColdFusion MX J2EE configuration. The ColdFusion MX server configuration contains an embedded version of JRun, which uses ColdFusion-specific JRun configuration options and mappings. For information on installing ColdFusion MX in the server configuration, see Chapter 2, “Installing the Server Configuration,”

Context root

Because the J2EE environment$ supports multiple, isolated web applications running in a server instance, J2EE web applications running in a server are each rooted at a unique base URL, called

a context root (or context path). The J2EE application server uses this initial portion of the URL (that is, the portion immediately following http://hostname) to determine which web application services an incoming request.

For example, if you are running ColdFusion MX with a context root of cfmx, you display the ColdFusion MX Administrator using the URL http://localhost/cfmx/CFIDE/administrator/index.cfm.

Most J2EE application servers allow one application in each server instance to use / (forward slash) for the context root. Setting the context root to / for the ColdFusion MX application is especially useful when serving CFM pages from the web server because it supports the functionality most similar to previous ColdFusion releases. In addition, the RDS web application is not required if you use a context root of /.

When you deploy the ColdFusion MX EAR file, it uses the context root specified when you ran the installation wizard (which copied your specification to the context-root element of the META-INF/application.xml file). When you deploy ColdFusion MX as a WAR file, you use application-server-specific functionality to define the context root.

Note: Each web application running in a server instance must have a unique context root. The JRun default web application uses / for a context root so if you want to use / for the ColdFusion MX context root when deploying on JRun, you must either delete the default-war application or change the default-war context root by editing the default-ear/META-INF/application.xml file.

Multiple instances

When using the J2EE configuration, you can define multiple server instances on a single computer, each running ColdFusion MX. Running multiple instances of ColdFusion MX has the following advantages:

• Application isolation You deploy an independent application to each server instance. Each server instance has separate settings, and because each server instance runs in its own instance

of the JVM, problems encountered by one application have no effect on other applications.

• Load balancing and failover You deploy the same application to each server instance and add the instances to a cluster. The web server connector optimizes performance and stability by automatically balancing load and by switching requests to another server instance when a server instance stops running.

For more information on configuring ColdFusion MX on multiple server instances, including detailed information for configuring multiple server instances when running on JRun 4, see Configuring and Administering ColdFusion MX.

Platforms

Full ColdFusion MX functionality is available on Windows, Linux, and Solaris. Additionally, you can install and deploy the all-Java ColdFusion MX J2EE configuration on other platforms, although without the functionality provided by platform-specific binary files (Verity and C++ CFXs).

Preparing to install using the J2EE configuration

This section provides installation instructions for the ColdFusion MX J2EE configuration. When installing the J2EE configuration, you have the following options:

• New installation – install JRun 4 Select this option to install a copy of Macromedia JRun 4 with ColdFusion MX deployed and configured as an enterprise application in a JRun server. For installation details, see “Installing the J2EE configuration with JRun”. This is the recommended J2EE configuration option if JRun or another J2EE application server is not already installed on the computer.

• New installation – create EAR or WAR Select this option if you already have a J2EE application server running on the computer. The installation wizard creates an EAR file or two WAR files, which you deploy using J2EE application server-specific tools or utilities. For installation details, see “Installing an EAR file or WAR files”.

• Update existing ColdFusion MX – redeploy existing EAR or WAR Select this option if ColdFusion MX is already deployed in a J2EE application server running on the computer. With this option, the installation wizard backs up ColdFusion MX settings, backs up CFM pages, and creates and EAR file or two WAR files. You undeploy the current ColdFusion MX application, deploy ColdFusion MX 6.1, and copy the saved settings from the backup directory. For installation details, see “Installing an EAR file or WAR files”.

Note: Migration from ColdFusion 4.5 or 5 to the ColdFusion MX J2EE configuration is not supported. In addition, the J2EE configuration is not supported by ClusterCATS.

Using the built-in web server

Using the built-in web server

ColdFusion MX 6.1 has its own web server that you can use to develop ColdFusion MX applications, without depending on an external web server, such as Internet Information Server (IIS), Apache, or iPlanet. Macromedia does not recommend using the built-in web server in a production environment. However, it is more than suitable for development, allowing you to create virtual directories and set the default document (for example, default.cfm or index.cfm). During the ColdFusion MX 6.1 installation, you must choose a web server. If you select the builtin server, then your web root directory is located in the cf_root/wwwroot directory. By default, the web server runs on port 8500. This means that to display a page in your application, you must append :8500 to the host name or IP address in the URL; for example, http://localhost:8500/YourApp1/index.cfm. (If the page still does not display, make sure that the document is located in the built-in web server’s web root directory; for example, C:\CFusionMX\wwwroot\YourApp1\index.cfm.) Switching the port for the built-in web server You can change the default port on which the built-in web server runs.

To change the default port for the built-in web server:

1 Back up the jrun.xml file.

This file is in the cf_root\runtime\servers\default\SERVER-INF directory in Windows, and in the cf_root/runtime/servers/default/SERVER-INF directory on UNIX.

2 Open the original jrun.xml file for editing.

3 Change the port number specified in the WebService port attribute (near the bottom of the file):

8500

*

false

Note: Make sure that the deactivated attribute is set to false.

4 Save the file.

5 Restart ColdFusion MX.

Switching from another web server

You can switch from an external web server to the built-in ColdFusion MX web server without reinstalling, even if you did not select it during installation.

To switch from an external web server to the built-in web server:

1 Back up the jrun.xml file.

This file is in the cf_root\runtime\servers\default\SERVER-INF directory in Windows, and in the cf_root/runtime/servers/default/SERVER-INF directory on UNIX.

2 Open the original jrun.xml file for editing.

3 Locate the WebService service and set the deactivated attribute to false:

8500

*

false

4 Locate the ProxyService service and set the deactivated attribute to true:

8

1

1000

0

20

500

true

...

5 Save the file.

6 Copy the CFM pages in your web root directory (including the CFIDE and cfdocs directories) to the ColdFusion MX cf_root/wwwroot directory, and use appropriate URL references (for example, http://localhost:8500/YourApp1/index.cfm). If you switch from the built-in web server to an external web server, you must copy the contents of the cf_root/wwwroot directory to your web server root.

7 Restart ColdFusion MX.

To switch to another web server, follow the instructions for the appropriate web server on your platform in Chapter 4, “Configuring web servers,”

Note: The installation wizard does not allows you to configure both an external web server and the

built-in web server and in most cases, you do not enable both the built-in web server and an external

web server. If you do, you must create web server directory mappings so that both web servers use

the same web root.

Uninstalling ColdFusion MX 6.1

The steps for uninstalling ColdFusion MX 6.1 depend on your operating system. This section contains instructions for Windows and UNIX.

Uninstalling ColdFusion MX 6.1 from Windows

Uninstalling ColdFusion MX 6.1 deletes all program files and related components from your

computer.

To uninstall ColdFusion MX 6.1 from Windows:

1 Select Start > Settings > Control Panel > Add/Remove Programs >

Macromedia ColdFusion MX.

2 Uninstall ColdFusion MX.

3 When the program completes, remove any remaining files and directories in the cf_root

directory.

4 In some cases, the uninstall program may require that you restart the computer.

ColdFusion MX 6.1 is deleted from your server.

Uninstalling ColdFusion MX 6.1 from UNIX

Uninstalling ColdFusion MX 6.1 deletes all program files and related components from your

computer.

To uninstall ColdFusion MX 6.1 from UNIX:

1 Log in as root.

2 Enter the following command to go to the cf_root/uninstall directory:

cd cf_root/uninstall

3 Enter the following command:

./uninstall.sh

4 When the program completes, remove any remaining files and directories in the cf_root directory. ColdFusion MX 6.1 is deleted from your server.