Macromedia ColdFusion - 10.0 Installation Manual

Download

Installing

ADOBE®

COLDFUSION

Legal notices

For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html.

Last updated 7/9/2012

Chapter 1: Preparing to Install ColdFusion

About the ColdFusion installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Installing ColdFusion 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2: Installing the Server Configuration

Gathering information necessary to install the server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Installing ColdFusion using the server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

ColdFusion installation directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Using the built-in web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring the built-in web server (Tomcat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Starting, stopping, and restarting ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Editing the JVM settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Creating and editing a new ColdFusion instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Registering a remote instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Adding start and stop functionality to a remote instance over HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Setting up remote start and stop functionality using HTTPS in Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Setting up remote start and stop functionality using HTTP in Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Managing clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Adding a remote instance to a cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Configuring other web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Configuring Secured Socket Layer (SSL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Changing virtual directory and the doc root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Changing the connector port for cfstat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Enabling Search Engine Safe URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Enabling Secure Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Changing the log rotation settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Enabling persistent session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Updating from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Uninstalling ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

iii

Chapter 3: Installing the J2EE Configuration

Gathering information necessary to install the J2EE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

ColdFusion and J2EE application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Preparing to install using the J2EE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing an EAR file or WAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Updating from an earlier version for J2EE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

ColdFusion J2EE deployment and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Undeploying ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 4: Installing Integrated Technologies

Integrated Adobe and third-party technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing Dreamweaver extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Installing Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Contents

Installing Solr search server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Enabling Flash Remoting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Installing Flash Remoting Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Installing the ColdFusion .NET Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Configuring OpenOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 5: Configuring Your System

Overview of configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Managing ColdFusion services in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Managing the ColdFusion process in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Managing the ColdFusion process in Mac OS X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Enabling CORBA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Disabling Remote Development Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Disabling JSP functionality (server configuration only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Changing the ColdFusion user account in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

Chapter 6: Troubleshooting

Common installation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Data source problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Migration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

J2EE configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Postinstallation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Uninstall problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Last updated 7/9/2012

Chapter 1: Preparing to Install ColdFusion

Important: This copy of the installation documentation available on the DVD may be dated, to access the latest documentation, see

Before installing Adobe ColdFusion 10, review the ColdFusion product editions, system requirements, and other highlevel considerations.

About the ColdFusion installation

ColdFusion provides a powerful and flexible installation and upgrade process. The ColdFusion installation process includes the following phases:

1 Plan the installation by determining your installation, configuration, and upgrade options.

2 Run the ColdFusion installer.

3 (J2EE configuration only) Deploy and configure ColdFusion on your J2EE application server.

The ColdFusion installation process supports the following scenarios:

ColdFusion Help.

New installation Install ColdFusion on a computer with no earlier ColdFusion installation.

Upgrade installation You can upgrade from ColdFusion 8 or ColdFusion 9. When upgrading, the installer

preserves the existing settings and installs in a new directory, automatically assigning ports that do not conflict with the existing installation.

You can install ColdFusion 10 in any of the following configurations:

Server configuration Lets you install ColdFusion 10 with an embedded JEE server. This was formerly known as the

stand-alone configuration. For enterprise and developer licenses, you can create and manage new ColdFusion instances. For information on installing the server configuration, see page 4.

Note: ColdFusion 10 does not offer a separate multi-server mode of installation.

J2EE configuration (Enterprise Edition only) Lets you deploy ColdFusion 10 as a Java application running on a Java

2 Enterprise Edition (J2EE) application server, using a third-party J2EE server, such as IBM WebSphere or Oracle WebLogic. When you use the J2EE configuration, you can deploy ColdFusion 10 multiple times on a single computer. For information on installing the J2EE configuration, see page 22.

“Installing the Server Configuration” on

“Installing the J2EE Configuration” on

Installing ColdFusion 10

ColdFusion 10 product editions

The ColdFusion 10 product editions are available on the Adobe website. To view the product editions, go to

www.adobe.com/go/learn_cfu_cfeditions_en.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Preparing to Install ColdFusion

System requirements

The ColdFusion 10 system requirements are available on the Adobe website. To view the system requirements, including a list of supported J2EE application servers, see

www.adobe.com/go/learn_cfu_cfsysreqs_en.

Installation considerations

Before installing ColdFusion 10, review the considerations for installing or upgrading on your platforms.

Note: To use VisiBroker for CORBA connections in ColdFusion, see “Enabling CORBA support” on page 59.

• ColdFusion 10, ColdFusion 9, and ColdFusion 8 can coexist on the same system.

• In the case of ColdFusion cluster setup, any changes to the cluster settings, for example, adding a new member, or

changing member port (in the ColdFusion Administrator) causes web server restart. This may result in page time-out.

Refresh the page to resolve this issue.

• If ColdFusion uninstaller is not able to remove the connector for Apache (for example, in the case of Mac OS X),

do the following to manually remove it:

1 Delete the mod_jk.conf found in {apache_install_location}/conf/ directory.

2 Delete {cfroot}/config/wsconfig/1 folder which has the Apache connector file, mod_jk.so.

3 Remove the following line from {apache_install_location}/conf/httpd.conf file:

Include "{apache_install_location}\conf\mod_jk.conf".

4 Delete the file {apache_install_location}\conf\mod_jk.conf

• From the ColdFusion Administrator, when you wish to start multiple instances, start the cfusion instance first,

and then start the other instances..

• When you run the ColdFusion uninstaller, the logs folder (ColdFusion_Home/cfusion/) is deleted.

• When you install ColdFusion, you can install the Administrator Component to start and stop remote server.

Use the Remote Instance Administrator Component credentials to remotely start/stop the server from applications such as Server Manager, Instance Manager in ColdFusion Administrator, or ColdFusion Builder.

• J2EE deployment of ColdFusion EAR or WAR on JRun is not supported. The EWS.jar must be present in the

systemclasspath while deploying on a J2EE server.

Installation considerations for all platforms

The following are installation considerations for all platforms:

Installation considerations for Windows

The following installation considerations are for Windows systems only:

• Do not configure the server running ColdFusion as a Primary Domain Controller (PDC) or Backup Domain

Controller (BDC). Adobe follows the Microsoft network model, in which the first level is the PDC or BDC. These systems only manage the network or domain and are not designed to run application servers. ColdFusion should reside on the second level of Microsoft Windows stand-alone systems. Stand-alone servers can participate in a network or domain.

• Microsoft Windows XP handles only ten incoming TCP/IP connections concurrently. Therefore, Adobe does not

recommend using this operating system in a production environment; use Microsoft Windows 2003 Server and Windows 2008 Server instead.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Preparing to Install ColdFusion

Installation considerations for UNIX

The following are installation considerations for UNIX systems only:

• For troubleshooting purposes, the installer creates the following log file during an installation or upgrade in UNIX:

cf_root/Adobe_ColdFusion_10_InstallLog.log. If you contact AdobeTechnical Support for installation support, send them this file.

• If you are deploying the J2EE configuration on a platform other than Linux or Solaris, use the

ColdFusion_10_WWEJ_java.jar. This Java-only installer does not include features that require platform-specific binary files, such as C++ CFX support.

Last updated 7/9/2012

Chapter 2: Installing the Server Configuration

The ColdFusion server configuration contains an embedded copy of Tomcat and is most similar to earlier versions of ColdFusion.

Note: The cf_root directory refers to your installation directory. By default, this directory is C:\ColdFusion10 in Windows, and /opt/coldfusion10 in UNIX.

Gathering information necessary to install the server configuration

Although the ColdFusion 10 installer provides an intuitive interface, it helps to plan your answers to the questions asked by the installer. Use the following tables to help plan for installing the server configuration of ColdFusion 10.

Question Answer

Platform-specific installer name? ___________________________________________________

Serial number for ColdFusion? ___________________________________________________

Type of installation? ___ Server configuration

___ J2EE configuration

Subcomponents to install? ___ ColdFusion 10 ODBC Services

___ ColdFusion 10 Solr Services

___ Admin Component for Remote Start and Stop

___ .NET Integration Services

___ ColdFusion 10 Documentation

ColdFusion installation directory? ___________________________________________________

Configure web server or use built-in web server? ___ Configure web server for ColdFusion

___ Enable ColdFusion built-in web server

Web server to configure? (Only if you do not use the built-in web server.)

Configuration directory? (Apache and Sun Java Web Server)

___ IIS

___ Apache

___ SunJWS

___ Other

___________________________________________________

Enable Secure Profile ___Yes

___No

Identify a list of IP addresses that will have access to the ColdFusion Administrator.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Question Answer

Configure OpenOffice ___Yes

___No

Path to server binary? (Apache) ___________________________________________________

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? ___________________________________

Automatically check for server updates? ___Yes

___No

Installing ColdFusion using the server configuration

Once you have determined the answers to the questions in the section “Gathering information necessary to install the

server configuration” on page 4, you can install the ColdFusion server configuration in Windows or UNIX, as

applicable.

Installing ColdFusion server configuration in Windows or MAC

Note: (Windows only) The Windows installer requires a computer that supports at least 256 colors.

Install ColdFusion in Windows or MAC

1 Read the online version of the Release Notes for any late-breaking information or updates. For more information,

www.adobe.com/go/learn_cfu_releasenote_en.

see

2 Ensure that your operating system meets the system requirements described on the Adobe website at

www.adobe.com/go/learn_cfu_cfsysreqs_en.

3 Review “Installation considerations for Windows” on page 2 and “Installation considerations for all platforms” on

page 2.

4 Determine the answers to the questions in the table in “Gathering information necessary to install the server

configuration” on page 4.

5 Close any applications that are currently running on your computer.

6 If you plan to configure an external web server, ensure that the web server is running.

7 Insert the DVD or download the setup file from the Adobe website.

8 If the installation wizard does not start automatically when you insert the DVD, locate the appropriate installer file

on the DVD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion installer Windows only: coldfusion_10_WWEJ_win32.exe/coldfusion_10_WWEJ_win64.exe and double-click it.MAC only:Extract the coldfusion_10_WWEJ_osx10.dmg file and double-click the installer.

9 Follow the instructions in the installation wizard, and let it run to completion.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

10 Click OK to open the ColdFusion Administrator and configure the server.

11 To install any other integrated Adobe or third-party technologies, see “Installing Integrated Technologies” on

page 46.

12 Configure and manage your system, as described in “Configuring Your System” on page 52.

13 To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the

Resources page of the ColdFusion Administrator.

Installing the ColdFusion server configuration in UNIX

By default, ColdFusion installs into the /opt/coldfusion10 directory. You can also choose to install ColdFusion 10 in a different directory.

Note: The default user is nobody for the UNIX installer running ColdFusion.

Install the ColdFusion server configuration in UNIX

1 Read the online version of the Release Notes for any late-breaking information or updates. For more information,

www.adobe.com/go/learn_cfu_releasenote_en.

see

2 Ensure that your operating system meets the system requirements described on the Adobe website at

www.adobe.com/go/learn_cfu_cfsysreqs_en.

3 Review “Installation considerations for UNIX” on page 3 and “Installation considerations for all platforms” on

page 2.

4 Determine the answers to the questions in the section “Gathering information necessary to install the server

configuration” on page 4.

5 If you plan to configure an external web server, ensure that the web server is running.

6 Log in as root.

7 Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save

it to a directory on your local disk.

The following installation files are those for the supported server configuration platforms:

Platform File

Linux

• ColdFusion_10_WWEJ_linux32.bin (for 32-bit systems)

• ColdFusion_10_WWEJ_linux64.bin (64-bit systems)

Solaris ColdFusion_10_WWEJ_solaris64.bin

8 Using the cd command, go to the directory that contains the installation file.

9 Ensure that you have executable permission for the installation file. You can change permissions on the file by using

the following command:

chmod 777 ColdFusion_10_WWEJ_solaris64.bin

10 Start the installation with the following command:

./<filename>

Note: To run the Linux installer in GUI mode, type ./<filename> -i gui.

11 Follow the prompts in the installation program, and let it run to completion.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Note: For security reasons, it is crucial that you do not use root for the runtime user.

12 Start ColdFusion with the following command:

/cf_root/cfusion/bin/coldfusion start

If you specified the use of an external web server when you ran the installer, ColdFusion automatically runs the cf_root/cfusion/bin/cf-connectors.sh script when it starts the first time. This shell script runs the Web Server Configuration Tool by using the settings that you specified during the installation. If there are problems running this script, review the configuration and bin directory specifications, modify as necessary, and rerun the script. You can also configure your web server by using the scripts in cf_root/cfusion/bin/connectors, as appropriate.

To stop ColdFusion, use the following command:

/cf_root/cfusion/bin/coldfusion stop

For more information on managing processes, see “Managing the ColdFusion process in UNIX” on page 53.

13 Open ColdFusion Administrator to run the Configuration wizard.

14 Configure and manage your system, as described in “Configuring Your System” on page 52.

15 To install any other integrated Adobe or third-party technologies, see “Installing Integrated Technologies” on

page 46.

16 To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the

Resources page of the ColdFusion Administrator.

ColdFusion installation directory structure

By default, ColdFusion10 is your installation directory. The following table describes the directory structure:

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Directory Description

cfusion Contains the following directories:

• bin: Programs for starting, stopping, and viewing information for ColdFusion, and to run Crystal Reports (Windows

only). It also contains the password reset scripts for server administrator and Admin Component for remote server start and stop.

• cache: Repository for temporary files from ColdFusion.

• cfx: Sample C++ and Java CFX files with their supporting files. You can also store your CFX files in this directory

(although you can put them in any location that is defined in your classpath).

• charting: Files for the ColdFusion graphing and charting engine.

• CustomTags: Repository for your custom tags

• db: The sample Apache Derby databases for all platforms.

• gateway: Files for ColdFusion event gateways.

• jetty: Solr configuration files and files related to remote instance start and stop.

• jintegra: (Applies only to Windows) JIntegra programs, libraries, and other supporting files (for example, to integrate

Java and COM code; manage access to ActiveX controls (OCXs) that are hosted in a graphical user interface (GUI) container; and register the JVM and type libraries). (Applicable only for Windows.)

• jnbridge: Files for .NET Integration Services.

• lib: JAR, XML, property, and other files that are the foundation of ColdFusion, for functionality such as queries,

charting, mail, security, Solr, and system probes.

• logs: Repository for ColdFusion log files. JRE-specific log files are in the runtime/logs directory. Console outputs are

logged in to

coldfusion-out.log instead of cfserver.log.

• Mail: Repository for spooled mail and mail that cannot be delivered.

• META-INF: XML metadata for the ColdFusion Administrator.

• MonitoringServer: Contains crossdomain.xml used for multi-server monitoring.

• registry: (UNIX only) Flat file to store registry settings

• runtime: Programs and supporting files for the ColdFusion runtime. Also, contains the Tomcat libraries. The conf

directory in runtime contains all Tomcat configuration files.

• stubs: web services.

• wwwroot: Default web root directory for the built-in web server. When running on other web servers, this directory

contains the CFIDE and WEB-INF directories; do not remove this directory.

config Contains instances.xml and connector configuration files. Also, contains cluster configuration file, cluster.xml.

jre Java runtime files.

uninstall Files to uninstall ColdFusion.

Modifications to the directory structure

The following table shows the directories in ColdFusion 9 and the corresponding ones in ColdFusion 10:

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

ColdFusion 9 ColdFusion 10

cfroot cfusion

ColdFusion9\runtim e\jre

ColdFusion9\uninst all

ColdFusion9\runtim e\lib\wsconfig

ColdFusion10\jre

ColdFusion10\uninstall

ColdFusion10\config\wsconfi g

Note: The ColdFusion_install\cfusion\bin directory contains the Jvm.config file.

Using the built-in web server

ColdFusion provides in-built Tomcat application server that you can use to develop ColdFusion applications.

During the ColdFusion installation, choose a web server. If you select the built-in web server, your web root directory is located in the cfroot/wwwroot directory. By default, the web server runs on port 8500. It means that to display a page in your application, append: http://localhost:8500/YourApp1/index.cfm. If the page does not appear, ensure that the document is located in the built-in web server’s web root directory; for example, C:\ColdFusion10\cfusion\wwwroot\YourApp1\index.cfm.

Note: If port 8500 is in use, the installer checks up to 100 ports (starting with 8501) to find a port that is not used. ColdFusion uses that port and displays a message to indicate the selected port.

If you select an external web server during installation, the built-in web server is deactivated.

8500 to the host name or IP address in the URL; for example,

Change the port of the built-in web server

1 Back up the server.xml file.

This file is in the cfroot\cfusion\runtime\conf directory.

2 Open the original server.xml file for editing.

3 Search for internal webserver start. Update the port number.

<Connector executor="tomcatThreadPool"

port="8500" protocol="org.apache.coyote.http11.Http11NioProtocol" connectionTimeout="20000" redirectPort="8445"/>

4 Save the file and then restart ColdFusion.

Configuring the built-in web server (Tomcat)

While installing, if you have configured ColdFusion on an external web server, do the following to configure ColdFusion on in-built Tomcat:

1 Open the cfroot\cfusion\runtime\conf\server.xml file.

2 Search for internal webserver start. Uncomment the following connector XML.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

<Connector executor="tomcatThreadPool"

port="8500" protocol="org.apache.coyote.http11.Http11NioProtocol" connectionTimeout="20000" redirectPort="8445"/>

3 Save the file, and then restart ColdFusion.

Note: To enable OS Symbolic links after switching to Tomcat, edit the context.xml file found in

/cfusion/runtime/conf/ to add allowLinking="true" attribute to the context element.

Starting, stopping, and restarting ColdFusion

On Windows

❖ At prompt, go to the directory cfroot\cfusion\bin and run the following command: coldfusion.exe -start -

console.

To stop ColdFusion, use the command coldfusion.exe -stop -console. To restart, use the command

coldfusion.exe -restart -console.

Alternatively, you could also start, stop, and restart ColdFusion server using Windows Services.

Note: Paused tasks misfire when restarting ColdFusion.

Note: As possible in previous versions of ColdFusion, you can also use the cfstart script to start/stop the ColdFusion sever.

Note: The -console argument is optional. If it is not provided, the logs are saved in the cfroot\cfusion\logs

directory.

On UNIX/Linux/Solaris/MAC OSX

❖ At prompt, go to the directory cfroot\cfusion\bin and run the following command: ./coldfusion start

To stop ColdFusion, use the command ./coldfusion stop. To restart, use the command ./coldfusion

restart.

Note: Paused tasks misfire when restarting ColdFusion.

Note: Use the status command to find the status of ColdFusion server.

Editing the JVM settings

To edit the JVM settings, open the cfroot\cfusion\bin\jvm.config file and update the following details:

• java.home: Java home. If not set, ColdFusion verifies the default JRE in the cfroot\jre folder, in the registry, or

AVA_HOME environment variable.

in the J

• java.args: Settings for -Xmx, ColdFusion classpath, and so on.

• java.library.path: Settings for library path.

• java.class.path: Additional classpath settings in a comma-separated list.

• application.home: Default is cfroot\cfusion

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Creating and editing a new ColdFusion instance

After installing ColdFusion in stand-alone mode, create an instance of ColdFusion using the ColdFusion Administrator.

1 In the ColdFusion Administrator, go to Enterprise Manager > Instance Manager.

2 Click Add New Instance.

3 Enter the server name and server directory.

4 (Optional) Check Create Windows Service.

5 Click Submit.

In the Instance Manager, start, stop, restart, delete, access website, or access administrator.

6 Click the Edit icon to edit the instance manager.

7 Edit the internal webserver port and load balancing factor.

Load balancing factor represents the load the instance takes up. Load balancing factor is applicable only if the instance is part of the cluster.

For example, the load balancing factor for the first instance is 1 and that of the second instance is 2. The second instance receives two times more requests.

8 Click Submit.

Registering a remote instance

1 In the ColdFusion Administrator, click Enterprise Manager > Instance Manager > Register Remote Instance.

2 Specify the details such as instance name, remote host, remote port, http port, and JVM route.

Instance name is a string that is used to identify the instance. Remote port and HTTP port are displayed in the Instance Manager page. These ports are provided in the the instance. Remote port is the AJP port and the instance port is the connector port.

JVM route is the remote instance name. The JVM route is an attribute that acts as an identifier for a particular Tomcat worker. JVM route is provided in the For more information on JVM route, see

Note: A remote instance and a local instance cannot have the same JVM route if they are added in a cluster with sticky session enabled.

3 If you want remote start and stop functionality over HTTP, enter Admin Component port, Admin Component

user name, and Admin Component password. The default Admin Component port is 8985.

Note: To enable this feature, install admin component on the remote host.

a In the remote host, open the ColdFusion_installtion\cfusion\jetty\etc\jetty.xml.

b Search for the string, org.mortbay.jetty.bio.SocketConnector.

c Update the host with the IP address of the remote host.

d Restart the jetty server.

server.xml file available in the runtime\conf folder of the instance.

http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html.

server.xml file available in the runtime\conf folder of

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

4 Click Submit.

Adding start and stop functionality to a remote instance over HTTPS

You can start and stop a remote instance over HTTPS or HTTP. To enable this feature, install admin component while installing ColdFusion. You can install Solr, admin component, or both while installing ColdFusion.

1 Do the following in the remote host.

a In the remote host, generate a private key in a keystore file. Provide the details at prompt.

cfroot\jre\bin\keytool -genkeypair -alias certificatekey -keyalg RSA -validity 7 keystore keystore.jks

b Export the certificate. You can have a self-signed certificate or a certificate from a Certificate Authority.

cfroot\jre\bin\keytool -export -alias certificatekey -keystore keystore.jks -rfc -file selfsignedcert.cer

c Copy the jks file created in the jetty\etc directory.

d Open the jetty\etc\jetty.xml file.

e Search for the string, To add an HTTPS SSL Listener and add the following entry:

<Set name="Port">8443</Set> <Set name="maxIdleTime">30000</Set> <Set name="keystore"><SystemProperty name="jetty.home" default="." />/etc/jks-

file.jks</Set>

<Set name="password">changeit</Set> <Set name="keyPassword">changeit</Set> <Set name="truststore"><SystemProperty name="jetty.home" default="." />/etc/jks-

file.jks</Set>

<Set name="trustPassword">changeit</Set> </New> </Arg>

</Call>

f Update the keystore name, password, key password, and jks file in the entry.

g Search for the string org.mortbay.jetty.bio.SocketConnector.

h Update the host with the IP address of the remote host.

i Restart the jetty server.

Note: If the remote server is running on Windows Vista, Windows 7, or Windows Server 2008, start the jetty sever with admin privileges.

2 Do the following in the local host from where you add the remote instance:

a Copy the .cer file created in the remote host to any of the locations.

b Import the certificate.

cfroot\jre\bin\keytool.exe -importcert -keystore "cfroot\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

c Register the remote instance using the ColdFusion Administrator. For more information, see “Registering a

remote instance” on page 11.

d In the Register Remote Instance page, enter the admin component port, admin component user name, and

admin component password (user name and password. These details you specified while installing the Remote Instance Administrator). The default https port is 8443.

e Select the HTTPS check box.

f Click Submit.

Setting up remote start and stop functionality using HTTPS in Server Manager

You can set up start and stop remote instance functionality in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.

1 Do the following in the remote host.

a In the remote host, generate a private key in a keystore file. Provide the details at prompt.

cfroot\jre\bin\keytool -genkeypair -alias certificatekey -keyalg RSA -validity 7 keystore keystore.jks

b Export the certificate. You can have a self-signed certificate or a certificate from a Certificate Authority.

cfroot\jre\bin\keytool -export -alias certificatekey -keystore keystore.jks -rfc -file selfsignedcert.cer

c Copy the .jks file created in the remote host to the jetty\etc directory.

d Open the jetty\etc\jetty.xml file.

e Search for the string, To add a HTTPS SSL Listener and then add the following entry:

<Set name="keystore"><SystemProperty name="jetty.home" default="."

/>/etc/server.jks</Set>

<Set name="password">changeit</Set>

<Set name="keyPassword">changeit</Set>

<Set name="truststore"><SystemProperty name="jetty.home" default="."

/>/etc/server.jks</Set>

<Set name="trustPassword">changeit</Set> </New> </Arg>

</Call>

f Update the keystore name, password, key password, and jks file in the entry.

g Search for the string, org.mortbay.jetty.bio.SocketConnector.

h Update the host with the port number of the remote host.

i Restart the jetty server.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Note: If the remote server is running on Windows Vista, Windows 7, or Windows Server 2008, start the jetty sever with admin privileges.

2 Do the following in the local host from where you add remote instance:

a Copy the .cer file created in the remote host to any of the locations.

b Import the certificate.

cfroot\jre\bin\keytool.exe -importcert -keystore "cfroot\jre\lib\security\cacerts" -file selfsignedcert.cer -storepass password

3 Open wwwroot\CFIDE\ServerManager\ServerManager.air on the local host.

4 Specify the connection details.

5 Click Start/Stop Details.

6 Select HTTPS.

7 Provide the following information:

• App Server Username: User name for the admin component that you specified while installing ColdFusion.

Default value is admin.

• App Server Password: Password for the admin component.

• Port: ColdFusion remote instance’s HTTPS port.

• Server: ColdFusion remote instance name.

• ColdFusion Version: For ColdFusion, 10.

• Admin Server Port: Default https port is 8443. Port of the Jetty server.

• Context Root: Value is AdminServlet.

8 Click Apply.

Setting up remote start and stop functionality using HTTP in Server Manager

You can set up start and stop remote instance functionality in Server Manager. To enable this feature, install Remote Instance Administrator while installing ColdFusion.

1 Do the following in the remote host:

a In the remote host, open the ColdFusion_installtion\cfusion\jetty\etc\jetty.xml.

b Search for the string, org.mortbay.jetty.bio.SocketConnector.

c Update the host with the IP address of the remote host.

d Start the jetty server. Go to the ColdFusion_installation\cfusion\jetty directory and use jetty.exe.

You can also use the jetty services in the Windows services.

2 Open wwwroot\CFIDE\ServerManager\ServerManager.air on the local host.

3 Specify the connection details.

4 Click Start / Stop Details.

5 Select HTTP.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

6 Provide the following information:

• App Server Username: User name for the admin component that you specified while installing ColdFusion.

The default value is

admin.

• App Server Password: Password for the admin component.

• Port: ColdFusion remote instance’s HTTP port.

• Server: ColdFusion remote instance name.

• ColdFusion Version: For ColdFusion Zeus, 10.

• Admin Server Port: Default https port is 8985. Port of the Jetty server.

• Context Root: Value is AdminServlet.

7 Click Apply.

Managing clusters

Manage clusters using the ColdFusion Administrator.

1 In the ColdFusion Administrator, click Enterprise Manager > Cluster Manager.

2 Enter a cluster name and then click Add.

3 Click the cluster name and move the servers to the cluster based on the requirement.

4 (If necessary) Edit the multicast port.

Multicast port is used to group the cluster members together. Default value of multicast port is 45564. After you create a cluster, the port is added in the

cfroot\config\cluster.xml file.

For more information on multicast port, see http://tomcat.apache.org/tomcat-7.0-doc/config/cluster-

membership.html.

5 Specify if you need sticky session.

Sticky session ensures that after a session is established on an instance, all future requests from the client are mapped to that instance.

6 Click Submit.

Note: Restart the web server if cluster instances are modified.

Adding a remote instance to a cluster

To add a remote instance to a cluster, add the cluster block to the remote instance’s server.xml. Then, register the remote instance and add the instance to the cluster. For more information on configuring clusters on Tomcat, see

http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html.

1 Register the remote instance to the local machine.

2 Create a cluster in the local machine.

3 Open the cfroot\instance-name\runtime\conf\server.xml file of the remote instance.

4 Add the following block between the entries </host> and </engine>:

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

<Manager notifyListenersOnReplication="true" expireSessionsOnShutdown="false"

className="org.apache.catalina.ha.session.DeltaManager">

</Manager> <Channel className="org.apache.catalina.tribes.group.GroupChannel">

<Membership port="45565" dropTime="3000" address="228.0.0.4"

className="org.apache.catalina.tribes.membership.McastService" frequency="500">

</Membership> <Receiver port="4003" autoBind="100" address="auto" selectorTimeout="5000"

maxThreads="6" className="org.apache.catalina.tribes.transport.nio.NioReceiver">

</Receiver> <Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter">

<Transport

className="org.apache.catalina.tribes.transport.nio.PooledParallelSender">

</Transport> </Sender> <Interceptor

className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector">

</Interceptor> <Interceptor

className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor">

</Interceptor>

</Channel> <Valve className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""> </Valve> <Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve"> </Valve>

<ClusterListener

className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener">

</ClusterListener> <ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener"> </ClusterListener>

</Cluster>

5 In the entry, update the membership port with the multicast port of the cluster.

6 Using the ColdFusion Administrator of the local host, add the local instance and the remote instance to the cluster.

Note: If you enable sticky session, the JVM route of the remote instance and local instance must not be the same.

7 Restart all the instances.

Note: When adding a remote instance in a cluster, ensure that you comment out <Manager pathname="" /> in content.xml file located in

<cf_home>\runtime\conf directory.

Configuring other web servers

Use the Web Server Configuration Tool to configure other web servers.

❖ Run cfroot\runtime\bin\wsconfig.exe.

You can also configure web servers using the command-line interface as follows.

Configuring IIS

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

wsconfig.exe -ws iis -site <site_no>

wsconfig.exe -ws iis -site <site_name>

Configuring cluster

wsconfig.exe -ws iis -site <site_no> -cluster <cluster-name>

Configuring Apache

(Windows only) wsconfig.exe –ws apache –dir <apache_conf_directory> (Linux or MAC only) ./wsconfig –ws apache –dir <apache_conf_directory>

(Windows only) wsconfig.exe –ws apache –dir <apache_conf_directory> –bin <apache_bin_directory>/httpd –script <apache_bin_directory>/apachectl (Linux or Mac only) ./wsconfig –ws apache –dir <apache_conf_directory> –bin <apache_bin_directory>/httpd –script <apache_bin_directory>/apachectl

Configuring cluster

(Windows only) wsconfig.exe -ws apache –dir <apache_conf_directory> -cluster <cluster-name> (Linux or MAC only) ./wsconfig -ws apache –dir <apache_conf_directory> -cluster <cluster-name>

Configuring Sun Java Web Server

(Windows only) wsconfig.exe –ws SunJWS –dir <SunJWS_conf_directory> (Linux or MAC only) ./wsconfig –ws SunJWS –dir <SunJWS_conf_directory>

Configuring cluster

(Windows only) wsconfig.exe -ws SunJWS –dir <SunJWS_conf_directory> -cluster <cluster-name> (Linux or MAC only) ./wsconfig -ws SunJWS –dir <SunJWS_conf_directory> -cluster <cluster-name>

Unconfiguring IIS

wsconfig.exe -remove -ws iis -site <site_no>

wsconfig.exe -remove iis -site <site_name>

Unconfiguring Apache

./wsconfig -remove –ws apache –dir <apache_conf_directory>

./wsconfig -remove –ws apache –dir <apache_conf_directory> –bin <apache_bin directory>/httpd –script <apache_bin_directory>/apachectl

Unconfiguring Sun Java Web Server

./wsconfig -remove –ws SunJWS –dir <SunJWS_conf_directory>

Unconfiguring all webservers

./wsconfig -uninstall

Seeing the list of webservers

./wsconfig -list

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Configuring Secured Socket Layer (SSL)

SSL allows the browser and the server to communicate over a secured connection. Data that is sent is encrypted at one side, transmitted, and then decrypted at the other end. For more information about SSL configuration on Tomcat, see

http://tomcat.apache.org/tomcat-7.0-doc/ssl-howto.html.

To configure SSL for ColdFusion using the keytool utility, do the following:

1 Create a certificate file:

a Run the following command:

cfroot\jre\bin\keytool -genkey -alias tomcat -keyalg RSA

b Type the details as per the instruction.

Note: If you do not provide a password, the default password for keystore and key is changeit. If you don’t want to use the default password, ensure that you provide the same password for the keystore and the key.

Running this command creates a certificate.keystore in the following location:

• Windows: C:\Documents and Settings\user's_directory

• Linux: usr/home

2 Open the cfroot\cfusion\runtime\conf\server.xml file and search for the string Define a SSL HTTP/1.1.

3 Uncomment the connector details and update the section as follows:

<Connector port="8443" protocol="HTTP/1.1"

SSLEnabled="true" maxThreads="150" scheme="https" secure="true" keystoreFile="<certificate_location>\.keystore"

keystorePass="<password>" keyAlias="tomcat" clientAuth="false" sslProtocol="TLS" />

4 Restart ColdFusion.

5 Access ColdFusion using the following URL: https://<ip-address>:8443/CFIDE/administrator

Changing virtual directory and the doc root

Do the following to change the virtual directory and doc root:

1 Open CFInstallation\cfusion\runtime\conf\server.xml.

2 Under host block, search for the string, “To add virtual directory.”

3 Uncomment the entry context path below.

4 To add a virtual directory, add the aliases attribute as shown below:

<Context path="/" docBase="<absolute_path_to_cfrootectory>\wwwroot" WorkDir="<cf_home>\runtime\conf\Catalina\localhost\tmp" aliases="/path1=<absolute_path_to_directory1>,/path2=<absolute_path_to_directory2>"></Context>

Note: Alias path must include a leading ‘/’.

5 To change the doc root, change the docBase value in the above entry.

For more details on the Context attributes, see http://tomcat.apache.org/tomcat-6.0-doc/config/context.html.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

Changing the connector port for cfstat

You can use the connector output for logging cfstat metric. The cfconnector port is defined in the

CFInstallation/cfusion/lib/neo-metric.xml file. If you have configured a connector, update the port with the

connector port. The connector port (AJP port) is provided in the

CFInstallation/cfusion/runtime/conf/server.xml.

To update the connector port using the Administrator console:

1 Login ColdFusion Administrator.

2 Click Debugging & Logging > Debug Output.

3 Update the connector port and click Submit Changes.

Enabling Search Engine Safe URLs

Search Engine Safe URL (SES) helps the search engines to index dynamic web pages. SES URLs pass parameters using slashes instead of default URL pattern. By default, SES is enabled for stand-alone installation of ColdFusion on Tomcat.

Note: SES is applicable only for stand-alone installation of Tomcat. It does not work if ColdFusion is deployed as a WAR file on Tomcat.

Note: If you wish to use custom SES URLs, add the URL entry to the uriworkermap.properties file found in the

wsconfig folder for your web server.

Enabling Secure Profile

*New for ColdFusion 10*

ColdFusion allows you to secure ColdFusion server furthermore by enabling or disabling certain settings. When installing ColdFusion, you can enable Secure Profile by selecting the option when prompted on the Secure Profile screen. Further, you could provide a comma separate list of IP addresses that may be allowed to access the ColdFusion Administrator. For more information, see Enabling Secure Profile for ColdFusion Administrator.

Changing the log rotation settings

You can change the log rotation settings such as maximum number of backup files and the size of the backup files.

1 Specify log file settings in the neo-logging.xml, located in the <ColdFusion_Home>\lib directory.

2 The size of coldfusion-out.log and coldfusion-error.log is set to 20MB by deafult. You can change the size of the log

in the neo-logging.xml file by changing the

3 You can also change the maximum number of backups of coldfusion-out.log and coldfusion-error.log that

ColdFusion takes during log rotation within the neo-logging.xml file. Change the

maxFileSize setting.

maxBackSize setting.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

4 You can change the settings of the remaining files in the ColdFusion Administrator by going to the Debugging and

Logging > Logging Settings section. Change the Maximum file size and Maximum number of Archives settings accordingly.

Enabling persistent session

To persist a session after a Tomcat restart, do the following:

1 Open the cfroot\cfusion\runtime\conf\context.xml file.

2 Uncomment the Manager pathname node.

Note: Flex sessions are not persisted after a Tomcat restart.

Updating from an earlier version

If you have skipped the migration or you have to make modifications to the previous installation that has to be migrated, do the following:

1 Stop the server.

2 Save settings by copying the files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml (of previous installation) to a

directory named cfXsettings (in which X is the earlier version of ColdFusion) in the cf_webapp_new_installation_root_directory/WEB-INF/cfusion/lib directory.

3 Edit the ColdFusion 10 cfusion/lib/adminconfig.xml file by setting the value of the runmigrationwizard and the

migratecfX (in which X is the earlier version of ColdFusion) switch to true.

4 Restart the ColdFusion 10 application.

5 Browse to ColdFusion Administrator to run the migration wizard.

Uninstalling ColdFusion

Uninstalling ColdFusion deletes all program files and related components from your computer.

Uninstall ColdFusion from Windows

1 Select Start > Settings > Control Panel > Add/Remove Programs > Adobe ColdFusion 10.

2 Click Change/Remove.

3 When the program completes, remove any remaining files and directories in the cf_root directory.

4 In some cases, the uninstall program may require you to restart the computer.

ColdFusion is deleted from your server.

Uninstall ColdFusion from UNIX

1 Log in as root.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the Server Configuration

2 Enter the following command to go to the cf_root/uninstall directory:

cd cf_root/uninstall

3 Enter the following command:

./uninstall.sh

4 When the program completes, remove any remaining files and directories in the cf_root directory.

ColdFusion is deleted from your server.

Last updated 7/9/2012

Chapter 3: Installing the J2EE Configuration

Gathering information necessary to install the J2EE configuration

Question Answer

Platform-specific installer name? ___________________________________________________

Serial number for ColdFusion? ___________________________________________________

Type of installation? ___ Server configuration

_X_ J2EE configuration

EAR or WAR file? ___ EAR

___ WAR

Subcomponents to install? ___ ColdFusion 10 ODBC Services

___ ColdFusion 10 Solr Services

___ .NET Integration Services

___ ColdFusion 10 Documentation

Installation directory for ColdFusion and services? ___________________________________________________

Context root for ColdFusion (EAR file only, default=cfusion)?

ColdFusion Administrator password? ___________________________________________________

Enable Secure Profile ___Yes

Configure OpenOffice ___Yes

___________________________________________________

___No

Identify a list of IP addresses that will have access to the ColdFusion Administrator.

___No

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

Question Answer

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? ___________________________________

Automatically check for server updates? ___ Yes

___ No

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 (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 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

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

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:

cfusion-ear META-INF application.xml cfusion-war WEB-INF web.xml CFIDE cfdocs rds.war WEB-INF web.xml

If your J2EE application server supports enterprise applications, install and deploy the EAR file. For more information,

“Installing an EAR file or WAR files” on page 25.

see

Context root

Because the J2EE environment supports multiple, isolated web applications running in a server instance, J2EE web applications running in a server are each rooted at a unique base URL, called a context root (or 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 cf10, you display the ColdFusion 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

context-root element of the 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.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

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).

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.

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

configuration” on page 29.

Deploy expanded archive as working directory On other application servers (such as Oracle 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 29.

“ColdFusion J2EE deployment and

Installing an EAR file or WAR files in Windows

You can install the ColdFusion J2EE configuration in Windows.

Note: The Windows installer requires a computer that supports at least 256 colors.

Install ColdFusion in Windows (J2EE configuration)

1 Read the online version of the Release Notes for any late-breaking information or updates. For more information,

www.adobe.com/go/learn_cfu_releasenote_en.

see

2 Ensure that your operating system meets the system requirements described on the Adobe website at

www.adobe.com/go/learn_cfu_cfsysreqs_en.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

3 Review the “Installation considerations for Windows” on page 2 and “Installation considerations for all platforms”

on page 2.

4 Determine and record environment information, as described in “Preparing to install using the J2EE

configuration” on page 25.

5 Determine the answers to the questions in the section “Gathering information necessary to install the J2EE

configuration” on page 22

6 Close any applications that are currently running on your computer.

7 Insert the DVD or download the setup file from the Adobe website.

8 If the installation wizard does not start automatically when you insert the DVD, locate the appropriate installer on

the DVD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion installation executable file (ColdFusion_10_WWEJ_win32.exe (for 32-bit systems)/ColdFusion_10_WWEJ_win64.exe (for 64-bit systems)) and double-click it.

9 Follow the instructions in the installation wizard, and let it run to completion.

10 Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see

“ColdFusion J2EE deployment and configuration” on page 29.

11 Open the ColdFusion Administrator to run the Configuration wizard.

12 To install any other integrated Adobe or third-party technologies, see “Installing Integrated Technologies” on

page 46.

13 Configure and manage your system, as described in “Configuring Your System” on page 52.

14 To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the

Resources page of the ColdFusion Administrator.

15 Code ColdFusion CFM pages.

Store CFM pages under the web application root (either cfusion-ear\cfusion-war or cfusion-war) and access these pages using a URL of the form http://hostname:portnumber/context-root/filename.cfm, as follows:

• hostname: The machine name, IP address, or localhost.

• portnumber: The port number used by your application server’s web server.

• contextroot: The context root for the ColdFusion web application. For more information, see “Context root” on

page 24.

• filename: The directory path and file to display. The path is relative to the cfusion-war directory.

Installing an EAR file or WAR files in UNIX

You can install the ColdFusion J2EE configuration in UNIX. If you are updating an existing deployment of ColdFusion for J2EE, see

Install ColdFusion in UNIX (J2EE configuration)

1 Read the online version of the Release Notes for any late-breaking information or updates. For more information,

see

2 Ensure that your operating system meets the system requirements described on the Adobe website at

www.adobe.com/go/learn_cfu_cfsysreqs_en.

3 Review the “Installation considerations for UNIX” on page 3 and “Installation considerations for all platforms” on

page 2.

“Updating from an earlier version for J2EE” on page 29 before you continue.

www.adobe.com/go/learn_cfu_releasenote_en.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

4 Determine and record environment information, as described in “Preparing to install using the J2EE

configuration” on page 25.

5 Determine the answers to the questions in the section “Gathering information necessary to install the J2EE

configuration” on page 22.

6 Log in as root.

7 Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save

it to a directory on your local disk.

The following installation files are those for supported J2EE configuration platforms:

Platform File

Linux

• ColdFusion_10_WWEJ_linux32.bin (for 32-bit systems)

• ColdFusion_10_WWEJ_linux64.bin (64-bit systems)

Solaris ColdFusion_10_WWEJ_solaris64.bin

UNIX (other than Solaris or Linux) ColdFusion_10_WWEJ_java.jar

8 Using the cd command, go to the directory with the installation file.

9 Start the installation with the following command:

./<filename> -i console

The installation program starts.

To use the ColdFusion_10_WWEJ_java.jar file to install on a UNIX platform other than Solaris or Linux, enter the following command (for more information, see

java_home/bin/java -jar ColdFusion_10_WWEJ_java.jar -i console

“Installation considerations for UNIX” on page 3):

Note: To run the Linux installer in GUI mode, type ./<filename> -i gui.

10 Follow the prompts, and let the installation program run to completion.

Note: For security reasons, it is crucial that you do not use root for the run-time user. Instead, use a nonprivileged user that does not have a login shell, such as the default user account nobody, which exists for this type of situation.

11 Deploy ColdFusion and configure Java settings, as required by your application server.

For more information, see “ColdFusion J2EE deployment and configuration” on page 29.

Note: If you deployed the rds.war file, and an error message indicates that RDS is not installed or not enabled, edit the rds.properties file to match the ColdFusion context root, restart the application server, and re-open the ColdFusion Administrator.

12 Open the ColdFusion Administrator to run the Configuration wizard.

13 Configure and manage your system, as described in “Configuring Your System” on page 52.

14 To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the

Resources page of the ColdFusion Administrator.

15 Code and test ColdFusion CFM pages.

Store CFM pages under the web application root (either cfusion-ear/cfusion-war or cfusion-war) and access these pages using a URL of the form http://hostname:portnumber/context-root/filename.cfm, as follows:

• hostname: The machine name, IP address, or localhost.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

• portnumber: The port number used by your application server’s web server.

• contextroot: The context root for the ColdFusion web application. For more information, see “Context root” on

page 24.

• filename: The directory path and file to display. The path is relative to the cfusion-war directory.

Installing an EAR file or WAR files in Mac OS X

You can install the ColdFusion J2EE configuration for Mac OS X. If you are updating an existing deployment of ColdFusion 8 for J2EE, see

Install ColdFusion in Mac OS X (J2EE configuration)

1 Read the online version of the Release Notes for any late-breaking information or updates.

For more information, see www.adobe.com/go/learn_cfu_releasenote_en.

2 Ensure that your operating system meets the system requirements described on the Adobe website at

www.adobe.com/go/learn_cfu_cfsysreqs_en.

3 Review the “Installation considerations for UNIX” on page 3 and “Installation considerations for all platforms” on

page 2.

4 Determine and record environment information, as described in “Preparing to install using the J2EE

configuration” on page 25.

5 Determine the answers to the questions in the section “Gathering information necessary to install the J2EE

configuration” on page 22.

6 Log in as root.

7 Copy the installation file that is appropriate for your platform and locale from the DVD or Adobe website, and save

it to a directory on your local disk.

The following installation files are those for supported J2EE configuration platforms:

“Updating from an earlier version for J2EE” on page 29 before you continue.

• ColdFusion_10_WWEJ_osx10.dmg - To install in Mac OS X systems

8 Start the installation by double-clicking the installation file on the desktop. The file ColdFusion 10 Installer.app is

installed in the same directory. Double click this APP file to start the installation in GUI mode.

9 Follow the prompts, and let the installation program run to completion.

Note: For security reasons, it is crucial that you do not use root for the runtime user. Instead, use a nonprivileged user that does not have a login shell, such as the default user account nobody, which exists for this type of situation.

10 Deploy ColdFusion and configure Java settings, as required by your application server. For more information, see

“ColdFusion J2EE deployment and configuration” on page 29.

11 Open the ColdFusion Administrator to run the Configuration wizard.

12 Configure and manage your system, as described in “Configuring Your System” on page 52.

13 To learn about ColdFusion, read the documentation, which is accessible through the Documentation link on the

Resources page of the ColdFusion Administrator.

14 Code and test ColdFusion CFM pages.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

• hostname The machine name, IP address, or localhost.

• portnumber The port number used by your application server’s web server.

• contextroot The context root for the ColdFusion web application. For more information, see “Context root”

on page 24.

• filename The directory path and file to display. The path is relative to the cfusion-war directory.

Updating from an earlier version for J2EE

If you previously deployed the ColdFusion J2EE configuration on your application server, you must also perform the following steps as part of the installation procedure:

1 As appropriate for your application server, either stop the ColdFusion application and RDS application (if it is

running), or stop the application server before you start the installation wizard.

2 (Windows only) If you installed the SequelLink ODBC Agent, stop the ODBC services before you start the

installation wizard.

3 Copy application files to a backup directory.

4 Save settings by copying the files cf_webapp_root/WEB-INF/cfusion/lib/neo-*.xml to a backup directory.

5 Before you deploy ColdFusion 10, undeploy the previous ColdFusion application using your application-server-

specific undeploy functionality.

6 Deploy ColdFusion 10 as described in “Deploying ColdFusion 10 on IBM WebSphere” on page 31, “Deploying

ColdFusion 10 on Oracle WebLogic” on page 37, or “Deploying ColdFusion 10 on JBoss Application Server” on

page 40.

7 Create a directory named cfXsettings (in which X is the earlier version of ColdFusion) in the cf_webapp_root/WEB-

INF/cfusion/lib directory.

8 Copy the backed up settings files to the ColdFusion 10 cfusion/lib/cfXsettings directory.

9 Edit the ColdFusion 10 cfusion/lib/adminconfig.xml file by setting the value of the runmigrationwizard and the

migratecfX (in which X is the earlier version of ColdFusion) switch to true.

10 Restart the ColdFusion 10 application.

11 Browse to ColdFusion Administrator to run the migration wizard.

Note: The migration wizard supports only the migration of settings from ColdFusion 9.

ColdFusion J2EE deployment and configuration

The J2EE specification allows application servers to handle compressed and expanded deployments in a serverdependent manner; each application server has its own deployment and configuration mechanism, as the following table shows:

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

Application server Deployment mechanism Expanded or compressed deployment

Apache Tomcat Tomcat Deployment Manager Expanded

IBM WebSphere IBM WebSphere Administrative Console Compressed

Oracle WebLogic Weblogic Administration Console/Auto deploy to

server domains

JBOSS Application Server Auto deploy to server root Expanded

Oracle Weblogic Server Oracle Weblogic Server Administration Console Expanded

Expanded

For basic deployment information, see your J2EE application server documentation. ColdFusion deployment instructions differ for each J2EE application server. For more information, see deployment instructions for the specific application server.

J2EE directory structure

The following table describes the directories under the cf_webapp_root web application directory when you use the J2EE configuration:

Directory Description

cfdocs Documentation for ColdFusion.

CFIDE Files for the ColdFusion Administrator.

WEB-INF/cfclasses Compiled ColdFusion templates in your ColdFusion applications.

WEB-INF/cfc-skeletons Support for ColdFusion components that are exported as web services.

WEB-INF/cfform Files that support Flash forms.

WEB-INF/cftags Templates for ColdFusion.

WEB-ING/flex Configuration and files for LiveCycle Data Services ES.

WEB-INF/gateway Files that support event gateways.

WEB-INF/cfusion/bin Executable files used by ColdFusion.

WEB-INF/cfusion/cfx CFX tag include file and examples.

WEB-INF/cfusion/charting Files for the ColdFusion graphing and charting engine.

WEB-INF/cfusion/Custom Tags Repository for your custom tags.

WEB-INF/cfusion/db Sample databases for all platforms. These databases are Apache Derby databases.

WEB-INF/cfusion/jintegra JIntegra programs, libraries, and other supporting files (for example, to integrate Java and

WEB-INF/cfusion/lib

WEB-INF/lib and

WEB-INF/cfusion/MonitoringServer

WEB-INF/cfusion/logs ColdFusion log files.

WEB-INF/cfusion/Mail Files, including spool files, used by ColdFusion for mail.

COM code; manage access to ActiveX controls (OCXs) that are hosted in a graphical user interface (GUI) container; and register the JVM and type libraries).

JAR, XML, property, and other files that are the foundation of ColdFusion, including functionality such as queries, charting, mail, security, Solr searches, and system probes.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

Directory Description

WEB-INF/cfusion/registry Used only in UNIX, by the cfregistry tag.

WEB-INF/cfusion/stubs Compiled code for web services.

WEB-INF/cfusion/solr Solr configuration and Jetty.

Deploying ColdFusion 10 on IBM WebSphere

The following instructions tell you how to deploy ColdFusion 10 on IBM WebSphere Application Server (AS) and Network Deployment (ND).

The following terms refer to WebSphere and ColdFusion directories:

websphere_root The directory in which IBM WebSphere Application Server is installed; for example, C:\Program

Files\WebSphere in Windows, and /opt/WebSphere in UNIX.

cf_webapp_root The directory to which the ColdFusion web application is deployed; for example, C:\Program

Files\WebSphere\AppServer\installedApps\<My_Host>\cfusion.ear\cfusion.war in Windows, and /opt/WebSphere/AppServer/installedApps/<My_Host>/cfusion.ear/cfusion.war in UNIX.

java_home The root directory of your Java 2 software development kit (J2SDK); for example, C:\j2sdk1.6.0_29.

Deploy ColdFusion 10 on WebSphere 7 or 8 (AS)

1 Start the IBM WebSphere Application Server, if it is not running.

2 Open the IBM WebSphere Administrative Console, if it is not running.

3 Select Applications > Install New Application.

4 When the Preparing for the Application Installation page appears, in the text box for the local file system, enter the

path to the EAR file that you installed when you installed ColdFusion; for example, C:\ColdFusion10\cfusion.ear.

If you are running the Administrative console from a browser that is not on the same system on which WebSphere is running, that is, not from localhost, use the Remote file system option, which enables directory browsing on the server file system.

5 Leave the Context Root box empty and click Next.

6 Accept the default values on the second Select Installation Options page, if appropriate for your WebSphere

configuration, and then click Next.

WebSphere might display an Application Security Warnings page with a message at the bottom of the page that starts with "ADMA0080W: A template policy file without any permission set is included in the 1.2.x enterprise application." You can ignore this warning.

7 If you have multiple application servers, select the application server in which to install the ColdFusion application

and RDS support, and then click Next.

8 When the Map Virtual Hosts for Web Modules panel appears, select the virtual host or hosts in which to install the

ColdFusion 10 application and Remote Development Services (RDS) support, and then click Next.

RDS must be on the same virtual host and port as ColdFusion 10.

9 When the Summary panel appears, review the installation configuration, and then click Finish.

10 When the Application Adobe ColdFusion 10 Installed Successfully message appears on the Installing page, select

Save To Master Configuration, and then select Save on the Save page to save your workspace.

If you changed the application name from the default, the message uses your application name.

Last updated 7/9/2012

INSTALLING COLDFUSION 10

Installing the J2EE Configuration

11 Start the enterprise application named Adobe ColdFusion 10.

12 Browse to the ColdFusion Administrator to run the Configuration Wizard.

Note: Copy the version of tools.jar that the application server uses to the cfusion/lib directory.

Deploy ColdFusion 10 on WebSphere 7 or 8 (ND)

1 Start the IBM WebSphere Application Server, if it is not running.

2 Open the IBM WebSphere Administrative Console, if it is not running.

3 Select Applications > Install New Application.

4 When the Preparing for the Application Installation page appears, in the text box for the local file system, enter the

path to the EAR file that you installed when you installed ColdFusion; for example, C:\ColdFusion10\cfusion.ear.

5 Leave the Context Root box empty and click Next.

6 Accept the default values on the second Select Installation Options page, if appropriate for your WebSphere

configuration, and then click Next.

7 Select the cluster on which to install the ColdFusion application and RDS support, and then click Next.