Jump to: navigation, search

Using the JMS Event Logger with Oracle OpenMQ

This page provides an example of configuring a JMS Event Logger Application object when using the OpenMQ provider.

Configuring JMS Event Logger Application with Oracle OpenMQ

  1. Create Database Access Point Application in the Configuration Manager named EL_OpenMQ.
  2. On the Options tab, create a section named logger-settings. In this section add the following options:
    • [logger-settings]
    • delivery-protocol=jms
    • jms-connection-factory-lookup-name=ConnectionFactory
    • jms-initial-context-factory=com.sun.jndi.fscontext.RefFSContextFactory
    • delivery-queue-name= IxnEventLogQueue
    • jms-provider-url= file:///D:/OpenMQExample (the path points to the folder where the .bindings file (in UNIX file format) is stored on the Interaction Server host)
  3. On the Connections tab of the Interaction Server Application definition, add the created Event Logger.
  4. Configure the Interaction Server options to load JVM and all of the required libraries. Interaction Server Configuration for working with OpenMQ is described in the OpenMQ—Interaction Server JVM section of the JMS Capture Point Guide.

OpenMQ—JMS EventLogger Queue

This section provides an example of setting up queue for the JMS Event Logger when using OpenMQ provider.

Setting up EventLogger queue with Open Message Queue Administration Console

  1. Connect to the OpenMQ broker that is running.
  2. Add the following queue using the Add Broker Destination dialog: IxnEventLogQueue
  3. For the queue that you have added, set Max Number of Producers and Max Number of Active Consumers to Unlimited.
  4. Add a new Object Store and set the following JNDI Naming Service Properties:
    1. Set java.naming.factory.initial to com.sun.jndi.fscontext.RefFSContextFactory.
    2. Set java.naming.provider.url to file:///D:/OpenMQExample.
      Important
      This is the directory in which the .bindings file containing definitions will be saved.
  5. Connect to the newly created object store.
  6. Add a connection factory object using the Add Connection Factory Object dialog:
    1. Specify the lookup name, such as ConnectionFactory.
    2. Specify the Factory Type as QueueConnectionFactory.
    3. In the Client Identification tab, specify the Default Username and Default Password (for example, guest/guest).
  7. Add destinations to the object store for all four queues that you defined previously.
    Important
    The lookup names can be different from the destination names.
  8. After the above steps have been completed, the folder D:/OpenMQExample/ contains the .bindings file with connection factory and queue definitions. Open the file, examine it for the presence of the defined queues and connection factory, and save it with File format set to UNIX so that it is possible to use it on UNIX operating systems.
This page was last edited on June 19, 2020, at 12:28.
Comments or questions about this documentation? Contact us for support!