Enabling Application Isolation - MACROMEDIA COLDFUSION MX 61 - CONFIGURING AND ADMINISTERING COLDFUSION MX Manual

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
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
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:
Create a separate server instance.
1
Deploy ColdFusion MX on the server instance.
2
option of the
-config
command, which specifies a customized
jrun
"Multihoming" on page

Enabling application isolation

65.
77