Set up a highly available message bus

If we configured the portal farm to use a single content subscriber, we might want to create a highly available message bus. The message bus ensures that content is always updated on the server instances, even if one subscriber server becomes unavailable. To create a highly available message bus, create a cluster of subscriber servers and then add them to the bus. If the bus is set up on the initial server from which the cluster is based, where you ran the create-wcm-jms-resource task, then the resulting cluster will become a member of the bus, as will all cluster members.

IBM WebSphere Application Server assigns one member of the cluster at a time to own the message queue. It automatically reassigns the queue to another cluster member if the original becomes unavailable. Setting up a IBM Web Content Manager subscriber cluster is the same as creating a IBM WebSphere Portal cluster.

See the appropriate Setting up a cluster topic in the Related task section.

Set up a highly available message bus

These steps assume that you currently have a single messaging server set up on the farm. These steps are either completed on each farm instance if you have a unique installation or on the master farm instance if you have a shared configuration.

1. Modify the WCM message driven bean (MDB) to include additional service integration (SIB) endpoints, one for each cluster member in the subscriber cluster:

   1. Log on to the dmgr console and go to...
      Resources | JMS | Activation specifications | IWKItemChangeMonitorActivation

      ...and under Provider endpoints add the additional...

      server:port:BootstrapBasicMessaging

      ...for each cluster member in the subscriber cluster; separate them by commas.

   2. Click OK to save the changes.

   3. Select...
      IWKSyndicationMonitorActivation

      ...and under Provider endpoints add the additional...

      server:port:BootstrapBasicMessaging

      ...for each cluster member in the subscriber cluster; separate them by commas.

   4. Click OK to save the changes.

   5. Click Save to save the changes.

   6. Log out of the dmgr console.

2. Modify the WCM JMS Connection Factory definition to include additional SIB endpoints, one for each cluster member in the subscriber cluster:

   1. Log on to the dmgr console and go to...
      Resources | JMS | Topic connection factories | IWKMessagingTopicConnectionFactory

      Under Provider endpoints add the additional...

      server:port:BootstrapBasicMessaging

      ...for each cluster member in the subscriber cluster; separate them by commas.

   2. Click OK to save the changes.

   3. Click Save to save the changes.

   4. Log out of the dmgr console.

Parent: Set up a portal farm
Related:
Set up a cluster