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 service integration, "Default SIBus Policy". After adding the bus member, you can create more messaging engines and can configure one or more new core group policies 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 policy for service integration.
  • 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.
  4. Click Add.
  5. Click the Cluster button.
  6. Use the drop-down list to select the name of the cluster that you want to add as a bus member.
  7. 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 one or more new core group policies 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 service integration policy, "Default SIBus Policy". For more information about configuring high availability and workload sharing, see the related tasks.




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=tjj0010_
File name: tjj0010_.html