UAC (Universal Application Container)

The Universal Application Container (UAC) component executes the workload request and provides the server functions associated with a container environment.

Its responsibilities include the following:

• Provide a scalable and secure platform foundation for Universal Command Agent for SOA.
• Provide Publish, Listen, and Request / Reply functionality.
• Provide a deployment environment for the connectors.
• Provide persistence and fault tolerance mechanisms.
• Provide auditing, logging, and error handling functionality.
• Provide an interface for remote operations for Universal Broker.
• Can process multiple UAI requests.

UAC is a resident process that is started by Universal Broker and stays resident until stopped by Universal Broker. UAC receives and processes the message from UAI. It passes the data in the message to the appropriate connector, which then builds the message and initiates the requested workload operation.

The reply may consist of a simple acknowledgement that the workload started or completed, or it may contain application messages or workload output. In either case, UAC passes the reply message back to UAI unaltered. The exceptions to this are the SOAP faults, which are mapped to error messages, which then are passed to UAI. The requests and replies are persisted as well for fault tolerant operations.

The following figure summarizes the basic process flow for UAC.