WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Adding a cluster as a member of a bus

You can add a server cluster as a member of a service integration bus so that it can use the bus to communicate. When a cluster is added to the bus, all servers in the cluster are added to it, and one messaging engine is created. The members of a service integration bus are the application servers and clusters within which messaging engines for that bus can run.

Before you begin
To add a cluster to a bus, the following resources must be defined:
About this task
When you add a server cluster as a member of a bus, consider the following points:
  • A messaging engine with default properties is created for the cluster.
  • The messaging engine uses the default core group policy for messaging engines, Default SIBus Policy. After adding the bus member, you can create more messaging engines and can configure a new core group policy to customize the way that the messaging engines are managed. It is advisable to create a new, separate, core group policy for each new messaging engine, including the first one. It is not advisable to alter the default SIBus core group policy.
  • When you add a server cluster as a member of a bus, you do not need to add the servers in that cluster separately.
  • If you subsequently delete a bus member and then re-create it, you must manually delete the old data source to ensure that the messaging engines will restart after the bus member has been created.

To add a server cluster as a member of a bus, use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, click Service integration > Buses. A list of buses is displayed in the content pane.
  2. In the content pane, select the bus to which you want to add the cluster.
  3. In the content pane, under Topology, click Bus members. A list of members in the bus is displayed. Click Add.
  4. Select the Cluster option and choose the cluster you want to add to your bus from the drop down list.
  5. Select File store or Data store as your message store. For more details, see Considerations when choosing between a file store and a data store
  6. For a file store, you need to specify the Log directory path, and Permanent store directory path when Same settings for permanent and temporary stores option is selected. The default directory path is ${USER_INSTALL_ROOT}/filestores/com.ibm.ws.sib/me_name.me_build/. For more information, see the table in Configuring a JDBC provider and data source.
  7. If you choose a data store, you need to have a data source configured. See File store configuration attributes for more details. In the Data source JNDI name field, type the JNDI name of the data source that provides access to the database that holds the data store.
  8. Click Next.
  9. Click Finish to confirm the creation of the bus member.
  10. Save your changes to the master configuration.
Results
The cluster is added to the bus and a default messaging engine is created for that cluster. The default behavior provides a high availability configuration without any workload sharing.
What to do next
You can now change the configuration of the messaging engine and associated data store if required.

If you require high availability, you might want to do further configuration, for example to specify preferred servers for the messaging engine, or enable the messaging engine to fail back. If you require scalability or workload sharing, you need to add as many messaging engines as you require to the cluster. To customize the messaging engine behavior, you must create and configure a new core group policy for the messaging engines and use match criteria to associate the messaging engines with the core group policy. It is advisable to create a new, separate, core group policy for each new messaging engine, including the first one. It is not advisable to alter the default SIBus core group policy. For more information, see the related tasks.

Related concepts
Bus member types and their effect on high availability and workload sharing configuration
Related tasks
Modifying file store configuration

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tjj0010_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)