Installation Guides › WebSphere Version › Installation on a WebSphere Cluster › How to Install CA Identity Manager on a WebSphere Cluster › Create Message Stores

Create Message Stores

The Service Integration Bus includes a messaging engine for each cluster member. It manages the communications for the bus. Each messaging engine has a message store, for its exclusive use, where it records messages, subscription information, and transaction states.

Important! Configure a message store for each cluster member with one database per cluster member. The message store can be any database that WebSphere can access remotely, but it must be a non-XA provider. You can use the non-XA provider distributed with CA Identity Manager. If you use a different non-XA provider, see the WebSphere documentation for configuration details. A new schema must be created for each database and the database must be empty.

To create message stores

1. For this task you will need the following information:
   • The database name
   • The schema name
   • The username and password for the database runtime user
   • The username and password for the user who will execute the script with the DDL statements that create the schema
2. Use IBM's sibDDLGenerator command to generate the DDL statements needed to create the database resources used by the messaging engine.

   For instructions on using this utility, see IBM's documentation for the sibDDLGenerator.

3. After you create the DDL statements, you run a SQL script to import the schema into the database.
4. To enable the messaging engine to use the database, you configure a non-XA JDBC provider for the database type at the cluster scope level.
5. Configure a data source for the cluster in the WebSphere Console.

   Note the JNDI name when you create the data source.

6. In the Administrative Console for the Deployment Manager, go to System Administration, Nodes.
7. Verify that the nodes show a Synchronized status.
8. Test the connection to the data source, the node where you created the data source.
9. Repeat this procedure for each cluster member.

Note: After you create the message store, create core group policies which determine the distribution of messaging engines among servers in the cluster.