Universal Command Agent for SOA Usage
Starting and Stopping
Universal Command Agent for SOA is started and stopped by Universal Broker via the UAC Server component.
There is no user interaction for this operation.
Message Payload
The message payload contains the data required for the target workload to execute. This can include operation information, input parameters, authentication information, and any other data required by the target workload (application or service) to operate.
The payload file is an XML document that Universal Command Manager reads in through STDIN.
All HTTP and SOAP operations require a payload, while the JMS and MQ operations do not require a payload.
The payload format is validated for HTTP, SOAP, and MQ messages because the payload is in xml format and must be parsed.
There is no validation of the payload format for JMS messages because the payload is in text format. If you include xml-style elements and attributes in your JMS messages, it will be up to the target application to validate the format.
The content of the payload for all protocols is not validated because the payload represents business data; it is not the responsibility of Universal Command Agent for SOA to know about business details related to the workload that it is executing.
For an example of message payload, see Web Services Execution.
Additional Information
The following pages provide additional detailed information for Universal Command Agent for SOA usage: