16.2. Configure server instance as a worker node

Task: Configure a JBoss Enterprise Application Platform Worker Node

Follow this task to correctly configure a JBoss Enterprise Application Platform instance as a SJWS worker node.
  1. Create a server profile for each worker node

    Make a copy of the server profile that you wish to configure as a worker node. (This procedure uses the default server profile.)
    [user@workstation jboss-ep-5.2]$ cd jboss-as/server
    [user@workstation server]$ cp -r default/ default-01
    [user@workstation server]$ cp -r default/ default-02
  2. Give each instance a unique name

    Edit the following line in the deploy/jbossweb.sar/server.xml file of each new worker instance:
    <Engine name="jboss.web" defaultHost="localhost">
    Add a unique jvmRoute value, as shown. This value is the identifier for this node in the cluster.
    For the default-01 server profile:
    <Engine name="jboss.web" defaultHost="localhost" jvmRoute="worker01">
    For the default-02 server profile:
    <Engine name="jboss.web" defaultHost="localhost" jvmRoute="worker02">
  3. Enable session handling

    Uncomment the following line in the deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml file of each worker node:
    <property name="useJK">false</property>
    This property controls whether special session handling is used to coordinate with mod_jk and other connector variants. Set this property to true in both worker nodes:
    <property name="useJK">true</property>
  4. Start your worker nodes

    Start each worker node in a separate command line interface. Ensure that each node is bound to a different IP address with the -b switch.
    [user@workstation jboss-eap-5.2]$ ./jboss-as/bin/run.sh -b 127.0.0.1 -c default-01
    [user@workstation jboss-eap-5.2]$ ./jboss-as/bin/run.sh -b 127.0.0.100 -c default-02