Enterprise Manager section

The Enterprise Manager section of the Administrator lets you create Tomcat server instances with ColdFusion already deployed, register remote Tomcat server instances, and create clusters of Tomcat server instances.

    Instance Manager page

    The Instance Manager page lets you view the local and remote Tomcat servers that can be accessed by a cfusion server running.

    From this page you can access pages that define new, local, Tomcat servers and register existing Tomcat servers running on remote computers, as follows:

    Add New Instance
    Create a Tomcat server and automatically deploy a copy of the current ColdFusion MX application into that server. Alternatively, you can deploy ColdFusion MX applications packaged using the J2EE Archives page.

    Register Remote Instance
    Define an existing remote Tomcat server to the Instance Manager for adding these servers to a cluster. It is not mandatory to run the remote Tomcat server instance when you define it to the Instance Manager. However, it must be running before you can add it to a cluster.

    Edit ColdFusion Server: Modify built-in web server settings for a server instance.

    Available servers

    Area

    Description

    Actions

    Lets you start, stop, restart, and delete a Tomcat server.

    You cannot start or stop a remote instance with the Enterprise Manager, therefore, the start and stop icons are disabled for remote servers. Additionally, you can click the Edit icon to display the Edit ColdFusion Server page or the ColdFusion

    Name

    Specifies the Tomcat server name. If the server is started, you can click this name to open a browser window to the Tomcat server's web root.

    Server Directory

    Specifies the server directory.

    HTTP Port

    Specifies the port for the built-in web server.

    Remote Port

    JNDI port for the server instance.

    Host

    Specifies the host name or IP address for the server instance.

    Cluster

    Cluster Specifies the name of the cluster that contains the server.

    • By default, the Instance Manager deploys a copy of the current cfusion application (data sources, settings, administrator password, and so on).

    • You can optionally use the Create from EAR/WAR option to create a server with a previously archived application.

    • To deploy an empty application, create one with the J2EE archives page and use the Create from EAR/WAR option.

    • You cannot stop the cfusion and admin servers.

    Cluster Manager page

    The Cluster Manager page in ColdFusion Administrator lets you create and manage clusters of Tomcat servers, each containing the same ColdFusion application.

    1. Add a cluster by typing a name in the Cluster Name box, and clicking Add. This creates a cluster and adds it to the Configured Clusters table.

    2. Add servers to the cluster by clicking the Edit icon next to the cluster name in the Configured Clusters table. This displays the Edit Cluster Page.

    Edit Cluster Page

    The Edit Cluster page in ColdFusion Administrator lets you define the server instances for a cluster and to customize cluster settings.

    Managing clusters

    Manage clusters using the ColdFusion Administrator.

    1. In the ColdFusion Administrator, click Enterprise Manager > Cluster Manager.

    2. Enter a cluster name and then click Add.

    3. Click the cluster name and move the servers to the cluster based on the requirement.

    4. (If required) Edit the multicast port.

      Multicast port is used to group the cluster members together. Default value of multicast port is 45564. After you create a cluster, the port is added in the cf_install_dir\cfusion\config\cluster.xml file.

      For more information on multicast port, see http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-membership.html.

    5. Specify if you need sticky session.

      Sticky session ensures that after a session is established on an instance, all future requests from the client are mapped to that instance.

    6. Click Submit.

    Adding a remote instance to a cluster

    To add a remote instance to a cluster, add the cluster block to the remote instance’s server.xml. Then, register the remote instance and add the instance to the cluster. For more information on configuring clusters on Tomcat, see http://tomcat.apache.org/tomcat-5.5-doc/cluster-howto.html.

    1. Register the remote instance to the local machine.

    2. Create a cluster in the local machine.

    3. Open the cf_install_dir\instance-name\runtime\conf\server.xml file of the remote instance.

    4. Add the following block between the entries </host> and </engine>:

       
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"         channelSendOptions="8"> 
    <Manager notifyListenersOnReplication="true" expireSessionsOnShutdown="false" className="org.apache.catalina.ha.session.DeltaManager"> 
    </Manager> 
    <Channel className="org.apache.catalina.tribes.group.GroupChannel"> 
        <Membership port="45565" dropTime="3000" address="228.0.0.4"     className="org.apache.catalina.tribes.membership.McastService" frequency="500"> 
        </Membership> 
        <Receiver port="4003" autoBind="100" address="auto" selectorTimeout="5000"     maxThreads="6" className="org.apache.catalina.tribes.transport.nio.NioReceiver"> 
        </Receiver> 
        <Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter"> 
            <Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"> 
            </Transport> 
        </Sender> 
        <Interceptor className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"> 
        </Interceptor> 
        <Interceptor     className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor"> 
        </Interceptor> 
    </Channel> 
    <Valve className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""> 
    </Valve> 
    <Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve"> 
    </Valve> 
 
    <ClusterListener     className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener"> 
    </ClusterListener> 
    <ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener"> 
    </ClusterListener> 
 
</Cluster>

    5. In the entry, update the membership port with the multicast port of the cluster.

    6. Using the ColdFusion Administrator of the local host, add the local instance and the remote instance to the cluster.
      Note: If you enable sticky session, the JVM route of the remote instance and local instance must not be the same.

    7. Restart all the instances.