Add a cluster as a member of a bus
We 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.
To add a cluster to a bus, the following resources must be defined:
- A service integration bus.
- A cluster. For a high availability configuration, the cluster should contain at least two nodes, each with a server on, that is, at least two physical machines.
- A location for the message store for the messaging engine. Each messaging engine uses a message store to preserve operating and recovery information.
- To use a file store, we need a file location.
- To use a data store, we need a suitable data source, such as a relational database, that is accessed through a JDBC data source.
Use the default JDBC data source and Derby JDBC Provider for its data store. If we do not want to use the default data source configuration, we can use a different data source or we can configure the data store to use a different JDBC provider.
To have any of the messaging engines in the cluster to fail over to another server, all servers that might host each messaging engine need access to the message store for that messaging engine.
When we add a server cluster as a member of a bus, consider the following points:
- If we use messaging engine policy assistance, one or more messaging engines are created and configured, according to the messaging engine policy type we select. We 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 we can customize them.
- If we 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, we 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 we are already familiar with it. Otherwise, use messaging engine policy assistance.
- If we are working in a mixed-version cell, a service integration bus running in this version of the product can only include WebSphere Application Server v6 bus members 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 using an inter-engine authentication alias. If we add a server cluster as a bus member at WAS v6, and it is the first bus member at this level, select or create an authentication alias during this task. This action sets the inter-engine authentication alias.
- If we subsequently delete a bus member and then re-create it, we 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.
Subtopics
- Add a cluster to a bus for high availability or scalability
- Add a cluster to a bus with a custom configuration
- Add a cluster to a bus without using messaging engine policy assistance
Related:
Service integration high availability and workload sharing configurations Bus member types and their effect on high availability and workload sharing How a message-driven bean connects in a cluster Policies for service integration Configuration for high availability Configuration for workload sharing with high availability Configuration for workload sharing or scalability Messaging engine policy assistance Interconnected buses Create a policy for messaging engines Modifying file store configuration Add a server as a new bus member Create the database, schema and user ID for a messaging engine Configure file store attributes for a messaging engine Modify the messaging engine policy for a cluster bus member Secure links between messaging engines addSIBusMember command Bus members [Collection]