User Guide
Table Of Contents
- Contents
- Introduction
- Administering ColdFusion MX 7
- Administering ColdFusion MX
- Using the ColdFusion MX Administrator
- Contents
- Initial administration tasks
- Accessing user assistance
- Server Settings section
- Data & Services section
- Debugging & Logging section
- Extensions section
- Event Gateways section
- Security section
- Packaging and Deployment section
- Enterprise Manager section
- Custom Extensions section
- Administrator API
- Data Source Management
- Contents
- About JDBC
- Adding data sources
- Connecting to DB2 Universal Database
- Connecting to Informix
- Connecting to Microsoft Access
- Connecting to Microsoft Access with Unicode
- Connecting to Microsoft SQL Server
- Connecting to MySQL
- Connecting to ODBC Socket
- Connecting to Oracle
- Connecting to other data sources
- Connecting to Sybase
- Connecting to JNDI data sources
- Web Server Management
- Deploying ColdFusion Applications
- Administering Security
- Using Multiple Server Instances
- Administering Verity
- Introducing Verity and Verity Tools
- Indexing Collections with Verity Spider
- Using Verity Utilities
- Contents
- Overview of Verity utilities
- Using the mkvdk utility
- Using the rck2 utility
- Using the rcvdk utility
- Using the didump utility
- Using the browse utility
- Using the merge utility
- Index
Defining additional server instances 93
Defining additional server instances
The multiserver configuration is a customized installation of JRun. JRun supports multiple server
instances (also called JRun servers) running on the same computer. Each server instance runs in a
separate JVM, which executes all ColdFusion pages for that instance.
You use the Instance Manager area of the ColdFusion MX Administrator to define and manage
server instances. The Instance Manager only runs in the cfusion JRun server that is created as part
of a multiserver configuration installation.
When you create a server instance with the Instance Manager, by default it deploys a copy of the
cfusion server’s ColdFusion enterprise application, including data sources, mappings, and
settings. Alternatively, you can create a new server instance and specify the location of an EAR or
WAR file (created by the J2EE Archive page), which the Instance Manager uses as the basis for
your new ColdFusion server instance.
Note: If you are running JRun 4, you can also create a server in the JRun Management Console
(JMC) and deploy the ColdFusion application using JRun deployment functionality.
To define a server instance:
1.
Ensure that you have installed ColdFusion MX 7 using the multiserver configuration.
2.
Open the ColdFusion MX Administrator for the cfusion server in a browser
(http://hostname:8300/CFIDE/administrator).
3.
Select Enterprise Manager > Instance Manager.
4.
Click Add New Instance.
5.
Specify the following in the Add New ColdFusion Server area:
■ Server name
■ (Optional) Directory that contains the server instance. The ColdFusion MX Administrator
fills in the default automatically (jrun_root/servers/servername).
■ (Optional) Create from EAR/WAR. If you use the J2EE Packaging feature to create a J2EE
archive file with your application’s files (including CFM, CFC, and CFR files) and data
sources, use this field to specify the EAR or WAR filename and create a server instance with
your application deployed automatically.
■ (Optional, Windows only) Specify whether to create a Windows service for the server
instance and whether to define the Windows service with an auto restart recovery option.
6.
Click Submit.
The ColdFusion MX Administrator creates a server instance with ColdFusion MX deployed in
it and starts the server instance. The ColdFusion MX application that it deploys is based on the
application archive file specified in the Create from EAR/WAR field or on the cfusion server
instance (if you don’t specify an EAR or WAR file).
Creating a JRun server instance and deploying the ColdFusion MX application can take a few
minutes.
7.
Click Return to Instance Manager.
You can also start and stop the server instance using the JMC, the JRun Launcher, or the
command line (
jrun_root/bin jrun -start|-stop servername).