SOAP Connector Request-Reply Operation

Owned by Stonebranch (Deactivated)
Jul 15, 2024
2 min read

Overview

The SOAP Connector operation is, by default, a request/reply operation with the same constraints as the HTTP operation.

When the request is made, the reply from the target workload can be either of two types:

Reply with Acknowledgement

In this type, the request is acknowledged via the reply, but no data is sent back. The target workload is executed with no additional feedback.

Reply with Payload

In this type, the request blocks until a reply is received from the target workload containing data, presumably after either:

  • Target workload has completed.
  • Error was issued during execution.

The data can be the results of the workload, the workload status, or an error message.

System Flow

The following figure illustrates the system flow for a SOAP Connector Request / Reply operation using the Universal Command Agent for SOA: SOAP Connector.



System Flow Description

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

Step 1

Universal Command is executed requesting the HTTP workload. The command options for the Universal Command Agent for SOA: SOAP 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: SOAP Connector sends the workload execution message via SOAP and blocks for the reply.

Step 4

When the target workload completes, or aborts due to an error, it replies to the workload execution request with either return code and data or the error message.

Step 5

UAC replies to UAI, which returns the relevant information to UCMD.