Specifications

J2EE web applications running in a server are each rooted at a unique base URL, called a (orcontext root

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 with a context root of , you display the ColdFusioncf10

Administrator using the URL .http://localhost/_cf10_/CFIDE/administrator/index.cfm

Most J2EE application servers allow one application in each server instance to use a forward slash for the

context root. Setting the context root to / for the ColdFusion application is especially useful when serving CFM

pages from the web server, because it supports the functionality most similar to earlier ColdFusion versions.

In addition, the RDS web application is not required if you use a context root of /.

When you deploy the ColdFusion EAR file, it uses the context root that you specified when you ran the

installation wizard, which copied your specification to the element of thecontext-root

META-INF/application.xml file. When you deploy ColdFusion as a WAR file, you use

application-server-specific functionality to define the context root.

Multiple instances

When you use the J2EE configuration, you can define multiple server instances on a single computer, each

running ColdFusion. Running multiple instances of ColdFusion 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.

Platforms

Full ColdFusion functionality is available for Windows, Macintosh, Linux, and Solaris, except that the following

are Windows-specific: COM, .NET, and ODBC Services. AIX support is provided for WebSphere application

server only. Functionality provided by platform-specific binary files. is not available on AIX. Additionally, you

can install and deploy the all-Java ColdFusion J2EE configuration on other platforms, although without the

functionality provided by platform-specific binary files (C++ CFXs).

#back to top

Preparing to install using the J2EE configuration

Instead of JRun, Tomcat is embedded with a stand-alone ColdFusion 10 installation. Previous versions of

ColdFusion installer allow you to create multi-server installations whereas ColdFusion 10 installer lets you

only install stand-alone installation. After installing ColdFusion in stand-alone mode, you can create multiple

instances and clusters, provided you have an Enterprise or Developer license.

Note

This feature is not available in Standard Edition.

#back to top

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.