Jump to: navigation, search

Using the JMS Event Logger with IBM WebSphere MQ

This page provides an example of configuring a JMS Event Logger Application object when using WebSphere MQ.

This is a specific example of the more general configuration procedure.

Configuring JMS Event Logger Application with IBM WebSphere MQ

  1. On the Options tab, create a section called logger-settings. In this section add the following options:
    • Delivery-protocol=jms
    • delivery-queue-name =event(the same as the corresponding Destination name)
    • jms-connection-factory-lookup-name=my_ConnFactory (the name of the connection factory that you created in WebSphere MQ)
    • jms-initial-context-factory=com.sun.jndi.fscontext.RefFSContextFactory
    • jms-provider-url=file:///home/InteractionServer (the path points to the folder where the .bindings file, in UNIX file format, is stored on the Interaction Server host)
  2. On the Connections tab of the Interaction Server which will use this JMS Message queue, add the just created Event Logger.

Next Steps

Configure the Interaction Server options to load JVM and all of the required libraries. Interaction Server Configuration for working with WebSphere is described in the WebSphereMQ—Interaction Server JVM section of the JMS Capture Point Guide.

WebSphereMQ-JMS Event Logger Queue

This page provides an example of setting up queue for the JMS Event Logger when using IBM WebSphere MQ.

Setting up queue using IBM WebSphere MQ Explorer

  1. Start WebSphere MQ Explorer. Find the Object tree in the Navigator window.
  2. Right-click the Queue Managers node and select New to create a new Queue Manager. Follow the steps in the resulting Wizard, choosing a name (for example, my_QManager) and unique listening port.
  3. As the Object tree is updated, find the Queue node under the new Queue Manager. Right-click this node and select New > Local Queue.
  4. Create Local Queue named mq_event. Select Persistent for the Default Persistence setting.
  5. With the Queue node selected in the Object tree, right-click mq_event in the Content pane and select Put Test Message. Enter any text of your choice in the Message data field, then click Put message. This test message waits in the queue until the Event Logger retrieves it.
  6. In the Object tree, right-click the JMS Administered Objects node and select Add Initial Context. Choose File system for the JNDI namespace location and select the directory where the corresponding storage file will be created.
  7. The new node for initial context now appears in the Object tree. Select it and verify that the Connection Factories and Destinations nodes appear under it. If necessary, right-click and use the context menu to connect to the InitialContext object make these nodes visible.
  8. Right-click Connection Factories and select New > Connection Factory. Enter or select the following values:
    • Sample name—my_ConnFactory
    • Messaging provider—WebSphere MQ
    • Transport—MQ Client
    • Base queue manager and Broker queue manager (last screen)—the Queue Manager that you created in Step 2.
    • Host name and port—Correct values for your environment
  9. Right-click Destinations and select New > Destination and create a new Destination that corresponds to the queue that you created in Step 4:
    • Type—Queue
    • Names—jms-event
    • On the last screen, select the proper Queue Manager and Queue objects.
  10. Find the file named .bindings at the location established in Step 6. It will be referred to later on the sample configuration.
This page was last edited on June 19, 2020, at 12:29.

Feedback

Comment on this article:

blog comments powered by Disqus