Producing events for consumption by JMS applications

Configure WebSphere® Application Server so that you can use a JMS application to consume events that are emitted by a local mapping service.

Before you begin

You can configure your local mapping service to emit events, which are useful for monitoring and archive purposes. For more information about when the events are emitted and the ways you can consume these events, see Event emissions when using service mapping. Follow the steps in this task if you want to use your own JMS application to consume the events. Alternatively, you can use the built-in data capture functions in IBM® Integration Bus to view and process the events. See Producing events for consumption by IBM Integration Bus for instructions on configuring this option.

About this task

The local mapping service can publish events into any JMS provider that is configured in WebSphere Application Server. See Types of messaging providers for information about the different messaging providers you can use. For example, you can use the following topologies:
  • Publish the events into the default messaging provider for WebSphere Application Server. Configure a JMS application that runs in WebSphere Application Server to subscribe to the default messaging provider, so that the application is notified of each event emission.
  • Publish the events into a WebSphere MQ messaging provider. Configure a JMS application that runs either inside or outside WebSphere Application Server to subscribe to the WebSphere MQ topic, so that the application is notified of each event emission.
  • Publish the events into a third-party JMS messaging provider. You must either configure the provider by using a Java™ EE Connector Architecture (JCA) resource adapter, or define it as a third-party non-JCA messaging provider.
For any of these example scenarios, you must configure a JMS unified connection factory and a JMS topic for the messaging provider.

Procedure

  1. Configure a JMS unified connection factory. Make a note of the JNDI name that you use for the connection factory. You must provide the same value for the -connectionFactory parameter when you run the createLMServiceEventPoint command.
  2. Configure a JMS topic. You can specify the JMS topic that events are published to when you run the createLMServiceEventPoint command. If you do not specify a topic, events are published to a topic by using the default topic string:
    $SYS/AppServer/<cell_name>/<node_name>.<server_name>|<cluster_name>/<client_application_name>/<LMS_name>/<operation_name>
    Where either <node_name>.<server_name> must be specified, or <cluster_name> must be specified, depending on your configuration. For more information, see Creating an event point on a local mapping service by using the command line.
  3. To include message data in events, you must create the WebSphere variable SM_EVENT_POLICY_PERMIT_MESSAGE_DATA and set its value to true. For a Network Deployment environment, the scope of the WebSphere variable definition determines whether the policy is applied to all nodes in the cell, or to individual clusters or servers. For information about managing WebSphere variables, see Creating, editing, and deleting WebSphere variables.
  4. To understand the event format and contents, see Service mapping event schema.

What to do next

You have now configured WebSphere Application Server to publish service mapping events so that a JMS application can consume them. You must also configure WebSphere Application Server to emit the events by creating and enabling an event point. You can control the contents of the events when you create the event point. Follow the steps in Creating an event point on a local mapping service by using the command line.


Icon that indicates the type of topic Task topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Tuesday, 22 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-express-iseries&topic=tsmwas_eventsconsumptionjms
File name: tsmwas_eventsconsumptionjms.html