Installing and Using ColdFusion MX
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,
CONTENTS INTRODUCTION . ................................................... 5 About Macromedia ColdFusion MX documentation . . . . . . . . . . . . . . . . . . . . . . . 5 Documentation set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Viewing online documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 CHAPTER 1: Essential Information . . .................................... 7 About the ColdFusion MX 6.
CHAPTER 3: Installing the J2EE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 J2EE application servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Choosing EAR or WAR deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Context root. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Multiple instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTRODUCTION Installing and Using ColdFusion MX is intended for anyone who needs to install and configure ColdFusion MX 6.1. About Macromedia ColdFusion MX documentation The ColdFusion MX documentation is designed to provide support for the complete spectrum of participants. Documentation set The ColdFusion documentation set includes the following titles: Book Description Installing and Using ColdFusion MX Describes system installation and basic configuration for Windows, Solaris, Linux, and HP-UX.
Introduction
CHAPTER 1 Essential Information This chapter describes Macromedia ColdFusion MX 6.1 product editions, system requirements, and other high-level considerations. Contents About the ColdFusion MX 6.1 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ColdFusion MX 6.1 product editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About the ColdFusion MX 6.1 installation ColdFusion MX 6.1 provides a powerful and flexible installation and upgrade process. The ColdFusion MX 6.1 installation process includes the following phases: 1 Plan the installation You determine your installation, configuration, and upgrade options. You run the ColdFusion MX 6.1 installer. 3 (J2EE configuration only) Deploy ColdFusion MX You deploy and configure ColdFusion MX on your J2EE application server.
ColdFusion MX 6.1 product editions The following table describes each edition of ColdFusion MX 6.1: Edition Description Licensing Developer For Windows and Linux. • Supports requests from the local host and one remote IP address • Includes every feature in the Enterprise Edition, with the following exceptions: • A 10K Verity document search • No HTTP-based load-balancing and failover using Macromedia ClusterCATS If you install ColdFusion MX 6.
Edition Description Licensing Enterprise For Windows, Linux, Solaris, and HP-UX.
System requirements for Windows This section lists the Windows system requirements for the Macromedia ColdFusion MX 6.1 Developer, Standard, and Enterprise Editions. An “x” in the following table means that the edition supports the requirement in that row. Developer Edition Standard Edition Enterprise Edition Windows 98* x x x Windows Millennium Edition (ME)* Requirement Windows version x x Windows NT 4.
Developer Edition Standard Edition Enterprise Edition Sun JDK/JRE 1.3.1 or later x x x IBM JVM 1.2.2–1.3 or later x x x Internet Explorer 5.x, 6 x x x Netscape Communicator 4, 6 x x x Mozilla 1.0 x x x Requirement Java Virtual Machine (JVM) Note: ColdFusion MX 6.1 ships with the Sun 1.4.2 JVM. Browsers for ColdFusion MX Administrator Databases Oracle 8i R2-R3 (8.1.6 - 8.1.7) Oracle 9i R1-R2 x Sybase Adaptive Server 11.5 and higher Sybase Adaptive Server Enterprise 12.0 and 12.
System requirements for UNIX This section lists the UNIX system requirements for the Macromedia ColdFusion MX 6.1 Developer, Standard, and Enterprise Editions. An “x” in the following table means that the edition supports the requirement in that row. Standard Edition Enterprise Edition x Red Hat Linux 7.2, 7.3, 8.0, 9 RedHat Linux AS 2.1 Install the latest patches (including the kernel and those listed in “Configuring Your System” on page 49) from ftp://ftp.redhat.
Requirement Developer Edition Standard Edition Enterprise Edition Apache web server 1.3.22–1.3.27, 2.0.43 or higher x x x Netscape Enterprise Server 3.6x x x x iPlanet 4.x SunONE Web Server 6.x (formerly iPlanet 6.x x x x Sun JDK/JRE 1.3.1 or later x x x IBM JVM 1.3 or later x x x Internet Explorer 5.x, 6 x x x Netscape Communicator 4, 6 x x x Mozilla 1.0 x x x Java Virtual Machine (JVM) Note: ColdFusion MX 6.1 ships with the Sun 1.4.2 JVM.
J2EE configuration requirements This section lists additional system requirements for Windows and UNIX when running in the J2EE configuration. This information was up-to-date at the time this document was written. For any updates, see www.macromedia.com/go/cfmxj2ee-cert. Operating system and Java requirements The following table lists the J2EE application servers supported by ColdFusion MX when running in the J2EE configuration.
Edition Operating systems Macromedia JRun 4 Windows NT 4.0 Server SP6A Windows 2000 Professional SP2 Windows 2000 Server SP2 Windows 2000 Advanced Server SP3 Windows XP Professional Windows 2003 Red Hat Linux 7.2, 7.3, 8.0, 9.0 RedHat Advanced Server 2.1 SuSE Linux 7.3 Turbo Linux 8 (JA only) Solaris 7, 8, 9 Sun ONE Application Server 7 Windows NT 4.0 Server SP6A Windows 2000 Server SP2 Windows 2000 Advanced Server SP2 Windows XP Red Hat Linux 7.2, 7.
• • • • You can switch to use a different web server for ColdFusion MX after the installation, by following the instructions for your platform and the web server in “Configuring web servers” on page 53. However, if you configure the web server that uses ColdFusion 5 to use ColdFusion MX instead, ColdFusion 5 will be disabled. During installation of the server configuration, if you select the built-in web server, your web root directory is C:\CFusionMX\wwwroot by default.
Installation considerations for UNIX The following are installation considerations for UNIX only: • For troubleshooting purposes, the installer creates the following log file during an installation • 18 or upgrade on UNIX: cf_root/Macromedia_ColdFusion_MX_install.log. If you contact Macromedia Technical Support for installation support, you must send them this file. If you are deploying the J2EE configuration on a platform other than Linux or Solaris, use the coldfusion-61-other.jar installer.
CHAPTER 2 Installing the Server Configuration This chapter describes how to install and uninstall ColdFusion MX 6.1 in the server configuration. The ColdFusion MX 6.1 server configuration contains an embedded copy of JRun and is most similar to previous ColdFusion versions. Note: In this chapter, cf_root refers to your installation directory. By default, this directory is C:\CFusionMX in Windows, and /opt/coldfusionmx on UNIX. Contents Installing ColdFusion MX 6.1 . . . . . . . . . . . . . . . . . . . . .
Installing ColdFusion MX 6.1 This section provides installation instructions for the ColdFusion MX 6.1 server configuration on Windows and UNIX. When installing the server configuration, you have the following options: • • New installation Select this option if you do not have ColdFusion MX on the computer or if you have ColdFusion 4.5 or 5 on the computer. Update existing ColdFusion MX Select this option if ColdFusion MX is already installed on the computer.
Question Answer UNIX Runtime user Default is nobody (HP-UX must change this value). For security reasons, it is crucial that you do not use root for the runtime user. Start at system startup (Solaris and RedHat Linux only) Yes | No After running the installer, you must complete the installation process by running the Configuration Wizard. You start the Configuration Wizard by opening the ColdFusion MX Administrator. You should also plan your answers to the questions asked by the Configuration Wizard.
Question Answer Comment Upgrade from ColdFusion 4.5 or ColdFusion 5 Migrate existing settings? Yes | No Migrate client variables in registry? Yes | No Unless you are storing client data that must be preserved, Macromedia recommends that you do not migrate these variables. Installing ColdFusion MX 6.1 on Windows This section explains how to install ColdFusion MX 6.1 in a Windows platform. Note: The Windows installer requires a computer that supports at least 256 colors. To install ColdFusion MX 6.
b Open cf_root/lib/adminconfig.xml (server configuration) or cf_root/WEB- INF/cfusion/lib/adminconfig.xml (J2EE configuration) in a text editor, change runmigrationwizard (migrate ColdFusion 5 settings) and runmxmigrationwizard (migrate the ColdFusion MX ODBC services to ColdFusion MX 6.1) to true, as necessary, and save the file. c Restart the ColdFusion MX Administrator from the Windows Start menu. You are prompted again to migrate your settings.
To install ColdFusion MX 6.1 on UNIX: 1 Read the online version of the Release Notes for any late-breaking information or updates. For more information, see www.macromedia.com/go/proddoc_releasenotes. 2 Make sure that your operating system meets the system requirements described in “System requirements for UNIX” on page 13. 3 Review the “Installation considerations for UNIX” on page 18. 4 If you plan to configure an external web server, ensure that the web server is running.
14 Open the ColdFusion MX Administrator in a browser, using http://localhost/CFIDE/administrator/index.cfm if you configured an external web server and http://localhost:8500/CFIDE/administrator/index.cfm if you are using the built-in web server. Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time. Note: If you are accessing ColdFusion MX 6.
4 Mount the CD drive, as follows: /usr/sbin/pfs_mount /SD_CDROM The CD appears under /SD_CDROM.
Directory Description verity Verity collections. (The Verity program files are in the lib directory.) 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 MX 6.
Switching from another web server You can switch from an external web server to the built-in ColdFusion MX web server without reinstalling, even if you did not select it during installation. To 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 on UNIX. 2 Open the original jrun.xml file for editing.
Uninstalling ColdFusion MX 6.1 The steps for uninstalling ColdFusion MX 6.1 depend on your operating system. This section contains instructions for Windows and UNIX. Uninstalling ColdFusion MX 6.1 from Windows Uninstalling ColdFusion MX 6.1 deletes all program files and related components from your computer. To uninstall ColdFusion MX 6.1 from Windows: 1 Select Start > Settings > Control Panel > Add/Remove Programs > Macromedia ColdFusion MX. 2 Uninstall ColdFusion MX.
Chapter 2: Installing the Server Configuration
CHAPTER 3 Installing the J2EE Configuration This chapter describes how to install, deploy, and undeploy Macromedia ColdFusion MX Enterprise Edition in the J2EE configuration. It includes overview information, specific instructions for installing Macromedia JRun 4 (which automatically deploys and configures ColdFusion MX), and general instructions for use with all J2EE application servers. Contents J2EE application servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
J2EE application servers One of the main advantages of ColdFusion MX is that it can be installed as an integrated server (the server configuration) or deployed as a Java application on a standards-based J2EE application server (the 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.
If your J2EE application server supports enterprise applications, you should install and deploy the EAR file. For more information, see “Installing an EAR file or WAR files” on page 39. Note: The instructions in this chapter apply to the ColdFusion MX J2EE configuration. The ColdFusion MX server configuration contains an embedded version of JRun, which uses ColdFusion-specific JRun configuration options and mappings.
Platforms Full ColdFusion MX functionality is available on Windows, Linux, and Solaris. Additionally, you can install and deploy the all-Java ColdFusion MX J2EE configuration on other platforms, although without the functionality provided by platform-specific binary files (Verity and C++ CFXs). Preparing to install using the J2EE configuration This section provides installation instructions for the ColdFusion MX J2EE configuration.
Question Answer JRun4 install JRun Management Console (JMC) username and password ______________________________________________ Planned location of JRun directory? ______________________________________________ Will you configure an external web server (such as Apache or IIS)? Yes | No (Apache and iPlanet) Configuration directory? ______________________________________________ (Apache) Path to server binary? ______________________________________________ If using an external web server, locatio
Question Answer Comment Install example applications and getting started tutorial application? Yes | No ColdFusion MX ships with a variety of example applications. Installing the example applications also installs the supporting files used by the Getting Started Building ColdFusion MX Applications tutorial lessons. Do not use the example applications if you are installing into a production environment.
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 CD or download the setup file from the Macromedia website. 8 If the installation wizard does not start automatically when you insert the CD, locate setup.exe on the CD and double-click it. If you are installing from a network or a downloaded file, locate the ColdFusion MX 6.1 installation executable file (coldfusion-61-win.
To install the J2EE configuration with JRun on UNIX: 1 Read the online version of the Release Notes for any late-breaking information or updates. For more information, see www.macromedia.com/go/proddoc_releasenotes. 2 Ensure that your operating system meets the system requirements described in “System requirements for UNIX” on page 13. 3 Review the “Installation considerations for UNIX” on page 18.
13 Open the ColdFusion MX Administrator in a browser, using http://localhost/context- root/CFIDE/administrator/index.cfm (external web server) or http://localhost:8300/contextroot/CFIDE/administrator/index.cfm (built-in JRun web server). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time. Note: If you are accessing ColdFusion MX 6.
Installing an EAR file or WAR files in Windows This section explains how to install the ColdFusion MX 6.1 J2EE configuration in a Windows platform. If you are updating an existing deployment of ColdFusion MX for J2EE, see “Updating from ColdFusion MX for J2EE” on page 42 before continuing. Note: The Windows installer requires a computer that supports at least 256 colors. To install ColdFusion MX 6.
contextroot The context root for the ColdFusion MX web application. For more information, see “Context root” on page 33. ■ 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\default\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://127.0.0.1:8100/cfmx/eisapp/index.cfm.
10 Deploy ColdFusion MX 6.1 and configure Java settings, as required by your application server. For more information, see “ColdFusion MX J2EE deployment and configuration” on page 43. 11 Open the ColdFusion MX Administrator in a browser (http://hostname:portnumber/context- root/CFIDE/administrator/index.cfm). Because opening the ColdFusion MX Administrator for the first time automatically invokes the Configuration Wizard, it is best to open the Administrator at this time.
• If you don’t run the Configuration Wizard, you can run it later by performing the following steps: a Close the ColdFusion MX Administrator. b Open cf_root\WEB-INF\cfusion\lib\adminconfig.xml in a text editor, change runmxmigrationwizard and runsetupwizard to true, as necessary, and save the file. c Restart the ColdFusion MX Administrator.
To deploy ColdFusion MX as an enterprise application on JRun 4: 1 Run the installation wizard for your platform, as described in “Installing an EAR file or WAR files” on page 39. Select the EAR option. When you get to the deployment step, return to these instructions. If you are updating an existing deployment of ColdFusion MX for J2EE, you must undeploy ColdFusion MX for J2EE before deploying ColdFusion MX 6.1, as described in “Updating from ColdFusion MX for J2EE” on page 42.
5 Continue with the procedure from the Configuration Wizard step, as described in “Installing an EAR file or WAR files” on page 39. Expanding and deploying WAR files on JRun 4 Although it is best to deploy ColdFusion MX as an enterprise application, you can also deploy ColdFusion MX as a web application. When deploying ColdFusion MX as a web application on an existing JRun server, you expand the cfusion.war file, deploy it, and optionally modify the context root.
Depending on your operating system, you might have to add the following to the java.args JVM argument: • COM (Windows only) Add the following arguments: -DJINTEGRA_NATIVE_MODE -DJINTEGRA_PREFETCH_ENUMS • CORBA (optional) Copy vbjorb.jar to WEB-INF/cfusion/lib and define the following argument: -Xbootclasspath/a:"cf_root/WEB-INF/cfusion/lib/vbjorb.
Directory Description WEB-INF/cfusion/bin Executable files used by ColdFusion MX. 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. 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.
Chapter 3: Installing the J2EE Configuration
CHAPTER 4 Configuring Your System This chapter describes how to manage ColdFusion MX services and processes, how to configure web servers manually, and how to change user accounts and configure databases for ColdFusion MX. Note: In this chapter, cf_root refers to your installation directory. By default, this directory is C:\CFusionMX in Windows, and /opt/coldfusionmx on UNIX. Contents Overview of configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of configuration tasks The following table describes when to do the configuration tasks that are documented in this chapter: Configuration task When to do it “Managing ColdFusion MX” on page 51 You must stop and restart ColdFusion MX after you enable or disable security in the ColdFusion MX Administrator or change any of the Java and JVM settings, in order for your changes to take effect. You can do this at any time after you install ColdFusion MX 6.1.
Managing ColdFusion MX The ColdFusion MX installation creates a few services in Windows and a single process on UNIX. The following sections describe how to manage them: • “Managing ColdFusion MX services in Windows” on page 51 • “Managing the ColdFusion MX process on UNIX” on page 53 Managing ColdFusion MX services in Windows This section describes the ColdFusion MX services and explains how to manage them.
To start or stop a ColdFusion service: 1 Open the Services dialog box: In Windows NT 4.0, select Start > Settings > Control Panel > Services. In Windows 2000, Windows XP, or Windows 2003, select Start > Settings > Control Panel > Administrative Tools > Services. ■ For other Windows platforms, see the Windows online Help. If a service is running, its status appears as Started in the Status column. If it is not running, no status appears for the service.
Managing the ColdFusion MX process on UNIX This section describes the ColdFusion MX process and explains how to manage it. Note: This discussion applies to the ColdFusion MX server configuration only. Under the J2EE configuration, you start and stop ColdFusion MX by starting the application server. Overview of the ColdFusion MX process The ColdFusion MX installation creates a single process on UNIX called cfusion.
Tip: ColdFusion MX provides batch files and shell scripts in the cf_root/bin/connectors directory to help you get started with command-line usage. For more information on the Web Server Configuration Tool, including information on multihoming and distributed usage, see Configuring and Administering ColdFusion MX. Note: If you cannot verify your configuration, repeat the procedure.
To verify your IIS configuration: 1 Verify that the following file was created: cf_root\runtime\lib\wsconfig\jrun.dll (server configuration) or jrun_root/lib/wsconfig/jrun.dll (JRun J2EE configuration). On IIS6, this file is named jrun_iis6.dll. 2 For each of your IIS websites, verify that application mappings for .cfm, .cfml, .cfc, .jsp, and .jws were added, as follows: a In IIS, right-click an IIS website and select Properties.
To configure Netscape or iPlanet for ColdFusion MX in Windows: 1 Start the Web Server Configuration Tool by selecting Start > Programs > Macromedia ColdFusion MX > Web Server Configuration Tool from the Start menu. 2 Click Add. 3 In the Server drop-down list box, select the host name and the server or cluster name to configure. For the ColdFusion MX server configuration, this is always default. Clustering support is only available on the JRun J2EE configuration.
3 In the Server drop-down list box, select the host name and the server or cluster name to configure. For the ColdFusion MX server configuration, this is always default. Clustering support is only available on the JRun J2EE configuration. Note: The server or cluster does not have to reside on the web server computer. 4 In the Web Server Properties area, select Apache and specify the path to the directory that contains the httpd.conf file. 5 Select Configure web server for ColdFusion MX applications.
Configuring web servers on UNIX This section explains how to configure the following web servers on UNIX: • Configuring Apache web server on UNIX • Configuring Netscape or iPlanet web server on UNIX Configuring Apache web server on UNIX This section describes how to configure the Apache web server for ColdFusion MX on UNIX, and how to verify your configuration. Note: When running the Web Server Configuration Tool on the JRun J2EE configuration, wsconfig.jar is located in jrun_root/lib.
Configuring Netscape or iPlanet web server on UNIX This section describes how to configure Netscape Enterprise web server 3.6x or iPlanet web server (4.x or 6.x) for ColdFusion MX on UNIX, and how to verify your configuration. Note: When running the Web Server Configuration Tool on the JRun J2EE configuration, wsconfig.jar is located in jrun_root/lib. You can also use the scripts in cf_root/bin/connectors, modifying them, as appropriate for your environment.
Installing Verity Locales ColdFusion MX lets you do Verity searches for languages other than English. For European languages, ColdFusion uses LinguistX technology from Inxight, and for Asian languages, ColdFusion uses ICU (IBM Classes for Unicode) technology. For more information on Verity, see Configuring and Administering ColdFusion MX. This section describes how to install a Verity Locales package from the Macromedia website, and how to switch to a different Verity Locales package.
Installing Visibroker for CORBA connections To install Visibroker for CORBA connections: 1 Install Visibroker on the CORBA server side. For more information, see the Borland Visibroker documentation. 2 Add the vbjorb.jar file to the ColdFusion MX classpath, as follows: a In the ColdFusion MX Administrator, select Server Settings > Java and JVM. When using the J2EE configuration, you add the vbjorb.jar file to the J2EE application server classpath, using the server-specific method.
4 Prepare your CORBA server side, as follows: a Start your Visibroker osagent service or process, if it is not already running, by entering the following command: osagent Note: If you must connect to an osagent in another subnetwork, include the following lines in the vbjorb.properties file: vbroker.agent.addr= vbroker.agent.
4 Save the file. 5 Restart ColdFusion MX. For more information, see “Starting and stopping services” on page 51 for Windows, or “Managing the process” on page 53 for UNIX. RDS is disabled on the ColdFusion MX server. Disabling JSP functionality ColdFusion MX Enterprise Edition provides support for JavaServer Pages (JSP) technology via the underlying J2EE application server on which it runs.
4 In the Open dialog box, browse to compmgmt.msc, the Computer Management console file (usually located in the system or system32 directory). Click Open. The MMC for Computer Management appears: 5 On the Tree tab, under Services and Applications, click Services. All of the services for your computer appear in the right pane. 6 Right-click ColdFusion MX Application Server and select Properties. The ColdFusion MX Application Server Properties (Local Computer) dialog box appears.
Enabling web services access for Flash Remoting By default, Flash Remoting cannot access ColdFusion MX 6.1 through web services. To enable Flash Remoting to access ColdFusion MX 6.1 through web services: 1 Open the cf_root/wwwroot/WEB-INF/web.xml file in a text editor. In the J2EE configuration, open cf_root/WEB-INF/web.xml. 2 Locate the servlet definition for FlashGateway and change the DISABLE_CFWS_ADAPTERS init-param from true to false, as follows: FlashGateway .
Configuring RedHat Linux 7.3, 8.0, and 9 To use C++ binaries on RedHat Linux 7.3, 8.0, or 9, the Linux installation must have the corresponding RedHat libc compatability libraries to run ColdFusion MX 6.1, as follows: • RedHat-9 for i386 compat-libstdc++-7.3-2.96.118.i386.rpm • RedHat-8.0 for i386 compat-libstdc++-7.3-2.96.110.i386.rpm • RedHat-7.3 for i386 compat-libstdc++-6.2-2.9.0.16.i386.rpm Users must have 6.2-2.* or better for RedHat 7.3, or 7.3-2.* for RedHat 8.0 or 9.
INDEX Numerics 256 color minimum for installer 22, 35 A Apache web server configuring in Windows 56 configuring on UNIX 58 application isolation 33 application.xml file, web-uri element 44 B backup directory for J2EE update install 35 built-in web server using 27 using with external web server 28 C C++ CFX support JVM arguments for J2EE 45 RedHat Linux libraries 66 CD-ROM drive, mounting on HP-UX 25 CFIDE, renamed by update install 20 cfmx-connectors.
F failover 33 Flash Remoting, overview 17 G glibc, Verity requirements 66 H hosting, disabling JSPs 63 HP-UX, mounting CD-ROM drive on 25 I IIS configuring 54 IIS6 55 installing ColdFusion MX considerations for UNIX 18 considerations for Windows 17 general considerations 16 in Windows 22, 36, 40 on UNIX 23, 38, 41 internal web server 27 iPlanet web server configuring in Windows 55 configuring on UNIX 59 J J2EE configuration all-Java version 34 ClusterCATS not supported 34 deployment 43 directory structure 4
T tools.
Index
