Jump to: navigation, search

Using a Message Queue with Event Logger

You can have Event Logger send events to a message queue, such as IBM MQ-Series, or Microsoft Message Queue (MSMQ). This provides a mechanism for reliable reporting events delivery to Interaction Server's reporting clients. Disconnection of the client does not lead to a loss of reporting events. Instead, events are stored in the message queue and delivered to the client (or otherwise read by the client) after it reconnects.

To use this functionality, you must create a DAP object that is specifically for the streaming of reporting events into MSMQ or MQ-Series. Both Interaction Server and the client connect to this DAP. This DAP must have the following section and options, which partly resemble the sections and options of the Event Logger DAP and are also documented in the eServices 8.1 Reference Manual:

  • logger-settings section
    • delivery-protocol. Possible values are:
      • event-log—The default, for using Event Logger database scripts
      • mq-series—For the MQ-Series message queue system
      • msmq—For the MSMQ message queue system
      • jms—For a JMS queue
      • groovy—For the Groovy Event Logger
    • delivery-queue-name—The name of the queue to send messages to.

Optionally, Event Logger DAP can use the following section and option:

  • event-filtering section. Contains the single option event-filter-by-id, whose value is a list of comma-separated event identifiers. Only these events are sent to the message queue; events not listed are not sent. This option is analogous to the option of the same name used in the Event Logger DAP.
The event identifiers used in event-filter-by-id are listed in the Platform SDK 8.1 API References for Java and .NET.
This page was last edited on August 27, 2020, at 14:21.
Comments or questions about this documentation? Contact us for support!