MACROMEDIA COLDFUSION MX 61 - INSTALLING COLDFUSION MX FOR IBM WEBSPHERE APPLICATION... User manual

Installing and Using ColdFusion MX for
IBM® WebSphere®Application Server

Trademarks
Afterburner, AppletAce, Attain, Attain Enterprise Learning System, Attain Essentials, Attain Objects for Dreamweaver,
Authorware, Authorware Attain, Authorware Interactive Studio, Authorware Star, Authorware Synergy, Backstage, Backstage
Designer, Backstage Desktop Studio, Backstage Enterprise Studio, Backstage Internet Studio, ColdFusion, Design in Motion,
Director, Director Multimedia Studio, Doc Around the Clock, Dreamweaver, Dreamweaver Attain, Drumbeat, Drumbeat 2000,
Extreme 3D, Fireworks, Flash, Fontographer, FreeHand, FreeHand Graphics Studio, Generator, Generator Developer's Studio,
Generator Dynamic Graphics Server, JRun, Knowledge Objects, Knowledge Stream, Knowledge Track, Lingo, Live Effects,
Macromedia, Macromedia M Logo & Design, Macromedia Flash, Macromedia Xres, Macromind, Macromind Action, MAGIC,
Mediamaker, Object Authoring, Power Applets, Priority Access, Roundtrip HTML, Scriptlets, SoundEdit, ShockRave,
Shockmachine, Shockwave, Shockwave Remote, Shockwave Internet Studio, Showcase, Tools to Power Your Ideas, Universal
Media, Virtuoso, Web Design 101, Whirlwind and Xtra are trademarks of Macromedia, Inc. and may be registered in the United
States or in other jurisdictions including internationally. Other product names, logos, designs, titles, words or phrases mentioned
within this publication may be trademarks, servicemarks, or tradenames of Macromedia, Inc. or other entities and may be
registered in certain jurisdictions including internationally.
This product includes code licensed from RSA Data Security.
This guide contains links to third-party websites that are not under the control of Macromedia, and Macromedia is not
responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your
own risk. Macromedia provides these links only as a convenience, and the inclusion of the link does not imply that Macromedia
endorses or accepts any responsibility for the content on those third-party sites.
Apple Disclaimer
APPLE COMPUTER, INC. MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING THE
ENCLOSED COMPUTER SOFTWARE PACKAGE, ITS MERCHANTABILITY OR ITS FITNESS FOR ANY
PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES.
THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL
RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE.
Copyright © 2002–2003 Macromedia, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced,
translated, or converted to any electronic or machine-readable form in whole or in part without prior written approval of
Macromedia, Inc.
Part Number CT27MNA
Acknowledgments
Project Management: Randy Nielsen
Writing: Hal Lichtin, Randy Nielsen
Editing: Linda Adler, Noreen Maher
Third Edition: February 2003
Fourth Edition: September 2003
Macromedia, Inc.
600 Townsend St.
San Francisco, CA 94103

3
CONTENTS
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
About Macromedia ColdFusion MX documentation . . . . . . . . . . . . . . . . . . . . . . . 5
Documentation set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Viewing online documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
CHAPTER 1: Essential Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
About ColdFusion MX for IBM WebSphere Application Server . . . . . . . . . . . . . . . 8
Overview of the J2EE platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Overview of ColdFusion MX for IBM WebSphere Application Server . . . . . . . . 8
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Operating system and Java requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Additional requirements and software support . . . . . . . . . . . . . . . . . . . . . . . . . 10
Directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Differences between ColdFusion MX and ColdFusion MX on WebSphere . . . . . . 12
General ColdFusion MX feature differences . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Differences in directory locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Differences in the ColdFusion MX Administrator . . . . . . . . . . . . . . . . . . . . . . 14
Installing ColdFusion MX for IBM WebSphere Application Server. . . . . . . . . . . . 15
Considerations for all platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Considerations for Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Installation procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating and migrating applications on ColdFusion MX . . . . . . . . . . . . . . . . . . . 16
Learning about ColdFusion MX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Migrating existing ColdFusion applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
CHAPTER 2: Installing on WebSphere V5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing and deploying Macromedia ColdFusion MX . . . . . . . . . . . . . . . . . . . . . 18
Installing the ColdFusion MX files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Deploying ColdFusion MX on WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Running the Configuration and Settings Migration Wizard . . . . . . . . . . . . . . . 22
Enabling and configuring specific ColdFusion MX functionality . . . . . . . . . . . . . 23
Enabling features with operating system-specific binaries . . . . . . . . . . . . . . . . . 23
Enabling Access to COM objects (Windows only) . . . . . . . . . . . . . . . . . . . . . . 25
Enabling charting and graphing (UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Disabling RDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Undeploying ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 Contents
CHAPTER 3: Installing on WebSphere V4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Installing and deploying Macromedia ColdFusion MX . . . . . . . . . . . . . . . . . . . . . 30
Installing the ColdFusion MX files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deploying ColdFusion MX on WebSphere. . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Running the Configuration and Settings Migration Wizard . . . . . . . . . . . . . . . 35
Enabling and configuring specific ColdFusion MX functionality . . . . . . . . . . . . . 36
Enabling features with operating system-specific binaries . . . . . . . . . . . . . . . . . 36
Enabling sandbox security (AIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Enabling access to COM objects (Windows) . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Enabling charting and graphing (Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Supporting messages from a POP mail server (pre-FixPak 4) . . . . . . . . . . . . . . 40
Disabling RDS after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Undeploying ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
CHAPTER 4: Enabling and Using ColdFusion MX Features . . . . . . . . . . . . . . . . . 43
Enabling ColdFusion MX functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Installing Verity Search Packs for ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . 44
Enabling CORBA support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Enabling web services access for Flash Remoting . . . . . . . . . . . . . . . . . . . . . . . 46
Using a third-party JDBC database driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Managing ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Managing the ColdFusion MX application. . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Managing ColdFusion MX Windows services . . . . . . . . . . . . . . . . . . . . . . . . . 47
Using the / context root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Accessing the ColdFusion MX Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Migrating a ColdFusion application to IBM WebSphere Application Server . . . . . 49
Using RDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
About RDS configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Configuring RDS for a new ColdFusion MX context root . . . . . . . . . . . . . . . . 51

5
INTRODUCTION
Installing and Using ColdFusion MX for IBM WebSphere Application Server is intended for anyone
who needs to configure and manage their ColdFusion development environment.
About Macromedia ColdFusion MX documentation
The ColdFusion MX documentation is designed to provide support for the complete spectrum of
participants.
Documentation set
The ColdFusion MX documentation set includes the following titles:
Book Description
Installing and Using
ColdFusion MX for IBM
WebSphere
Application Server
Describes system installation and basic configuration for Windows NT,
Windows 2000, AIX, Linux, and Solaris.
Configuring and
Administering
ColdFusion MX
Part I describes how to use the ColdFusion MX Administrator to manage
the ColdFusion environment, including connecting to your data sources and
configuring security for your applications, Part II describes Verity search
tools and utilities that you can use for configuring the Verity K2 Server
search engine, as well as creating, managing, and troubleshooting Verity
collections.
Developing ColdFusion
MX Applications
Describes how to develop your dynamic web applications, including
retrieving and updating your data, using structures, and forms.
Getting Started
Building ColdFusion
MX Applications
Contains an overview of ColdFusion features and application development
procedures. Includes a tutorial that guides you through the process of
developing an example ColdFusion application.
CFML Reference Provides descriptions, syntax, usage, and code examples for all ColdFusion
tags, functions, and variables.
CFML Quick Reference A brief guide that shows the syntax of ColdFusion tags, functions, and
variables.

6 Introduction
Viewing online documentation
All ColdFusion MX documentation is available online in HTML and Adobe Acrobat Portable
Document Format (PDF) files. Go to the documentation home page for ColdFusion MX on the
Macromedia website: www.macromedia.com.

7
CHAPTER 1
Essential Information
This chapter describes Macromedia ColdFusion MX for IBM WebSphere Application Server and
provides information that applies to all WebSphere installations.
Contents
About ColdFusion MX for IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . . . . 8
System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Directory structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Differences between ColdFusion MX and ColdFusion MX on WebSphere
Installing ColdFusion MX for IBM WebSphere Application Server . . . . . . . . . . . . . . . . . . . . . 15
Creating and migrating applications on ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

8 Chapter 1: Essential Information
About ColdFusion MX for IBM WebSphere Application Server
Macromedia ColdFusion MX for IBM WebSphere Application Server enables you to add
ColdFusion MX capabilities to your Sun Java 2 Platform, Enterprise Edition (J2EE) application
server. It is a J2EE application that installs on top of your existing Java application server and
provides development, deployment, and management services for ColdFusion applications.
Overview of the J2EE platform
The J2EE platform is a set of detailed specifications and runtime services for developing
enterprise applications. A J2EE-compliant application is based on standardized, modular
components. J2EE provides these components with a complete set of services, and automatically
handles many details of the application behavior; for example, providing pluggable and scalable
database connection pooling and transparently managing web session clustering and failover.
J2EE provides a security model to protect your data and JDBC, an application programming
interface (API) to access your data. Also, J2EE is interoperable with other technologies that follow
the same modularized standard; for example, you can use Enterprise JavaBeans (EJBs), Java
Servlets, JavaServer Pages (JSP), and XML in your applications.
For more information, see http://java.sun.com/j2ee.
Overview of ColdFusion MX for IBM WebSphere Application Server
The ColdFusion MX for IBM WebSphere Application Server runtime environment is a Java
application that takes advantage of the services in the J2EE platform to connect to databases,
manage security, and process application requests. It provides the full scripting environment of
Macromedia ColdFusion MX and lets you develop fully featured Rich Internet Applications
rapidly and efficiently. When ColdFusion MX for IBM WebSphere Application Server is installed
on top of the WebSphere Application Server, it uses that server’s J2EE runtime to compile and
execute ColdFusion applications.
For more information about Macromedia ColdFusion MX, see the ColdFusion MX
documentation.
For information about differences between ColdFusion MX and ColdFusion MX for IBM
WebSphere Application Server on your operating system and application server version, see
“Differences between ColdFusion MX and ColdFusion MX on WebSphere” on page 12.
System requirements
This section lists the system requirements for ColdFusion MX for Windows and UNIX. This
information was up-to-date at the time this document was written. For any updates, see
www.macromedia.com/go/cfmxj2ee-cert.
Note: If you use Macromedia ColdFusion Studio to develop your web applications, note that
ColdFusion MX supports ColdFusion Studio versions 4.5.2 and 5.0 only.

System requirements 9
Operating system and Java requirements
The following table lists the operating systems supported by the ColdFusion MX for IBM
WebSphere Application Server editions. The following considerations also apply:
•The supported Java runtime environment is the default runtime installed with the application
server.
•Additional system update requirements follow the table.
For the most up-to-date list of certified platforms, see the Macromedia support site,
www.macromedia.com/support/coldfusion.
Include the following updates for your operating system:
•To use Microsoft Access or other databases that require an ODBC driver, on Windows NT 4.0
Server or Windows 2000 Server, you must have the following component installed: MDAC
2.5 SP1 (www.microsoft.com/data/download.htm).
•For all UNIX distributions, install the latest production-level patches, including the kernel,
from the supplier’s download sites: for Red Hat, ftp://ftp.redhat.com/pub; for SuSE, ftp://
ftp.suse.com/pub; for Solaris, http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-
access; for AIX, http://www.ibm.com/software/webservers/appserv/support.html.
•To use C++ CFXs with RedHat Linux 8.0, the Linux installation must have a RedHat libc
compatibility library such as the following:
RedHat-8.0 for i386 compat-libstdc++-7.3-2.96.110.i386.rpm
Users must have 7.3-2.* or later.
Edition Operating systems
IBM WebSphere 4 Windows NT 4.0 Server SP6A
Windows 2000 Server SP3
Windows 2000 Advanced Server SP3
Red Hat Linux 7.2
SuSE Linux 7.2
Solaris 7
Solaris 8
AIX 4.3.3
AIX 5L v5.1
IBM WebSphere 5 Windows NT 4.0 Server SP6A
Windows 2000 Server SP3
Windows 2000 Advanced Server SP3
Red Hat Linux 8.0
RedHat Advanced Server 2.1
SuSE Linux 7.3
Solaris 8
AIX 4.3.3
AIX 5L v 5.1

10 Chapter 1: Essential Information
Additional requirements and software support
The following table lists the hardware requirements, supported browsers, specific supported
application server editions, and supported databases for the various ColdFusion MX for IBM
WebSphere Application Server editions:
Category J2EE server Requirement
Minimum hardware
requirements
All Processor
Windows and Linux: Pentium
Solaris: SPARC
AIX: POWER/3
Minimum RAM
Developer Edition, Windows: 128 MB
All others: 256 MB
Recommended RAM
Developer Mode, Windows: 256 MB
All others: 512 MB
Free hard disk space
To deploy: 400 MB
To run: 250 MB
CD-ROM drive
Browsers supported for
ColdFusion MX
Administrator
All Internet Explorer 5.x, 6
Netscape 4, 6, 7
Mozilla 1.0
Supported Databases All JDBC drivers are included for the
following databases:
Oracle 8.1.6 - 8.1.7, 9i (R1 - R2)
Sybase 11.5 -11.9, 12, 12.5
DB2 for Windows, UNIX, and Linux v7.1,
v7.2, v8.1
DB2 for OS/390 v6.1, v7
Informix 9.2.x, 9.3.x, and 9.4
Microsoft SQL Server 7.0, 2000
MySQL
On Windows, drivers are included for :
Access 97, 98, 2000, 2003
ODBC socket, supports ODBC compliant
databases
Connectivity is provided for all databases
for which JDBC drivers compliant with the
JDBC 3.0 specification are available.

Directory structure 11
To use data sources that you configure in WebSphere and third-party JDBC drivers, see “Using a
third-party JDBC database driver” on page 46.
Directory structure
The ColdFusion root directory, referred to as cf_root, contains all ColdFusion software except for
Remote Development Services (RDS) support, which enables Macromedia Dreamweaver MX
and Macromedia HomeSite+ to access ColdFusion directly. RDS support is not recommended on
production servers.
If you install RDS support, it is located in a rds.war directory in the same parent directory as the
ColdFusion root directory.
The following table describes the contents of the root directory of ColdFusion MX for IBM
WebSphere Application Server. This table uses the backslash character (\) for directory paths; the
information is the same for UNIX, except that the directories are separated by forward slashes (/).
Supported Application
servers
IBM WebSphere 4 IBM WebSphere Advanced Edition,
Single Server 4.0.3, 4.0.4, or 4.0.5
Advanced Edition 4.0.3, 4.0.4, or 4.0.5
Note: FixPAK 3 or later is required
IBM WebSphere 5 IBM WebSphere Application Server 5.0
or 5.0.1
IBM WebSphere Application Server for
Developer 5.0 or 5.0.1
IBM WebSphere Application Server for
Network Deployment 5.0 or 5.0.1
Directory Contents
cfdocs Documentation for ColdFusion MX.
CFIDE Files for the ColdFusion MX Administrator.
META-INF Information about the application (might not contain substantial
information).
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\cftags Templates for ColdFusion MX.
WEB-INF\cfusion\bin Executable files used by ColdFusion MX.
WEB-INF\cfusion\cache Cached files.
WEB-INF\cfusion\cfx CFX tag include file and examples
WEB-INF\cfusion\charting Files for the ColdFusion MX graphing and charting engine.
WEB-INF\cfusion\Custom Tags Repository for your custom tags.
Category J2EE server Requirement

12 Chapter 1: Essential Information
Differences between ColdFusion MX and ColdFusion MX on
WebSphere
The following sections describe differences between the two configurations supported by
ColdFusion MX: the J2EE configuration and the server configuration. ColdFusion MX for IBM
WebSphere supports the J2EE configuration. Editions of ColdFusion MX available directly from
Macromedia also support the server configuration. These differences include:
General ColdFusion MX feature differences
Differences in directory locations
Differences in the ColdFusion MX Administrator
General ColdFusion MX feature differences
The following differences exist between the features that are available in the ColdFusion MX
server configuration and those that are available in ColdFusion MX for IBM WebSphere
Application Server:
For All operating systems
•The CFML GetMetricData() function is not supported.
•Your application must use relative paths to ensure that it works on any application server.
WEB-INF\cfusion\db Sample databases: in Windows, the files for sample Microsoft
Access databases and ODBC services. On UNIX, the files for the
sample Pointbase databases. Also includes software for installing
ODBC support and other database system specific files.
WEB-INF\cfusion\jintegra 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).
WEB-INF\cfusion\lib and WEB-
INF\lib
JAR, XML, property, and other files that are the foundation of
ColdFusion MX, including functionality such as queries, charting,
mail, security, Verity searches, and system probes.
WEB-INF\cfusion\logs ColdFusion MX log files.
WEB-INF\cfusion\Mail Files, including spool files, used by ColdFusion for mail.
WEB-INF\cfusion\registry Used only in UNIX, by the cfregistry tag.
WEB-INF\cfusion\stubs Contains compiled code for web services.
WEB-INF\cfusion\verity Verity collections.
WEB-INF\classes Java classes for the ColdFusion MX application.
WEB-INF\debug Files for debugging in ColdFusion MX.
WEB-INF\exception Files for exception handling in ColdFusion MX.
Directory Contents

Differences between ColdFusion MX and ColdFusion MX on WebSphere 13
•ColdFusion MX for IBM WebSphere Application Server requires a redirector web application
for RDS access if you do not deploy the ColdFusion MX web application at the / context root.
For more information, see “Using RDS” on page 50.
•ClusterCATS is not available; load-balancing is provided by your application server.
•On WebSphere 4, sandbox security cannot secure Java access to files and network resources.
For AIX
The following features are not supported on AIX:
•Verity search eng ine
•CFX tags written in C++
•CreateUUID uses Java random characters in place of the MAC address
•Crystal Report integration (cfreport tag)
•COM support
•ODBC support
For RedHat
The Verity search engine is not supported on RedHat Linux 8.0.
Differences in directory locations
This section compares directory locations for ColdFusion MX and ColdFusion MX for IBM
WebSphere Application Server.
Note: If you are developing a ColdFusion application on the ColdFusion MX server and you are
deploying it to IBM WebSphere Application Server, also see Chapter 4, “Migrating a ColdFusion
application to IBM WebSphere Application Server,” on page 49.
Location of ColdFusion MX root directory
In the ColdFusion MX server, the default location of the ColdFusion MX root directory, (referred
to as cf_root) is C:\CFusionMX in Windows and /opt/coldfusionmx on UNIX. For a description
of the contents of the cf_root directory for ColdFusion MX, see Installing and Using ColdFusion
MX on the ColdFusion MX Documentation page at www-3.ibm.com/software/webservers/
coldfusionmx/library.html.
In ColdFusion MX for IBM WebSphere Application Server, the location of the ColdFusion MX
root directory, where the ColdFusion web application is installed, differs depending on the
application server.
Note: For a description of the contents of the cf_root directory for IBM WebSphere Application
Server, see Chapter 1, “Directory structure,” on page 11.

14 Chapter 1: Essential Information
The following table lists the location of the root directory for the application servers:
Location of your ColdFusion application files
In ColdFusion MX, the ColdFusion application files are located under the web root directory; for
example, C:\InetPub\wwwroot. In ColdFusion MX for IBM WebSphere Application Server, your
ColdFusion application files belong under the cf_root directory. Your application server and its
configured web server will correctly handle your individual application files if they are located
under this directory.
Differences in the ColdFusion MX Administrator
The following table summarizes the differences in the ColdFusion MX Administrator between
ColdFusion MX and ColdFusion MX for IBM WebSphere Application Server:
Application server Windows location UNIX location
WebSphere 5 websphere_root\AppServer\
installedApps\node_name\
Macromedia ColdFusion
MX.ear\cfusion.war
websphere_root/AppServer/
installedApps/node_name/
Macromedia ColdFusion MX.ear/
cfusion.war
WebSphere 4 websphere_root\AppServer\
installedApps\cfusion.ear\
cfusion.war
websphere_root/AppServer/
installedApps/cfusion.ear/
cfusion.war
AIX websphere_root\AppServer\
installedApps\app_name\
cfusion.war
websphere_root/AppServer/
installedApps/app_name/
cfusion.war
Administrator component Status Notes
For all servers and operating systems
Server Settings > Java and
JVM
Removed Your application server handles these settings, not
ColdFusion MX.
Server Settings > Archives
and Deployment
Not
changed
This functionality might differ from what you would
expect from a J2EE application. For more information
about this feature, see the ColdFusion MX Administrator
online Help.
Data & Services > Data
Sources
Not
changed
This page might display the data sources that are
managed by your application server and by ColdFusion
MX. You cannot modify the data sources that are
managed by your application server on this page.
Debugging & Logging >
Debugging Settings
Changed The Enable Performance Monitor and Enable CFSTAT
options are not available. Performance monitoring is not
supported in ColdFusion MX for J2EE.
For WebSphere 4 and 5 on AIX
Data & Services > Verity
Collections
Inoperative Verity is not available, but the administrator pages
display. An attempt to set a value on these pages causes
an error message.
Data & Services > Verity K2
Server
Inoperative

Installing ColdFusion MX for IBM WebSphere Application Server 15
Installing ColdFusion MX for IBM WebSphere Application
Server
This section describes installation considerations and the overall installation procedure that apply
to all ColdFusion MX for IBM WebSphere Application Server editions.
Considerations for all platforms
The following are installation considerations for all platforms:
•In an optimal production environment, each ColdFusion MX application is hosted on a
dedicated server; database, mail, and other servers are not on the same computer.
•To interact with ColdFusion pages, components, and server-side ActionScript from a
Macromedia Flash movie, use the Macromedia Flash Remoting MX service in ColdFusion
MX. Although no special installations are required to develop ColdFusion applications for the
Flash Remoting MX service, you must install the Flash Remoting Components in the
Macromedia Flash MX authoring environment. The Flash MX authoring environment is
required to build applications that connect to and interact with the Flash Remoting MX
service in ColdFusion.
For more information on Flash Remoting MX, see Developing ColdFusion MX Applications,
available from the ColdFusion MX Documentation page at www-3.ibm.com/software/
webservers/coldfusionmx/library.html.
Considerations for Windows
The following are installation considerations for Windows:
•If you previously added a cf_root\bin or cf_root\verity\_nti40\bin directory to your system path
for ColdFusion 5, you must remove it before installing ColdFusion MX for J2EE. (For
instructions, see the Microsoft Windows online Help.) Otherwise, ColdFusion MX cannot
locate the correct Verity DLL files.
•Do not configure the server running ColdFusion MX as a primary domain controller (PDC)
or backup domain controller (BDC). Macromedia follows the Microsoft network model, in
which the first level is the PDC/BDC. These systems only manage the network or domain and
are not designed to run application servers. ColdFusion MX must reside on the second level of
Windows NT and Windows 2000 stand-alone systems. Stand-alone servers can participate in a
network or domain.
•Windows NT 4.0 Workstation and Windows 2000 Professional handle only 10 TCP/IP
connections concurrently. Therefore, Macromedia does not recommend using these operating
systems in a production environment; use Window NT 4.0 Server or Windows 2000 Server
instead.
Installation procedure
The ColdFusion MX for IBM WebSphere Application Server installation procedure depends on
your application server and the target operating system. The application server-specific
installation chapters detail these procedures.

16 Chapter 1: Essential Information
Creating and migrating applications on ColdFusion MX
This section describes resources that can help you get started creating ColdFusion MX
applications or migrating existing ColdFusion applications to ColdFusion MX on WebSphere
Application Server.
Learning about ColdFusion MX
If you are familiar with J2EE applications but you are a new ColdFusion MX user, there are
several sources of information that can help you to quickly begin using ColdFusion MX:
•Getting Started Building ColdFusion MX Applications
•Resources, including tutorials and example applications, that you can access from the Home
page of the ColdFusion MX Administrator
•The Get Started with ColdFusion MX page on the Macromedia website at
www.macromedia.com/go/cfresources.
Migrating existing ColdFusion applications
For information on migrating existing ColdFusion MX applications, including ColdFusion
applications to ColdFusion MX 6.1on IBM WebSphere, see Migrating ColdFusion Applications,
which is available at www.macromedia.com/go/cfmxmigration.

17
CHAPTER 2
Installing on WebSphere V5
Before you can use ColdFusion MX on IBM WebSphere Application Server V5, you must do the
following steps:
1Install the ColdFusion files.
2Deploy the ColdFusion J2EE application.
3Configure ColdFusion in the Configuration and Migration Wizard.
4Enable specific functionality required by ColdFusion applications, such as the Verity search
engine.
This chapter describes these steps in detail. It also describes how to undeploy ColdFusion MX.
Note: Check the Macromedia website at www.macromedia.com/go/cfmxj2ee-cert for any updates
to these installation instructions, or other late-breaking information.
This chapter uses the following conventions:
•websphere_root refers to the directory in which IBM WebSphere Application Server is installed;
for example, C:\Program Files\WebSphere in Windows, and /opt/WebSphere on UNIX.
•cf_root refers to the directory to which ColdFusion is deployed; for example, C:\Program
Files\WebSphere\AppServer\installedApps\MyHost\Macromedia ColdFusion
MX.ear\cfusion.war in Windows, and /opt/WebSphere/AppServer/installedApps/MyHost/
cfusion.ear/cfusion.war on UNIX.
Contents
Installing and deploying Macromedia ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Enabling and configuring specific ColdFusion MX functionality . . . . . . . . . . . . . . . . . . . . . . . 23
Undeploying ColdFusion MX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

18 Chapter 2: Installing on WebSphere V5
Installing and deploying Macromedia ColdFusion MX
Before you can run ColdFusion applications, you must complete the following procedures to
install and deploy ColdFusion MX to your application server:
1Installing the ColdFusion MX files
2Deploying ColdFusion MX on WebSphere
3Running the Configuration and Settings Migration Wizard
Note: This chapter describes how to install ColdFusion MX directly from the cfusion.ear file. You
can also install ColdFusion MX as a WAR file, but the process is more complex. To install using a
WAR file, you must expand the cfusion.ear file into its constituent WAR files and deploy the
cfusion.war file, specifying a context root in the WebSphere Administrative Console. If you do not
deploy ColdFusion at the / context root, you must also deploy the rds.war file and specify /CFIDE
as its context root.
Installing the ColdFusion MX files
The specific file you use to install ColdFusion MX for IBM WebSphere Application Server
depends on your operating system. The following table lists the supported operating systems and
the files on the product CD that you use to install ColdFusion MX:
Note: The installation files on the IBM website use the product part number as the filename. Also, the
AIX, Linux, and Solaris installation files on the website are in tar.gz zip archives; you must unzip these
archives to get the installable .bin files. If you use a downloaded file, replace the CD image filename in
the following instructions with the file you downloaded or downloaded and unzipped.
Use the following procedure to install the ColdFusion MX EAR file and installation
documentation.
To install ColdFusion MX files:
1Ensure that your system environment meets the system requirements described in Chapter 1,
“Essential Information,” on page 7.
2Review the section “Installing ColdFusion MX for IBM WebSphere Application Server”
on page 15.
3Read the Release Notes for any late-breaking information or updates.
Operating system Installation file
Full Product
Windows coldfusion-61-ibm-win.exe
Linux coldfusion-61-ibm-linux.bin
Solaris coldfusion-61-ibm-solaris.bin
AIX coldfusion-61-ibm-other.jar
Evaluation only
Windows coldfusion-61-ibm-eval-win.exe
Linux coldfusion-61-ibm-eval-linux.bin
Solaris coldfusion-61-ibm-eval-solaris.bin
AIX coldfusion-61-ibm-eval-other.jar

Installing and deploying Macromedia ColdFusion MX 19
4Close any applications that are currently running on the computer to which you are deploying
ColdFusion MX.
5If you have the ColdFusion MX for IBM WebSphere Application Server evaluation or product
CD-ROM, insert the CD. Otherwise, download the installer file for your platform from the
IBM website or a designated network.
6Start the installation program. Do one of the following, depending on your operating system:
7Follow the instructions in the installation program. Use the following information to complete
certain sections of the installation program:
■Before installing, determine the location of a working directory into which the ColdFusion
MX for J2EE EAR file should be installed.
■The initial installer screen lets you select the language for the installer. This selection also
determines the language for the online Help and installed documentation.
■On the License Agreement page, you must select I accept the terms of the License
Agreement before you can click Next.
■On the Install Type page, select whether you are updating a ColdFusion MX installation to
ColdFusion MX 6.1, or installing a new version of ColdFusion MX. If you select the
Update option, the installer backs up your application files, including configuration files.
This is required because you must undeploy your ColdFusion application as part of the
update procedure. You then use the backup files to restore the application.
■ColdFusion asks you for the directory in which to install the files. These files are required to
deploy ColdFusion on WebSphere, but are not required afterward. Therefore, you can
specify a staging area or temporary file location.
System Procedure
AIX Set the working directory to the directory that contains the JAR file
listed in the preceding table. Enter one of the following commands,
replacing java_home with the path to the bin directory for your JRE
installation:
In GUI mode (you must have XWindows Display configured):
java_home/java -jar coldfusion-61-ibm-other.jar -i gui
or, for the evaluation version:
java_home/java -jar coldfusion-61-ibm-eval-other.jar -i gui
In console mode:
java_home/java -jar coldfusion-61-ibm-other.jar -i console
or, for the evaluation version,
java_home/java -jar coldfusion-61-ibm-eval-other.jar -i console
Windows Double-click the installer file.
Solaris or Linux Set the working directory to the directory that contains the installer file
listed in the preceding table.
In GUI mode (you must have XWindows Display configured), enter the
installer file for your operating system, followed by the -i gui switch; for
example:
./coldfusion-61-ibm-linux.bin -i gui
In console mode, enter the installer file for your operating system,
followed by the -i console switch; for example:
./coldfusion-61-ibm-linux.bin -i console

20 Chapter 2: Installing on WebSphere V5
■If you specify an update installation, the installer asks you to select the directory in which to
back up your ColdFusion application files, and the location where you deployed the
ColdFusion MX web application you want to back up, such as C:\Program
Files\WebSphere\AppServer\installedApps\MyNode\Macromedia ColdFusion
MX.ear\cfusion.war. If you have multiple ColdFusion MX web applications, you must run
the installer once for each web application, to ensure that all files get backed up properly,
and specify a different backup directory each time.
Note: Do not specify a backup directory that is inside your current application directory. For
example, do not specify a directory such as C:\Program Files\WebSphere\AppServer\
installedApps\MyNode\Macromedia ColdFusion MX.ear. When you deploy the updated
version of ColdFusion MX, you first undeploy your old version of ColdFusion, which deletes files
in the application directory.
■On the Context Root page, specify a name for the ColdFusion MX application context
root. The context root is the first part of the URL for all requests sent to the application. The
application server uses the context root to determine which web application must service an
incoming request The default value is cfmx. For information, see “Using the / context root”
on page 48.
■In the ColdFusion MX Administrator password page, enter the password to require for the
ColdFusion MX Administrator.
■Review the options in the Pre-Installation Summary section and accept them to complete
the installation.
When the installation is complete, the EAR file and any backup files are put in the specified
locations. The installation wizard exits and a product registration page appears. Continue with
the next section of the instructions, “Deploying ColdFusion MX on WebSphere”.
Note: The installer creates the following log file: install_root/
Macromedia_ColdFusion_MX_J2EE_InstallLog.log, where install_root is the directory that you
specify when you install the ColdFusion MX files. If you contact Technical Support for installation
support, you must send them this log file.
Deploying ColdFusion MX on WebSphere
This section describes how to deploy ColdFusion MX on WebSphere 5.
To deploy ColdFusion MX on WebSphere 5:
1Start the IBM WebSphere Application Server, if it is not running.
2Open the Run the IBM WebSphere Administrative Console, if it is not running.
3If you are updating an existing ColdFusion MX application, you must uninstall the existing
copy of ColdFusion. Do the following:
aIn Windows, if the ODBC services are installed, open the Services panel and make sure that
the ColdFusion MX ODBC server and the ColdFusion MX ODBC agent are stopped.
bOn the WebSphere Administrative Console Applications > Enterprise Applications page,
select the ColdFusion application (the default name is Macromedia ColdFusion MX). If the
application is running, click stop; when it has stopped, select it again. Click Uninstall.