About multiple server instances



The ColdFusion Administrator lets you create server instances and clusters. Additionally, you can connect to remote JRun servers and add them to clusters.

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 Java Virtual Machine (JVM), problems that one application encounter have no effect on other applications.

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

The multiserver configuration is a specialized J2EE configuration that installs JRun and deploys ColdFusion as an expanded Enterprise Application Archive (EAR) in the cfusion JRun server. The cfusion server is the only server that can create servers and clusters. The JRun instance creation and clustering options in the ColdFusion Administrator are not available in the server configuration, nor are they available in the J2EE configuration, even if you deploy ColdFusion on JRun.

Note: You can also manually deploy ColdFusion on multiple server instances, using the server creation and deployment facilities of your J2EE application server. For more information, see the ColdFusion documentation.

    Expanded archive considerations

    ColdFusion must run from an expanded directory structure. The Instance Manager expands the EAR or WAR file automatically and then deploys the expanded directory structure into the new server instance.

    For more information on deploying ColdFusion in the J2EE configuration, see Installing ColdFusion.

    File location considerations

    ColdFusion lets you store CFM pages either under the external web server root or under the ColdFusion web application root. The discussions here assume that you store your CFM pages under the ColdFusion web application root and specify a context root for your application. However, in ColdFusion MX 6.1 documentation, the assumption that you stored CFM pages under the web server root.

    If you use the web server connector to access pages under the ColdFusion web application root and your ColdFusion web application has an empty context root (this is the default), the connector does not automatically serve static content, such as HTML pages and image files. If so, define web server mappings so that it can serve files from the ColdFusion web application root.

    For more information on serving CFM pages from the web server root, see Web Server Management