Installation Guide › Installing an AIX Implementation › Run the CA RCM Installer › Complete CA RCM Server Installation on AIX/WebSphere › Create the Service Integration Bus and Queues in CA RCM Cluster

Create the Service Integration Bus and Queues in CA RCM Cluster

Create the bus and data queues to complete creation of the cluster. Then you can install the CA RCM server on the cluster.

To create the Service Integration Bus and Queues in CA RCM Cluster

1. From the WebSphere administration console, click Service Integration, Buses.
2. Create a bus named eurekifyBus.
3. Under Security, select Enable bus security.
4. Under Permitted transports, choose Allow the use of all defined transport channel chains.
5. Add the CA RCM cluster as a bus member with the following settings:
   • Message store: data store
   • Datasource JDNI name: jdbc/eurekifyBusQueueDS
   • Scheme name: dbo
   • Authentication alias: eurekifyQueueDBCred
   • Create tables: selected
6. Create the following Queue type destinations for this bus. Verify that the CA RCM cluster is listed as a bus member when you create these queues.
   • eurekifyFixAlertsExecutorQBusQueue
   • eurekifyTxLogQBusQueue
   • eurekifyWfAsyncQBusQueue
   • eurekifyWftmsQBusQueue
   • eurekifyrcmTestQBusQueue
7. Create a Topic Space destination named eurekifyCacheEventsTBusTopic.
8. Save changes to the master configuration.
9. Configure the following properties for each of the destinations you created:
   • Exception destination: System
   • Maximum failed deliveries: 150
10. Create a Queue Connection Factory for the CA RCM cluster (Resources, JMS, Queue connection factories) with the following settings:
    • JMS Resource Provider: Default messaging provider
    • Name and JNDI Name: eurekifyQueueConnectionFactory
    • Bus Name: eurekifyBus
11. Under Connection Pool Properties, set Maximum connections to 100.
12. Create a Topic Connection Factory for the CA RCM cluster (Resource, JMS, Topic connection factories) with the following settings:
    • JMS Resource Provider: Default messaging provider
    • Name and JNDI name: eurekifyTopicConnectionFactory
    • Bus Name: eurekifyBus
13. Under Connection Pool Properties, set Maximum connections to 100.
14. Create queues (Resource, JMS, Queues) for the CA RCM cluster with the following settings:
    • For the fixAlertsExecutor queue:

      Name: fixAlertsExecutorQ

      JNDI Name: queue/fixAlertsExecutorQ

      Queue Name: eurekifyFixAlertsExecutorBusQueue

    • For the txLog queue:

      Name:txLogQ

      JNDI Name: queue/txLogQ

      Queue Name: eurekifytxLogQBusQueue

    • For the wfAsync queue:

      Name: wfAsyncQ

      JNDI Name: queue/wfAsyncQ

      Queue Name: eurekifywfAsyncQBusQueue

    • For the wftms queue:

      Name: wftmsQ

      JNDI Name: queue/wftmsQ

      Queue Name: eurekifywftmsQBusQueue

    • For the eurekifyTest queue:

      Name: eurekifyTestQ

      JNDI Name: queue/eurekifyTestQ

      Queue Name: eurekifyrcmTestQBusQueue

    Apply the following settings to all these queues:

    • JMS Resource Provider: Default messaging provider
    • Bus Name:
15. Create a Topic (Resources, JMS, Topics) for the CA RCM cluster using the following settings:
    • JMS Resource Provider: Default messaging provider
    • Name: cacheEventsT
    • JNDI name: topic/cacheEventsT
    • Bus Name: eurekifyBus
    • Topic Space: eurekifyCacheEventsTBusTopic
16. Under Connection Pool Properties, set Maximum connections to 100.