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 at least 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

New feature:

In this release, the procedure to create or modify a cluster bus member is simplified. In the administrative console, you can use a wizard to create a cluster bus member, so that there is guidance through the steps, the correct components are created, and some components are created automatically.

When you create or modify a cluster bus member, you can use messaging engine policy assistance, which provides guidance about creating and configuring messaging engines in a cluster to provide the behavior you require. You can select from one of three predefined messaging engine policy types, which support cluster configurations that require high availability, scalability, or both. For more advanced requirements, you can use messaging engine policy assistance to create a custom configuration, and some associated components are created automatically.

newfeat
When you add a server cluster as a member of a bus, consider the following points:
  • If you use messaging engine policy assistance, one or more messaging engines are created and configured, according to the messaging engine policy type you select. You can choose one of the predefined messaging engine policy types, which are designed to support frequently-used configurations, or choose a custom messaging engine policy type, where some configuration settings are created automatically but you can customize them.
  • If you do not use messaging engine policy assistance, one messaging engine is created. This messaging engine has default properties and 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. Use this procedure if you are already familiar with it. Otherwise, use messaging engine policy assistance.
  • If you are working in a mixed-version cell, a service integration bus running in this version of the product can only include WebSphere® Application Server Version 6 bus members that are running in the following versions of the product:
    • 6.0.2 (Fix Pack 23 or later)
    • 6.1.0 (Fix Pack 13 or later)
  • If security is enabled, and the bus has mixed-version bus members, the bus members establish trust by using an inter-engine authentication alias. If you add a server cluster as a bus member at WebSphere Application Server Version 6, and it is the first bus member at this level, you must select or create an authentication alias during this task. This action sets the inter-engine authentication alias.
  • 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. Refer to Data store life cycle and Removing a messaging engine from a bus for details.

What to do next

  • Adding a cluster to a bus for high availability or scalability

    You can add a cluster as a member of a bus and use messaging engine policy assistance and a predefined messaging engine policy that provides high availability, scalability, or scalability with high availability. Messaging engine policy assistance helps you to create and configure the messaging engines in a cluster to provide the required messaging engine behavior.

  • Adding a cluster to a bus with a custom configuration

    You can add a cluster as a member of a bus and use messaging engine policy assistance and the custom messaging engine policy. In this situation, messaging engine policy assistance helps you to create and configure messaging engines in a cluster that is a member of a bus when the predefined messaging engine policy types do not meet your needs. You can configure the messaging engine behavior, and the appropriate messaging engine policies are created automatically.

  • Adding a cluster to a bus without using messaging engine policy assistance

    You can add a cluster as a member of a service integration bus without using messaging engine policy assistance. One messaging engine with default properties is created for the cluster. After you add the cluster, you can create more messaging engines and you can create and configure new core group policies to customize the way that the messaging engines are managed.

Task topic    

Terms of Use | Feedback

Last updated: Oct 22, 2010 12:21:29 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-zos&topic=tjj0010_
File name: tjj0010_.html