WebSphere brand IBM WebSphere Premises Server, Version 6.1.x

Manually configuring the clustered system for multiple messaging engines

After you have run the high availability installer for WebSphere® Premises Server, you can use these instructions to add more messaging engines.

WebSphere Premises Server SIBus configuration overview

There are two SIBuses created with the WebSphere Premises Server installation, AMIT and ibmsensorevent.

The high availability cluster configuration is the default configuration created when a cluster of application servers in a cell is created. When the SIBus is created, there is only one active messaging engine on one of the cluster servers, and all service requests to cluster members are routed through this single messaging engine. Therefore, for a cluster of n servers, there is one local message put action for routing the service request on the server with the active messaging engine, and (n-1) remote message put actions for each of the servers with inactive messaging engines.

For workload management, the cluster configuration requires additional configuration from the default cluster installation. The purpose of this configuration is to remove the dependence on the messaging engine remote put calls by explicitly creating an additional messaging engine for each of the servers in the cluster and defining a CoreGroup policy to "assign" the messaging engine to an individual server in the cluster. With n active messaging engines in a cluster of n servers, each service request is processed locally on the server receiving the message rather than getting routed to an active messaging engine.

Adding multiple messaging engines

About this task

These steps are specifically for the ibmsensorevent SIBus. You will also need to perform these steps for the AMIT SIBus.

Procedure
  1. Open the WebSphere Application Server Network Deployment administrative console and navigate to Servers > Core groups > Core group settings > DefaultCoreGroup > Policies.
  2. Click New and select One of N policy for the policy type.
  3. Click Next.
  4. Define the new policy.
    1. For Name, enter SIBusClusterME001Policy.
    2. Select the checkbox for Failback.
    3. Select the checkbox for Preferred servers only.
    4. Click Apply.
  5. Under Additional Properties, click Match criteria.
  6. Click New and define the match criteria for the policy.
    1. For Name, enter type.
    2. For Value, enter WSAF_SIB.
    3. Click OK.
    In the next three steps, you repeat the actions in this step to define additional match criteria for the policy.
  7. Click New and define an additional match criteria for the policy.
    1. For Name, enter WSAF_SIB_BUS.
    2. For Value, enter ibmsensorevent.
    3. Click OK.
  8. Click New and define an additional match criteria for the policy.
    1. For Name, enter WSAF_SIB_MESSAGING_ENGINE.
    2. For Value, enter PremisesCluster.000-ibmsensorevent.
    3. Click OK.
  9. Click New and define an additional match criteria for the policy.
    1. For Name, enter IBM_hc.
    2. For Value, enter PremisesCluster.
    3. Click OK.
  10. Navigate back to the SIBusClusterME001Policy and click Preferred servers under Additional Properties.
  11. Select the server name of a cluster member from the Core group servers and click Add>>.
  12. Click OK.
  13. Repeat steps 4 through 12 to create new policies and assign each to a cluster member. Every cluster member except the central server needs a policy.
  14. Create messaging engines for each cluster member.

    When you ran the high availability installer, a cluster member named PremisesCluster.000-ibmsensorevent was created on the ibmsensorevent SIBus. This steps shows you how to create the messaging engine for that cluster member. Repeat this step as necessary to create (n-1) messaging engines for n cluster members.

    1. Navigate to Service integration > Buses > ibmsensorevent > Bus members > PremisesCluster.
    2. Click Add messaging engine and select File store.
      Note: You can use Data store instead of File store.
    3. Click Next.
    4. For Log directory path, enter ${LOG_ROOT}/sibus-se.
    5. For Permanent store directory path, enter ${LOG_ROOT}/sibus-se.
    6. Click Next.
    7. Click Finish.
  15. Synchronize all cluster members and server configurations by navigating to System administrator > Nodes and clicking Full Resynchronize.
  16. Restart the PremisesCluster cluster and the central server.
    1. Navigate to Server > Clusters.
    2. Select PremisesCluster and click Stop.
    3. Once it all cluster members are stopped, click Start.
    4. Navigate to Server > Application servers.
    5. Select the central server (such as PremisesNode, server1).
    6. Click Stop.
    7. Once the central server has stopped, click Start.
  17. Repeat all of the previous steps for the AMIT SIBus. To do this, replace every instance of "ibmsensorevent" with "AMIT" in the instructions, specifically in the console paths, SIBus name, and messaging engine names.

Library | Support | Terms of use

(c) Copyright IBM Corporation 2004, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.