LibraryToggle FramesPrintFeedback

Complete the following steps to set up JBI endpoint clustering:

  1. Install the jbi-cluster feature included in Fuse ESB Enterprise. See Installing the clustering feature.

  2. Optionally, configure the clustering engine with a JMS broker other than the Apache ActiveMQ. See Changing the JMS broker.

  3. Optionally, change the default clustering engine configuration to specify different cluster and destination names. See Changing the default configuration.

  4. Add endpoints and register the endpoint definition in the Spring configuration. See Using clustering in an application.

See the following sections for additional information:

Fuse ESB Enterprise has a pre-installed clustering engine that is configured to use the included Apache ActiveMQ. The default configuration for the Fuse ESB Enterprise cluster engine is defined in the jbi-cluster.xml file in the org.apache.servicemix.jbi.cluster.config bundle. This bundle is located in the installation directory in \system\org\apache\servicemix\jbi\cluster.

The default cluster engine configuration, shown in Example 5.1, is designed to meet most basic requirements.

Example 5.1. Default cluster engine configuration

<bean id="clusterEngine" class="org.apache.servicemix.jbi.cluster.engine.ClusterEngine">
  <property name="pool">
    <bean class="org.apache.servicemix.jbi.cluster.requestor.ActiveMQJmsRequestorPool">
     <property name="connectionFactory" ref="connectionFactory" />
     <property name="destinationName" value="${destinationName}" />
    </bean>
  </property>
  <property name="name" value="${clusterName}" />
</bean>
<osgi:list id="clusterRegistrations"
      interface="org.apache.servicemix.jbi.cluster.engine.ClusterRegistration" 
      cardinality="0..N">
  <osgi:listener ref="clusterEngine" bind-method="register" unbind-method="unregister" />
</osgi:list>        
<osgi:reference id="connectionFactory" interface="javax.jms.ConnectionFactory" />       
<osgi:service ref="clusterEngine">
  <osgi:interfaces>
    <value>org.apache.servicemix.nmr.api.Endpoint</value>
    <value>org.apache.servicemix.nmr.api.event.Listener</value>
    <value>org.apache.servicemix.nmr.api.event.EndpointListener</value>
    <value>org.apache.servicemix.nmr.api.event.ExchangeListener</value>
  </osgi:interfaces>
  <osgi:service-properties>
    <entry key="NAME" value="${clusterName}" />
  </osgi:service-properties>
</osgi:service>        
<osgix:cm-properties id="clusterProps" 
        persistent-id="org.apache.servicemix.jbi.cluster.config">
  <prop key="clusterName">${servicemix.name}</prop>
  <prop key="destinationName">org.apache.servicemix.jbi.cluster</prop>
</osgix:cm-properties>       
<ctx:property-placeholder properties-ref="clusterProps" />
</beans>

Fuse ESB Enterprise has a preconfigured Apache ActiveMQ instance that automatically starts when the container is started. This means you do not have to start a broker instance for the clustering engine to work.

To create a network of JBI containers, you must establish network connections between each of the containers in the network, and then establish a network connection between the active containers. You can configure these network connections as either static or multicast connections.

When a network connection is established, each container discovers the other containers' remote components and can route to them.

Comments powered by Disqus