Return to Jive Software

Currently Being Moderated

Setting Up Unicast Clustering

VERSION 2  Click to view document history

Created on: Jun 18, 2008 2:20 PM by seth - Last Modified:  Nov 2, 2009 2:27 PM by Karl Cyr

Extract the file tangosol_coherence-override.xml from clearspace-x.x.x.jar or jive-sbs-<edition>-x.x.x.jar

 

For this example, 10.0.0.1 is node 1, and has a machine-id of "A", 10.0.0.2 is node 2, and has a machine-id of "B". The port selection is arbitrary.

 

Insert the following as a child of the <cluster-config> tag for server A:

 

<unicast-listener>
     <machine-id>A</machine-id>
     <address>10.0.0.1</address>
     <port>11111</port>

     <!-- This set of well-known-addresses creates a cluster with two nodes -->
     <well-known-addresses>

          <!-- Each server in the cluster must have a unique <socket-address> id -->
          <socket-address id="A">
               <address>10.0.0.1</address>
               <port>11111</port>
          </socket-address>

          <socket-address id="B">
               <address>10.0.0.2</address>
               <port>11111</port>
          </socket-address>

     </well-known-addresses>
</unicast-listener>

 

 

And this goes in for server B:

 

<unicast-listener>
     <machine-id>B</machine-id>
     <address>10.0.0.2</address>
     <port>11111</port>

     <!-- This set of well-known-addresses creates a cluster with two nodes -->
     <well-known-addresses>

          <!-- Each server in the cluster must have a unique <socket-address> id -->
          <socket-address id="A">
               <address>10.0.0.1</address>
               <port>11111</port>
          </socket-address>

          <socket-address id="B">
               <address>10.0.0.2</address>
               <port>11111</port>
          </socket-address>

     </well-known-addresses>
</unicast-listener>
169 Views Tags: settings, clustering, coherence, unicast
Average User Rating
(0 ratings)
My Rating:

Bookmarked By (0)

More Like This

  • Retrieving data ...

More by seth