About this task
Although you must configure a data source for all active
messaging engines, the configuration process for a messaging engine
running in a cluster is the same as for any single messaging engine.
For more information, refer to
Setting up the data store for a messaging engine and
Data source minimum required settings, by vendor.
The data store configuration
depends on the purpose of your cluster:
- For a workload managed (WLM) cluster, every messaging engine in
the cluster must have its own unique data store schema.
- For a failover (HA) cluster, you must have only one data store
schema that will be used by the active messaging engine wherever it
starts.
For more information about clusters, refer to Service integration high availability and workload sharing configurations.
When a messaging engine is created as a member of a cluster,
you must explicitly configure both the data store and the JDBC data
source that the messaging engine uses to interact with the data store.
- If each messaging engine has its own JDBC data source, you can
create the data sources at node scope.
- If several messaging engines share the same JDBC data source,
you must create the data source at cluster scope, not node scope.
You must also ensure that you install the JDBC driver
jars at every node. For more information, refer to Creating
and configuring a data source using the administrative console.