Contents > Configuring and Administering ColdFusion MX > Using Multiple Server Instances > Enabling application isolation

Enabling application isolation

When you install the J2EE version of ColdFusion MX Enterprise on top of JRun, you can use the JMC to create multiple server instances and deploy ColdFusion MX on each instance. This configuration provides multiple ColdFusion MX web applications in fully independent processes, with no shared ColdFusion or J2EE server resources. In this configuration, you typically have a single web server with multiple virtual hosts (or sites) and multiple server instances on one computer.

Note: Although this discussion describes using JRun 4, other J2EE application servers provide equivalent capabilities, and most of the concepts apply when deploying ColdFusion MX Enterprise on those J2EE servers.

Running independent applications this way has several advantages, including the following:

• Errors at the levels of the ColdFusion application or the JRun server do not affect any other ColdFusion applications.
• You can support multihomed servers, where a single web server supports multiple IP addresses or domain names, such as www.mycompany.com and services.anothercompany.com, each running out of a separate web root.
• Individual applications can use different JVM configurations, or even different JVM implementations. This feature is particularly useful if one application requires a particularly large Java heap. To specify customized JVM options, start the JRun server instance from the command line using the -config option of the jrun command, which specifies a customized jvm.config file. This is explained in the "Starting and stopping JRun servers" discussion in Installing JRun.

Note: These instructions describe creating multiple server instances on a single computer. To create multiple server instances on separate computers, each computer requires a separate license of ColdFusion MX Enterprise Edition.

To achieve complete application isolation, you use web-server-specific functionality to create a separate website for each application. Web servers have different terminology for this concept. For example, in IIS, you define separate websites (available in Windows server editions only) and in Apache, you create multiple virtual hosts.

These instructions apply when running ColdFusion MX on JRun. The principles apply when running ColdFusion MX on other J2EE application servers. However, not all J2EE application servers integrate with external web servers. For more information, see Multihoming.

These instructions assume that you deploy each application at the context root of /, which enables users to access CFM pages by specifying http://hostname/pagename.cfm. If other web applications are running in the server instance, another web application may already use the context root of / and you must deploy ColdFusion MX using a different context root, such as /cfusion, which requires that users access CFM pages by specifying http://hostname/cfusion/pagename.cfm. For more information on using a context root, see Installing and Using ColdFusion MX.

Note: Although cfusion is the context root, it does not relate to your web root directory structure and you still store CFM pages in the web root directory.

To use multiple server instances for application isolation:

1. Create a separate server instance.
2. Deploy ColdFusion MX on the server instance.
3. Open the ColdFusion MX Administrator on the server instance using the built-in web server (hostname:portnumber/CFIDE/administrator/index.cfm) and define the resources (such as data sources and Verity collections) required for the application. Performing this step also ensures that ColdFusion MX was deployed successfully.
4. Using your web-server-specific method, create a virtual website (or separate website) for the application.

   This is different for each web server; for more information, see Multihoming or consult your web server documentation.

5. Test each virtual website to ensure that HTML pages are served correctly.
6. Follow the instructions for your web server to configure the connection between your virtual website and the server instance. For more information, see Web server configuration for application isolation.
7. Store your application's CFM files in the web root of the virtual website.
8. Test your application using the virtual website.
9. Test the ColdFusion MX Administrator. If you configured your web server during installation, the CFIDE directory is under the original web root and you must copy it to each virtual website or create a web server mapping to the original CFIDE directory.
10. Repeat these steps for each server instance.

Contents > Configuring and Administering ColdFusion MX > Using Multiple Server Instances > Enabling application isolation

ColdFusion 9 | ColdFusion 8 | ColdFusion MX 7 | ColdFusion MX 6.1 | ColdFusion MX | Forums | Developer Center | Bug Reporting

Version 6.1

Comments are no longer accepted for ColdFusion MX 6.1. ColdFusion 8 is the current version.

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/coldfusion/6.1/htmldocs/cluster5.htm

Add Comment