MQ Connector Inbound

Owned by
Stonebranch
Jul 03, 2023
2 min read


Overview

The MQ Connector - Inbound operation is an asynchronous operation that uses the Listen MEP.

It consists of a remote application workload publishing an MQ message using the MQ protocol to a specified destination queue hosted by the MQ provider. The MQ provider, which hosts the queues that represent the MQ destination, can be located on a remote application server or on the local application server that hosts Universal Event Monitor for SOA.

The MQ inbound connector listens on the specified destination queue for messages to arrive. When a message arrives, it reads the message off of the queue. The body of the message, which is usually associated with the application data, is written to a file where either:

  • Universal Event Monitor (UEM) can use the event as a trigger.
  • External application, such as a scheduler, can access the files directly.

Note

The destination queue must be hosted by the MQ provider and be associated to the application workload via the UAC.xml configuration file.


See MQ Inbound Connection for examples and UAC.xml File Description for a description of the elements and structure of the UAC.xml file.

System Flow

The following figure illustrates the system flow for an MQ Listen inbound operation using the Universal Event Monitor for SOA MQ Connector.


System Flow Description

The following list describes the steps (1 - 3), above.

Step 1

The application workload publishes an MQ message to a specified destination queue hosted by an MQ provider. The MQ Inbound Connector listens on the provider queue for the incoming message.

Step 2

The MQ Inbound Connector reads the MQ message from the inbound queue. Because the read is destructive, once the message is read from the queue, it is no longer available to other applications. The destination queue must be configured in the UAC.xml file in order for the MQ Inbound Connector to know what to read from.

Step 3

The MQ Inbound Connector writes the content of the message to the file whose name and location you specify in the UAC.xml configuration file. If you set the writeProperties attribute to true, Universal Event Monitor for SOA will write both the properties and content of the MQ message to the file.