JMS Connector Inbound

Owned by
Former user (Deleted)
Mar 10, 2015
2 min read


Overview

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

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

The JMS 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 JMS provider and be associated to the application workload via the UAC.xml configuration file.


See JMS 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 a JMS Listen inbound operation using the Universal Event Monitor for SOA JMS Connector.


System Flow Description

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

Step 1

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

Step 2

The JMS Inbound Connector reads the JMS 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 JMS Inbound Connector to know what to read from.

Step 3

The JMS 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 JMS message to the file.