Use this task to configure a data source
for a messaging engine that you intend
to run in a cluster.
Why and when to perform 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
Vendor-specific data sources minimum required settings.
The data store configuration depends
on the purpose of your cluster:
- For workload sharing, every messaging engine must
have its own data store.
- For failover, you must have one data store for
all of the messaging engines in the
failover cluster. When a messaging engine runs
in a failover cluster, its data store must
be accessible from every server that can potentially run the messaging engine that
owns the data store.
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.