JMS Connector Publish Operation
Overview
The JMS Connector Publish operation is an asynchronous operation that places a JMS message and its payload on the specified destination JMS queue or topic.
UAC returns a message indicating whether the JMS message was successfully placed on the queue or sent on the topic.
System Flow
The following figure illustrates the system flow for a JMS publish operation using the Universal Command Agent for SOA: JMS Connector.
System Flow Description
The following list describes the steps (1 - 4) 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 queue or topic. |
Step 4 |
UAC returns a success message if the message was placed on the queue or topic with no error, or an error message if there was an error. This reply is generated by UAC, not the JMS provider. |