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
Ensure that you have defined 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, 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 might host each messaging
engine need access to the message store for that messaging engine.
About this task
Use this procedure when you want to add a messaging engine
to an existing cluster bus member.Alternatively,
you can add one or messaging engines when you add a cluster as a member
of a bus. You can use messaging engine policy assistance, which guides
you through the creation and configuration of the messaging engines.
Procedure
- In the navigation pane, click .
- In the content pane, click the name of the cluster to which
you want to add a messaging engine.
The Bus member
detail pane is displayed.
- In the content pane, under Additional properties,
click Messaging engines.
A
list of messaging engines for the cluster is displayed.
- In the content pane, click Add messaging engine.
- Select the type of message store that you have already
defined.
- Enter details for the message store.
- 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.
- When the wizard is finished, save your changes to the master
configuration.
Results
A messaging engine is added to the cluster. You can now configure
the messaging engine if required.