Overview

The JMS Connector Request / Reply operation is a synchronous operation that uses a temporary queue to process the reply.

System Flow

The following figure illustrates the system flow for a JMS request / reply operation using the Universal Command Agent for SOA: JMS Connector.

The following list describes the steps (1 - 5) identified above:

Step 1	Universal Command is executed requesting the HTTP workload. The command options for Universal Command Agent for SOA: JMS Connector are read in from a script file specified with the SCRIPT_FILE option and the message payload is read in via STDIN. UCMD then sends the workload request to Universal Command Agent for SOA (specifically, the UAI component).
Step 2	Universal Command Agent for SOA receives the request from UCMD Server via STDIN. The UAI component validates the command options and existence of the message payload, sends the request to UAC, and blocks. UAC builds the workload execution message for the target workload.
Step 3	Universal Command Agent for SOA: JMS Connector publishes the workload execution message to the specified destination queue.
Step 4	Universal Command Agent for SOA: JMS Connector then reads the reply message off of the temporary reply queue specified in the properties file.
Step 5	UAC returns the reply message to UCMD (or an error message, if the operation failed).