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:
- 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.
If you want any of the messaging engines in the cluster to fail over
to another server, all servers that could host each messaging engine need
access to the message store for that messaging engine.
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
- In the navigation pane, click . A list of buses is displayed in the content pane.
- In the content pane, select the bus to which you want to add the
cluster.
- In the content pane, under Topology, click Bus
members. A list of members in the bus is displayed. Click Add.
- Select the Cluster option and
choose the cluster you want to add to your bus from the drop down list.
- 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
- 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.
- 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.
- Click Next.
- Click Finish to confirm the creation
of the bus member.
- 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.