User guide

18
INSTALLING COLDFUSION 9
Installing the J2EE Configuration
Last updated 1/20/2012
ColdFusion and J2EE application servers
One of the main advantages of ColdFusion is that you can install it as an integrated server (the server configuration)
or deploy it as a Java application on a standards-based J2EE application server (multiserver configuration and 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 in the J2EE configuration by using a J2EE application server, such as JRun 4 or IBM
WebSphere. When you use the J2EE configuration, you can use an existing J2EE application server; the installation
wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then deploy
by using the tools provided by your application server.
Choosing EAR or WAR deployment
In the J2EE environment, you deploy applications in one of the following formats:
Web application archive file Contains the ColdFusion application. A web application archive (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 must run from an expanded
directory structure:
cfusion (cfusion.war)
WEB-INF
web.xml
CFIDE
cfdocs
CFIDE (rds.war)
WEB-INF
web.xml
The cfusion.war file contains the ColdFusion web application. The rds.war file is a web application that redirects RDS
requests from /CFIDE to /context-root/CFIDE. It forwards requests to the ColdFusion Administrator when
ColdFusion uses a context root other than a forward slash (/).
Enterprise application archive file Contains the ColdFusion and RDS redirector web applications. An enterprise
application archive (also called an EAR) uses a directory structure that contains a META-INF/application.xml
deployment descriptor, which defines the web applications that 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 must run from an expanded directory structure:
ColdFusion Administrator password? ___________________________________________________
Whether to enable RDS? ___ Yes
___ No
Note: RDS allows the server to interact with remotely connected developers. Adobe
recommends that you disable RDS for production servers.
Disabling RDS also disables the directory browsing applets in the ColdFusion
Administrator.
RDS password? ___________________________________
Question Answer