User guide

INSTALLING COLDFUSION 9

Installing the J2EE Configuration

Last updated 1/20/2012

servers easier; however, you can also configure ColdFusion on multiple servers manually by deploying EAR files and

WAR files on multiple server instances.

Platforms

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

Windows-specific: COM, .NET, and ODBC Services. If you install ColdFusion 9 in Mac OS® X, to use Verity you must

install the stand-alone version of Verity on a computer running a supported operating system, and then configure the

K2 Server page in the ColdFusion Administrator. 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).

Preparing to install using the J2EE configuration

When you install the J2EE configuration, you have the following options:

New installation—multiserver configuration Use this option to install a copy of JRun 4 with ColdFusion deployed and

configured as an enterprise application in a JRun server. For installation details, see

“Installing ColdFusion using the

multiserver configuration” on page 12. Adobe recommends this configuration option if JRun or another J2EE

application server is not already installed on the computer and you plan to use JRun 4 instead of another J2EE

application server.

New installation—create an EAR or WAR file Use 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” on page 20.

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 J2EE configuration must run from 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. For more information, see

“ColdFusion J2EE deployment and

configuration” on page 25.

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, expand the EAR/WAR file

manually, and then deploy the expanded directory structure, which becomes your working directory. For more

information, see

“ColdFusion J2EE deployment and configuration” on page 25.