Add a messaging engine to a cluster
We 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, we do this to provide workload sharing or scalability in the cluster.
Ensure that we 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, 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.
Use this procedure when we want to add a messaging engine to an existing cluster bus member. Alternatively, we can add one or messaging engines when we add a cluster as a member of a bus. Use messaging engine policy assistance, which guides you through the creation and configuration of the messaging engines.
Add a messaging engine to a cluster
- In the navigation pane, click...
Service integration -> Buses -> bus_name -> [Topology] Bus members > cluster_name > Additional properties > 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 we have already defined.
- Enter details for the message store.
- If we 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 we use a unique path for each messaging engine.
- If we 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 the changes to the master configuration.
A messaging engine is added to the cluster. We can now configure the messaging engine if required.
Related:
Bus member types and their effect on high availability and workload sharing How a message-driven bean connects in a cluster Messaging engines Bus members List the messaging engines for a cluster bus member Configure messaging engine properties Create the database, schema and user ID for a messaging engine Configure file store attributes for a messaging engine Configure a messaging engine to use a data store Configure a JDBC data source for a messaging engine Correcting the messaging engine policy Add a cluster as a member of a bus Configure high availability and workload sharing of service integration Add a cluster to a bus without using messaging engine policy assistance Modify the messaging engine policy for a cluster bus member createSIBEngine command createMissingSIBEnginePolicy command Messaging engine troubleshooting tips