You can add a messaging engine to a cluster bus member
to provide additional asynchronous messaging services to the servers
that are members of the cluster. Typically, you do this to provide
workload sharing or scalability in the cluster.
Before you begin
To add a messaging engine to a cluster, a location for the
message store for the messaging engine must be defined. Each messaging
engine uses a message store to preserve operating and recovery information.
- To use a file store, you need a file location.
- To use a data store, you need a suitable data source, such as
a relational database, that is accessed through a JDBC data source.
You can use the default JDBC data source and Derby JDBC Provider for
its data store. If you do not want to use the default data source
configuration, you can use a different data source or you can configure
the data store to use a different JDBC provider.
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 cluster as a member of a bus, one messaging
engine is created automatically. Cluster bus members can support additional
messaging engines.
To add a messaging engine to a cluster, use the
administrative console to complete the following steps:
Procedure
- In the navigation pane, click .
- In the content pane, click the name of the bus.
- In the content pane, under Topology, click Bus
members. A list of members in the bus
is displayed.
- In the content pane, select the cluster to which you want
to add a messaging engine. A list of messaging engines
for the cluster is displayed.
- Click Add messaging engine.
- Follow the steps in the wizard to enter the details of
the message store for the messaging engine.
If
you use a file store, specify the directory paths for the log files,
the permanent file store, and the temporary file store. Do not use
the default path, and ensure that you use a unique path for each messaging
engine.
If you use a data
store, specify the JNDI name of the data source that provides access
to the database that holds the data store. You can use the same database
for more than one messaging engine, as long as each one uses a different
schema name.
- Save your changes to the master configuration.
Results
A messaging engine is added to the cluster.