Page History

Apache Geronimo v2.1 offers different alternatives for clustering such as Jetty or Tomcat native, WADI and Terracotta.

• Farming

A configuration can be deployed to a cluster of Geronimo servers via a single logical deployment step. Once deployed to a cluster, this configuration can then be transparently started, stopped or undeployed across all the cluster members.
These two features greatly streamline the maintenance of applications running on a cluster as Geronimo takes care of cluster-wide application distribution and management for you.

Configuration of Cluster Members

Cluster members are configured on a Geronimo server, which may but is not required to be a member of the cluster. This is achieved by adding a org.apache.geronimo.farm.config.BasicNodeInfo GBean for each cluster member to the farming configuration. This GBean looks like:

<gbean name="NodeInfo" class="org.apache.geronimo.farm.config.BasicNodeInfo">
    <attribute name="name">${PlanClusterNodeName}</attribute>
    <xml-attribute name="extendedJMXConnectorInfo">
        <ns:javabean xmlns:ns="http://geronimo.apache.org/xml/ns/deployment/javabean-1.0" class="org.apache.geronimo.farm.config.BasicExtendedJMXConnectorInfo">
            <ns:property name="username">system</ns:property>
            <ns:property name="password">manager</ns:property>
            <ns:property name="protocol">rmi</ns:property>
            <ns:property name="host">localhost</ns:property>
            <ns:property name="port">1099</ns:property>
            <ns:property name="urlPath">JMXConnector</ns:property>
            <ns:property name="local">true</ns:property>
        </ns:javabean>
    </xml-attribute>
</gbean>

It defines network address (host, port, urlPath) and credentials (username and password) to be used to connect to the cluster member via JMX. Such declarations are to be included within the config.xml file, farming module of your Geronimo server.
By default, the farming configuration defines the local server as a cluster member. To exclude it, you can prevent the GBean NodeInfo to start.

Farm Deployment

To deploy a configuration to configured members, you simply deploy it to the MasterConfigurationStore repository defined by the farming configuration. This configuration being stopped out-of-the-box, you may have to start it the first time via this GShell command:

deploy/start org.apache.geronimo.configs/farming//car

farming adds two new repositories to the server: MasterConfigurationStore and ClusterStore. MasterConfigurationStore is the repository you should use most of the time if not always. ClusterStore is a repository you may have to use in specific and infrequent scenarios.
To deploy to MasterConfigurationStore, you pass the --targets flag to the distribute or deploy commands like this:

deploy/distribute  --targets org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/farming/2.2-SNAPSHOT/car,j2eeType=ConfigurationStore,name=MasterConfigurationStore <your module>

Following this deployment

• MasterConfigurationStore contains a kind of virtual configuration, which has the same name than your deployment and defines GBeans controlling the remote start and stop of the actual configuration cluster-wide; and
• ClusterStore contains the actual configuration under an altered configuration name, a '_G_SLAVE' is appended to the configuration name.

Cluster-wide Management of Configurations

...

• WADI Clustering Support
• Tomcat Native Clustering