Macromedia ColdFusion - 9.0 Installation Manual

Installing

ADOBE®

COLDFUSION

This user guide is protected under copyright law, furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide.

This user guide is licensed for use under the terms Creative Commons Attribution Non-Commercial 3.0 License. This License allows users to copy, distribute, and transmit the user guide for noncommercial purposes only so long as (1) proper attribution to Adobe is given as the owner of the user guide; and (2) any reuse or distribution of the user guide contains a notice that use of the user guide is governed by these terms. The best way to provide notice is to include the following link. To view a copy of this license, visit

http://creativecommons.org/licenses/by-nc-sa/3.0/

Adobe, the Adobe logo, ColdFusion, and Flash are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

ActiveX, Microsoft , and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. IBM and AIX are trademarks of International Business Machines Corporation in the United States, other countries, or both. Java, Solaris, and Sun are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Macintosh and Mac OS are trademarks of Apple Inc., registered in the United States and other countries. Red Hat is a trademark or registered trademark of Red Hat, Inc. in the United States and other countries. SUSE is a trademark of Novell, Inc. UNIX is a registered trademark of The Open Group in the US and other countries . Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. All other trademarks are the property of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/)

This product contains either BSAFE and/or TIPEM software by RSA Data Security, Inc.

Portions include technology used under license from Autonomy, and are copyrighted.

Verity and TOPIC are registered trademarks of Autonomy.

This product includes software developed by the OpenSymphony Group (http://www.opensymphony.com/).

Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA.

Notice to U.S. Government End Users. The Software and Documentation are “Commercial Items,” as that term is defined at 48 C.F.R. §2.101, consisting of “Commercial Computer Software” and “Commercial Computer Software Documentation,” as such terms are used in 48 C.F.R. §12.212 or 48 C.F.R. §227.7202, as applicable. Consistent with 48 C.F.R. §12.212 or 48 C.F.R. §§227.7202-1 through 227.7202-4, as applicable, the Commercial Computer Software and Commercial Computer Software Documentation are being licensed to U.S. Government end users (a) only as Commercial Items and (b) with only those rights as are granted to all other end users pursuant to the terms and conditions herein. Unpublished-rights reserved under the copyright laws of the United States. Adobe Systems Incorporated, 345 Park Avenue, San Jose, CA 95110-2704, USA. For U.S. Government End Users, Adobe agrees to comply with all applicable equal opportunity laws including, if appropriate, the provisions of Executive Order 11246, as amended, Section 402 of the Vietnam Era Veterans Readjustment Assistance Act of 1974 (38 USC 4212), and Section 503 of the Rehabilitation Act of 1973, as amended, and the regulations at 41 CFR Parts 60-1 through 60-60, 60-250, and 60-741. The affirmative action clause and regulations contained in the preceding sentence shall be incorporated by reference.

Last updated 1/20/2012

Chapter 1: Preparing to Install ColdFusion

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

Installing ColdFusion 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Installing ColdFusion 9 Update 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2: Installing the Server Configuration

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

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

ColdFusion server configuration directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

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

Switching from another web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Updating from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Uninstalling ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 3: Installing the Multiserver Configuration

Gathering information necessary to install the multiserver configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About multiserver configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Installing ColdFusion using the multiserver configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Updating from an earlier version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Uninstalling ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

iii

Chapter 4: Installing the J2EE Configuration

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

ColdFusion and J2EE application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

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

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

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

ColdFusion J2EE deployment and configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Undeploying ColdFusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 5: Installing Integrated Technologies

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

Installing Dreamweaver extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Installing Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Installing Verity Search Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Installing Solr search server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Enabling Flash Remoting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Installing Flash Remoting Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing LiveCycle Data Services Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Installing the ColdFusion .NET Integration Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Installing ColdFusion Extensions for Eclipse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Configuring OpenOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Contents

Chapter 6: Configuring Your System

Overview of configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Managing ColdFusion services in Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Managing the ColdFusion process in UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

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

Configuring web servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Enabling CORBA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Disabling Remote Development Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

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

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

Chapter 7: Troubleshooting

Common installation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Data source problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Migration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

J2EE configuration problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Postinstallation problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Uninstall problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Last updated 1/20/2012

Chapter 1: Preparing to Install ColdFusion

Before installing Adobe ColdFusion 9, 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:

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

Upgrade installation You can upgrade from ColdFusion MX 7 and ColdFusion 8. 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 9 in any of the following configurations:

Server configuration Lets you install one instance of ColdFusion 9 with an embedded JEE server. This

configuration most closely resembles the ColdFusion 8 base release and ColdFusion 7. This was formerly known as the stand-alone configuration. For information on installing the server configuration, see

Configuration” on page 4.

Multiserver configuration (Enterprise Edition only) Installs Macromedia® JRun™ from Adobe and automatically

deploys ColdFusion 9 in a separate JRun server instance. This configuration supports server instance creation and ColdFusion deployment in the ColdFusion Administrator and lets you manage ColdFusion 9 deployments on multiple JRun servers. For information on installing the multiserver configuration, see

Configuration” on page 11.

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

2 Enterprise Edition (J2EE) application server, using the bundled license of JRun or a third-party J2EE server, such as IBM WebSphere or BEA WebLogic. When you use the J2EE configuration, you can deploy ColdFusion 9 multiple times on a single computer. For information on installing the J2EE configuration, see

Configuration” on page 17.

“Installing the Server

“Installing the Multiserver

“Installing the J2EE

Installing ColdFusion 9

ColdFusion 9 product editions

The ColdFusion 9 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 1/20/2012

INSTALLING COLDFUSION 9

Preparing to Install ColdFusion

System requirements

The ColdFusion 9 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 9, 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 67.

Installation considerations for all platforms

The following are installation considerations for all platforms:

• Adobe supports installing ColdFusion 9 side-by-side with ColdFusion 8, ColdFusion MX 7, ColdFusion MX 6.1.

• If you installed a Beta version of ColdFusion 9, uninstall it before you install this version.

• Adobe recommends using the built-in (internal port-based) web server for development, but not in a production

environment.

• Earlier versions of ColdFusion, including ColdFusion MX 6.1, can coexist with ColdFusion 9; however, you cannot

install ColdFusion 9 in the directory where the earlier version resides.

You can switch to use a different web server for ColdFusion 9 after the installation, by following the instructions for your platform and the web server in

“Configuring web servers” on page 61.

• During installation of the server configuration, if you select the built-in web server, your web root directory by

default is C:\ColdFusion9\wwwroot in Windows and /opt/coldfusion9 /wwwroot in UNIX. This web server runs on the 8500 port. To display a page, append 8500 to the end of the host name or IP address; for example, http://localhost:8500/MyApp.cfm. If the page still does not appear, ensure that the document is located in the ColdFusion 9 web root directory; for example, C:\ColdFusion9\wwwroot\MyApp.cfm. For more information, see “Using the built-in web server” on page 8.

• ColdFusion 9 is built in Java. By default, ColdFusion installs and runs on JDK 1.6. If you install ColdFusion 9 on

any J2EE server that is not running on JRE 1.6, replace the tools.jar file in the lib directory with the tools.jar file from the appropriate JRE.

• In an optimal production environment, each ColdFusion application is hosted on a dedicated server; database,

mail, and other servers are not on the same computer.

• Before you install ColdFusion 9, shut down ColdFusion MX 7 Verity to ensure proper migration of Verity

collections.

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 handle 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 instead.

Last updated 1/20/2012

INSTALLING COLDFUSION 9

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_9_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_9_WWE_java.jar. This Java-only installer does not include features that require platform-specific binary files, such as Verity and C++ CFX support.

Installing ColdFusion 9 Update 1

The following resources provide information about how to install ColdFusion 9 Update 1. The updater installs on top of an existing installation of ColdFusion 9.

• Installing the ColdFusion 9 Update

• FAQ about the Adobe ColdFusion 9.0 Update 1

Last updated 1/20/2012

Chapter 2: Installing the Server Configuration

The ColdFusion server configuration contains an embedded copy of Macromedia JRun from Adobe 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:\ColdFusion9 in Windows, and /opt/coldfusion9 in UNIX.

Gathering information necessary to install the server configuration

Although the ColdFusion 9 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 9.

Question Answer

Platform-specific installer name? ___________________________________________________

Serial number for ColdFusion? ___________________________________________________

Type of installation? _X_ Server configuration

___ Multiserver configuration

___ J2EE configuration

Subcomponents to install? ___ ColdFusion 9 ODBC Services

___ ColdFusion 9 Search Services

___ .NET Integration Services

___ ColdFusion 9 Documentation

___ LiveCycle Data Services ES

ColdFusion installation directory? ___________________________________________________

Serial number for Adobe LiveCycle Data Services Enterprise Suite (ES)? (Only if you selected to install the Enterprise Edition of LiveCycle Data Services ES)

If you leave this blank, the installer installs the Express Edition. For information on upgrading to the Enterprise Edition after completing the ColdFusion installation, see the LiveCycle Data Services ES documentation.

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

___ IIS

___ Apache

___ SunONE

___ Other

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

Question Answer

Configuration directory? (Apache and SunONE) ___________________________________________________

Path to server binary? (Apache) ___________________________________________________

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

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

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

Install ColdFusion in Windows

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 setup.exe file 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_9_WWE_win.exe/ColdFusion_9_WWE_win64.exe) and double-click it.

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

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

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

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

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/coldfusion9 directory. To install it into a different directory, create that directory before you run the installation.

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_9_WWE_linux.bin (for 32-bit systems)

• ColdFusion_9_WWE_linux64.bin (64-bit systems)

Solaris ColdFusion_9_WWE_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_9_WWE_solaris64.bin

10 Start the installation with the following command:

./<filename>

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

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

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/bin/coldfusion start

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

If you specified the use of an external web server when you ran the installer, ColdFusion automatically runs the cf_root/bin/cfmx-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/bin/connectors, as appropriate.

To stop ColdFusion, use the following command:

/cf_root/bin/coldfusion stop

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

13 Open ColdFusion Administrator to run the Configuration wizard.

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

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

page 48.

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

Resources page of the ColdFusion Administrator.

ColdFusion server configuration directory structure

The following table describes the directories under the cf_root directory when you install the server configuration of ColdFusion:

Directory Description

bin Programs for starting, stopping, and viewing information for ColdFusion, and to run Crystal Reports (Windows only).

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

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.

jintegra JIntegra programs, libraries, and other supporting files (for example, to integrate Java and COM code; manage access

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,

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

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

mail, security, Verity searches, Solr searches, and system probes.

logs Repository for ColdFusion log files.

JRE-specific log files are in the runtime/logs directory.

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

META-INF XML metadata for the ColdFusion Administrator.

registry (UNIX only) Flat file to store registry settings

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

Directory Description

runtime Programs and supporting files for the ColdFusion runtime.

In Windows, the files for the bundled JRE are in runtime\jre.

runtime/jre Files for the Java Runtime Environment (JRE) that is bundled with ColdFusion.

uninstall Files to uninstall ColdFusion.

verity Verity collections, configurations, and services directories.

solr Solr configurations and Jetty.

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

the WEB-INF directory; do not remove this directory.

Using the built-in web server

ColdFusion has its own web server that you can use to develop ColdFusion applications, without depending on an external web server, such as Internet Information Server (IIS), Apache, or Sun Java System Web Server. Adobe does not recommend using the built-in web server in a production environment. However, it is more than suitable for development, allowing you to create virtual directories and set the default document (for example, default.cfm or index.cfm).

During the ColdFusion installation, choose a web server. If you select the built-in web server, your web root directory is located in the cf_root/wwwroot directory. By default, the web server runs on port 8500. This means that to display a page in your application, append :8500 to the host name or IP address in the URL; for example, http://localhost:8500/YourApp1/index.cfm. (If the page still does not appear, ensure that the document is located in the built-in web server’s web root directory; for example, C:\ColdFusion9\wwwroot\YourApp1\index.cfm.)

Note: If you install the server configuration of ColdFusion with the built-in server and port 8500 is in use, for example by ColdFusion MX, ColdFusion MX 6.1, or ColdFusion MX 7, the installer starts with port 8501 and looks at up to 100 ports to find one that is not being used by an application that is running. ColdFusion uses that port and displays a message to indicate which port it selected.

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

Switching the port for the built-in web server

You can change the port on which the built-in web server runs.

Change the port for the built-in web server

1 Back up the jrun.xml file.

This file is in the cf_root\runtime\servers\coldfusion\SERVER-INF directory in Windows, and in the cf_root/runtime/servers/coldfusion/SERVER-INF directory in UNIX.

2 Open the original jrun.xml file for editing.

3 Change the port number specified in the WebService port attribute (near the bottom of the file):

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

<service class="jrun.servlet.http.WebService" name="WebService"> <attribute name="port">8500</attribute> <attribute name="interface">*</attribute> <attribute name="deactivated">false</attribute> ... </service>

Note: Ensure that the deactivated attribute is set to false.

4 Save the file, and then restart ColdFusion.

Switching from another web server

You can switch from an external web server to the built-in ColdFusion web server without reinstalling, even if you did not select it during installation.

Switch from an external web server to the built-in web server

1 Back up the jrun.xml file.

This file is in the cf_root\runtime\servers\default\SERVER-INF directory in Windows, and in the cf_root/runtime/servers/default/SERVER-INF directory in UNIX.

2 Open the original jrun.xml file for editing.

3 Locate the WebService service and set the deactivated attribute to false:

4 Locate the ProxyService service and set the deactivated attribute to true:

<service class="jrun.servlet.jrpp.JRunProxyService" name="ProxyService"> <attribute name="activeHandlerThreads">8</attribute> <attribute name="minHandlerThreads">1</attribute> <attribute name="maxHandlerThreads">1000</attribute> <attribute name="mapCheck">0</attribute> <attribute name="threadWaitTimeout">20</attribute> <attribute name="backlog">500</attribute> <attribute name="deactivated">true</attribute> ...

5 Save the file.

6 Copy the CFM pages in your web root directory (including the CFIDE and cfdocs directories) to the ColdFusion

cf_root/wwwroot directory, and use appropriate URL references (for example, http://localhost:8500/YourApp1/index.cfm). If you switch from the built-in web server to an external web server, copy the contents of the cf_root/wwwroot directory to your web server root. If you are using Adobe Dreamweaver, ensure that you reconfigure any sites that you move from one server to another.

7 Restart ColdFusion.

To switch to another web server, follow the instructions for the appropriate web server on your platform in “Configuring web servers” on page 61.

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Server Configuration

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

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.

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 1/20/2012

Chapter 3: Installing the Multiserver Configuration

The multiserver configuration deploys and configures ColdFusion on its own JRun server.

Gathering information necessary to install the multiserver configuration

Question Answer

Platform-specific installer name? ___________________________________________________

Serial number for ColdFusion? ___________________________________________________

Type of installation? ___ Server configuration

_X_ Multiserver configuration

___ J2EE configuration

Subcomponents to install? ___ ColdFusion 9 ODBC Services

___ ColdFusion 9 Search Services

___ColdFusion 9 Solr Services

___ .NET Integration Services

___ ColdFusion 9 Documentation

JRun 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 SunONE) ___________________________________________________

Path to server binary? (Apache) ___________________________________________________

___ IIS

___ Apache

___ Sun Java System Web Server

___ Other

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Multiserver Configuration

Question Answer

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

Note: You need to manually install LiveCycle Data Services ES on multiple server instances, in the same way as in the case of a single server installation. For more information about installing LiveCycle Data Services ES manually, see “Installing LiveCycle Data Services Manually” on page 51.

About multiserver configuration

When you install ColdFusion using the multiserver configuration, the installation wizard automatically deploys and configures ColdFusion on its own JRun server. This configuration supports server instance creation in the ColdFusion Administrator and lets you manage ColdFusion deployments on multiple JRun servers.

If you already have JRun 4 installed and you want to use the server instance creation feature of ColdFusion, you must uninstall it before you install the multiserver configuration of ColdFusion.

When you use the multiserver configuration, you can use the ColdFusion Administrator to 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.

For more information on configuring ColdFusion on multiple server instances, including detailed information for configuring multiple server instances when running on JRun 4, see the Configuring and Administering Adobe® ColdFusion® 9 guide.

For more information about J2EE servers, see “ColdFusion and J2EE application servers” on page 18.

Installing ColdFusion using the multiserver configuration

You must install ColdFusion using the multiserver configuration on a computer that has no earlier versions of JRun.

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Multiserver Configuration

During the multiserver installation procedure, the installation wizard performs the following actions:

• Installs JRun 4.

• Creates a JRun server named cfusion (in addition to the admin and samples JRun servers).

• (Windows) Creates and starts Windows services for the admin and cfusion JRun servers.

• Configures the jrun_root/bin/jvm.config file, as appropriate for the platform.

• (Optional) Configures the JRun cfusion server for use with an external web server. In Windows, the installation

wizard runs the Web Server Configuration Tool. In UNIX, the installation wizard creates a shell script that you can run to execute the Web Server Configuration Tool with the settings specified in the installation wizard.

Note: The default JRun web server port for the cfusion server is 8300. However, if you install the multiserver configuration of ColdFusion with the built-in server and port 8300 is in use, the installer starts with port 8301 and looks at up to 100 ports to find one that is not being used by an application that is running. ColdFusion uses that port and displays a message to indicate which port it selected.

Installing the multiserver configuration in Windows

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

Install the multiserver configuration in Windows

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 the “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 section “Gathering information necessary to install the multiserver

configuration” on page 11.

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 setup.exe file on the DVD

9 Follow the instructions in the installation wizard and let it run to completion. Ensure that you select Multiserver

configuration.

Note: The installation wizard disables the multiserver configuration option if JRun 4 is already installed on the computer.

10 Open the ColdFusion Administrator to configure the server.

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

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

page 48.

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

Resources page of the ColdFusion Administrator.

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Multiserver Configuration

14 Code CFM pages.

If you configured an external web server, store CFM pages under your web root directory. If you are using the builtin web server, store CFM pages under the web application root (jrun_root/servers/cfusion/cfusion-ear/cfusionwar) and access these pages using a URL of the form http://hostname:8300/context-root/filename.cfm, as follows:

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

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

on page 19.

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

For example, to display a CFM file located at C:\JRun4\servers\cfusion\cfusion-ear\cfusionwar\eisapp\index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://localhost:8300/cfusion/eisapp/index.cfm.

Installing the multiserver configuration in UNIX

Install the multiserver 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 the “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 multiserver

configuration” on page 11.

5 Log in as root.

6 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_9_WWE_linux.bin (for 32-bit systems)

• ColdFusion_9_WWE_linux64.bin (64-bit systems)

Solaris ColdFusion_9_WWE_solaris64.bin

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

8 Start the installation with the following command:

./<filename> -i console

The installation program starts.

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

9 Follow the instructions in the installation wizard. Ensure that you select Multiserver configuration.

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

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Multiserver Configuration

10 When the installation completes successfully, start the JRun cfusion server:

jrun_root/bin/jrun -start cfusion

11 If you specified external web server settings when you ran the installation wizard, run the jrun_root/bin/cfmx-

connectors.sh shell script. The script runs the Web Server Configuration Tool, which configures the web server for use with ColdFusion. The web server should also be running.

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 using the scripts in jrun_root/bin/connectors, or through java -jar jrun_root/lib/wsconfig.jar, as appropriate.

Note: This step is important, because if you specified the use of an external web server when you ran the installation wizard, the CFIDE and cfdocs directories are placed under that web server’s root directory, and you must successfully configure the web server before you open the ColdFusion Administrator.

12 Open ColdFusion Administrator to run the configuration wizard.

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

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.

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

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

on page 19.

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

For example, to display a CFM file located at /opt/jrun4/servers/cfusion/cfusion-ear/cfusionwar/eisapp/index.cfm using the built-in JRun web server and a context root of cfmx, you specify the URL as http://localhost:8300/cfmx/eisapp/index.cfm.

Configuration

In addition to enabling sandbox security in the ColdFusion Administrator, the application server must be running a security manager (

-Djava.security.manager

-Djava.security.policy="cf_webapp_root/WEB-INF/cfusion/lib/coldfusion.policy"

-Djava.security.auth.policy="cf_webapp_root/WEB-INF/cfusion/lib/neo_jaas.policy"

You configure these settings by using a text editor to modify the jrun_root/bin/jvm.config file. or through the Settings panel of the JRun Management Console (JMC).

java.lang.SecurityManager) and you must define the following JVM arguments:

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the Multiserver Configuration

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 9 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 9 application.

5 Browse to ColdFusion Administrator to run the migration wizard.

Uninstalling ColdFusion

The steps for uninstalling ColdFusion depend on your operating system.

Uninstall ColdFusion from Windows

1 Select Start > Settings > Control Panel > Add/Remove Programs > Adobe ColdFusion 9 with JRun 4.

2 Click Change/Remove.

3 When the program completes, remove any remaining files and directories in the cf_webapp_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.

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

cd cf_webapp_root/uninstall

3 Enter the following command:

./uninstall.sh

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

ColdFusion is deleted from your server.

Note: If you have UNIX on VMware, to uninstall, you must shut down ColdFusion and then remove it using the command as provided in the following example:

cd /opt and then rm -rf coldfusion9.

Last updated 1/20/2012

Chapter 4: 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

___ Multiserver configuration

_X_ J2EE configuration

EAR or WAR file? ___ EAR

___ WAR

Subcomponents to install? ___ ColdFusion 9 ODBC Services

___ ColdFusion 9 Search Services

___ .NET Integration Services

___ ColdFusion 9 Documentation

___ LiveCycle Data Services ES

Installation directory for EAR or WAR file? ___________________________________________________

Serial number for Adobe LiveCycle Data Services ES? (Only if you selected to install the Enterprise Edition of LiveCycle Data Services ES)

If you leave this blank, the installer installs the Express Edition. See the LiveCycle Data Services ES documentation for information on upgrading to the Enterprise Edition after completing the ColdFusion installation.

Whether the EAR/WAR is to be used with WebSphere (Only if you selected to install LiveCycle Data Services ES.)

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

___________________________________________________

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the J2EE Configuration

Question Answer

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

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:

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the J2EE Configuration

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

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 cf9, you display the ColdFusion Administrator using the URL http://localhost/cf9/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.

Note: Each web application running in a server instance must have a unique context root. The JRun default web application uses / for a context root, so if you want to use / for the ColdFusion context root when you deploy on JRun, either delete the default-war application or change the default-war context root by editing the default-ear/METAINF/application.xml file.

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 1/20/2012

INSTALLING COLDFUSION 9

Installing the J2EE Configuration

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

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.

“Installing ColdFusion using the

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

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.

“ColdFusion J2EE deployment and

Last updated 1/20/2012

INSTALLING COLDFUSION 9

Installing the J2EE Configuration

Installing an EAR file or WAR files in Windows

You can install the ColdFusion J2EE configuration in Windows. If you are updating an existing deployment of ColdFusion MX, ColdFusion MX 6.1, or ColdFusion MX 7 for J2EE, see on page 24 before you continue.

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.

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

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

configuration” on page 17

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 setup.exe file 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_9_WWE_win.exe (for 32-bit systems)/ColdFusion_9_WWE_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 25.

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

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

14 If using JRun, add the Log4J-1.2.12.jar file to the JRun server classpath (C:\Jrun4\servers\lib). By default, it is in the

ColdFusion classpath(C:\JRun4\servers\CF9\cfusion-ear\cfusion-war\WEB-INF\cfusion\lib).

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

Resources page of the ColdFusion Administrator.

16 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:

“Updating from an earlier version for J2EE”

• 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 19.

Last updated 1/20/2012

+ 57 hidden pages