Creating resources for manually installed event emitter services

When you manually install event emitter services, you must first create resources. If you do not use the configuration wizard to install the emitter services, or if you deploy more than one instance of the emitter services for performance reasons, you must manually create all required resources for the event emitter services. See the related links. You use the administrative console to create the required resources.

Before you begin

Before you begin this task, you must create the IBM® Business Monitor service integration bus (SIB). For instructions, see the related reference.

About this task

This topic provides instructions for creating the following required resources:

JMS destination queue
JMS error destination queue
Error queue connection factory
Queue connection factory
JMS queue
JMS error queue
Activation specification
Event emitter factory for the REST event emitter service
Event emitter factory for the JMS event emitter service

Note: If you are creating these resources for a JMS emitter for the first time on a server (if the event services were not previously deployed manually on the server or by the configuration wizard), you can choose to use all the default names to simplify installation of the emitter services. In the following steps, the default names are indicated. You can reuse already-defined event emitter factories or create new event emitter factories. Create separate event emitter factories for REST and for JMS.

Use the administrative console to create the resources, and create the resources in the order given.

Procedure

To create the JMS destination queue, complete the following steps:
1. Select Service integration > Buses, and click MONITOR.cell_name.Bus.
2. Select Destination resources > Destinations, and then click New.
3. When the create new destination queue creation wizard launches, ensure that Queue is selected, and click Next.
4. Name the resource MonitorEventEmitterXMLQueue2. The default is MonitorEventEmitterXMLQueue.
5. For the description, provide a general description of the queue (for example: Queue for the Business Monitor server JMS event emitter queue. Click Next.
6. Select the Node where the Bus member resides, click Next, and then click Finish.
To create the JMS error destination queue, repeat Step 1. Name the resource MonitorEventEmitterXMLErrorQueue2. The default is MonitorEventEmitterXMLErrorQueue. For the description, type Bus for the Business Monitor server JMS event emitter error queue.
Specify the error queue as the exception destination queue.
1. Select Service integration > Buses, and click MONITOR.cell_name.Bus.
2. Select Destination resources > Destinations, and select the destination queue that you created in Step 1.
3. In the Exception destination section, select the Specify button, and specify the name of the error queue that you created in Step 2
4. Click OK, and then click Save.
To create the error queue connection factory, complete the following steps:
1. Select Resources > JMS > Queue connection factories.
2. Select the appropriate scope for the new error queue connection factory, and click New.
3. Click OK to accept the default messaging provider.
4. On the Configuration tab, type the Name, Description, and JNDI name for the new error queue connection factory, and select the Bus name. Click OK, and then click Save. See the following list items:
  - Name: MonitorEmitterXMLErrorQConnFactory2
    The default name is MonitorEmitterXMLErrorQConnFactory.
  - Description: ErrorQConnFactory for the Business Monitor server JMS event emitter queue
  - JNDI name: jms/MonitorEventEmitter/ErrorQConnFactory2
    The default JNDI name is jms/MonitorEventEmitter/ErrorQConnFactory.
  - Bus name: MONITOR.cell_name.Bus
5. Specify the Security Settings for a secure environment, and then click Apply. The authentication alias for XA recovery is MonitorBusAuth. The Container-managed authentication alias is MonitorBusAuth.
To create the queue connection factory, repeat Step 4. Use the following information:
- Name: MonitorEmitterQConnFactory2
  The default name is MonitorEmitterQueueConnFactory.
- Description: QConnFactory for the Business Monitor server JMS event emitter queue
- JNDI name: jms/MonitorEventEmitter/QueueConnFactory2
  The default JNDI name is jms/MonitorEventEmitter/QueueConnFactory
- Bus name: MONITOR.cell_name.Bus
To create the JMS queue, complete the following steps:
1. Select Resources > JMS > Queues.
2. Select the appropriate scope for the new queue, and click New.
3. Click OK to accept the default messaging provider.
4. On the Configuration tab, type the Name and JNDI name for the new queue, and select the Bus name and the Queue name. Click Apply. See the following list items:
  - Name: MonitorEventEmitterQueue2
    The default name is MonitorEventEmitterQueue
  - JNDI name: jms/MonitorEventEmitter/Queue2
    The default JNDI name is jms/MonitorEventEmitter/Queue.
  - Bus name: MONITOR.cell_name.Bus
  - Queue name: Select the JMS destination queue that you created in Step 1
To create the JMS error queue, repeat Step 6. Use the following information:
- Name: MonitorEventEmitterErrorQueue2
  The default name is MonitorEventEmitterErrorQueue
- JNDI name: jms/MonitorEventEmitter/ErrorQueue2
  The default JNDI name is jms/MonitorEventEmitter/ErrorQueue
- Bus name: MONITOR.cell_name.Bus
- Queue name: Select the JMS error destination queue that you created in Step 2
To create the activation specification, complete the following steps:
1. Select Resources > JMS > Activation specifications.
2. Select the appropriate scope for the new activation specification, and click New.
3. Click OK to accept the default messaging provider.
4. On the Configuration tab, type the Name, JNDI name, and select the Bus name, Destination type, and Destination JNDI for the new activation specification. See the following list items:
  - Name: MonitorEventEmitterActivationSpec2
    The default name is MonitorEventEmitterActivationSpec
  - JNDI name: jms/MonitorEventEmitter/ActivationSpec2
    The default JNDI name is jms/MonitorEventEmitter/ActivationSpec.
  - Bus name: MONITOR.cell_name.Bus
  - Destination type: Queue
  - Destination JNDI: Select the JMS destination that you created in Step 1
5. Set the Authentication Alias to MonitorBusAuth.Click OK, and then click Save.
To create the event emitter factory for the REST event emitter service, follow these steps:
1. Select Service integration > Common Event Infrastructure > Event emitter factories
2. Select the appropriate scope for the new event emitter factory, and click New.
3. On the Configuration tab, type the Name and JNDI name for the new event emitter factory. Click Apply. See the following list items:
  - Name: EmitterFactoryForREST2
    The default name is EmitterFactoryForREST.
  - JNDI name: com/ibm/monitor/EmitterFactoryForREST2
    The default JNDI name is com/ibm/monitor/EmitterFactoryForREST.
4. Under Event transmission, select Support event service transmission, select Use entry from below, and then type com/ibm/events/configuration/bus-transmission/Default.
To create the event emitter factory for the JMS event emitter service, repeat Step 9. Click OK, and then click Save. See the following list items:
- Name: EmitterFactory2
  The default name is EmitterFactory.
- JNDI name: com/ibm/monitor/EmitterFactory2
  The default JNDI name is com/ibm/monitor/EmitterFactory.
Restart your server so that the changes take effect. If you are creating resources in a network deployment (ND) environment, restart the cluster where the resources were created.