Set up a highly available message bus

If you configured the portal farm to use a single content subscriber, you may want to create a highly available message bus to ensure 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 and will automatically reassign 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 below.

To set up a highly available message bus: These steps assume that you currently have a single messaging server set up on farm. These steps are either performed on each farm instance if you have a unique installation or on the master farm instance if you have a shared configuration.

1. To modify the Web Content Manager message driven bean (MDB) to include additional service integration (SIB) endpoints, one for each cluster member in the subscriber cluster:

   1. Open the Deployment Manager administrative console.

   2. Navigate to Resources -> JMS -> Activation specifications.

   3. Select IWKItemChangeMonitorActivation 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 changes.

   5. Select IWKSyndicationMonitorActivation and under Provider endpoints add the additional server:port:BootstrapBasicMessaging for each cluster member in the subscriber cluster; separate them by commas.

   6. Click OK to save changes.

   7. Click Save to save changes.

   8. Log out of the Deployment Manager administrative console.

2. To modify the Web Content Manager JMS Connection Factory definition to include additional SIB endpoints, one for each cluster member in the subscriber cluster:

   1. Open the Deployment Manager administrative console.

   2. Navigate to Resources -> JMS -> Topic connection factories.

   3. Select IWKMessagingTopicConnectionFactory 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 changes.

   5. Click Save to save changes.

   6. Log out of the Deployment Manager administrative console.

Parent

Set up a portal farm

Related tasks

Set up a cluster on Windows

 

+

Search Tips   |   Advanced Search