Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer message stores > Administer data stores > Configure a messaging engine to use a data store
Configure a data source for a messaging engine running in a cluster
Methods that you can use to configure a data source for a messaging engine depend on the cluster in which you intend to run the messaging engine. Although 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. See Create the database, schema and user ID 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, have only one data store schema that will be used by the active messaging engine wherever it starts.
For more information about clusters, see Service integration high availability and workload sharing configurations.
When a messaging engine is created as a member of a cluster, 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, create the data source at cluster scope, not node scope.
You must also ensure that you install the JDBC driver jars at every node. See Configure a data source .
Service integration high availability and workload sharing configurations
Create the database, schema and user ID for a messaging engine
Configure a JDBC data source for a messaging engine
Vendor-specific data sources