Universal Agent for SOA for UNIX - Deployment Options

Owned by
Former user (Deleted)
Sept 05, 2013
2 min read

Deployment Options

Deployment of Universal Agent for SOA has been designed to be flexible in order to fit the needs of your Enterprise IT.

There are two main deployment options:

  1. Single-Server Deployment (SSD)
  2. Distributed Server Deployment (DSD)

SSD is the default deployment.

Single-Server Deployment (SSD)

Single-Server Deployment (SSD) is where all components, with the exception of the Universal Command Agent managers, are deployed to the same physical server. This includes Universal Command Agent for SOA, Universal Broker and associated components, and your target workload(s).

The following figure illustrates the Single Server Deployment (SSD).

 

 

SSD Deployment Flow of Events

The following list identifies the flow of events that occur with SSD deployment:

  1. The calling application invokes the Universal Command (UCMD) Manager to execute a remote workload. For this example the remote workload, or target workload, is an internet or message based workload.
     

    Note

    Although this figure implies the use of a Java-based workload, you can execute any remote workload, regardless of what language the workload is implemented in, as long as it has an interface that supports HTTP, SOAP, or JMS.

     
  2. The request is forwarded to the Universal Broker specified in the invocation of the Universal Command Manager, which then spawns the UCMD Server and passes the workload execution request to Universal Command Agent for SOA.
  3. Universal Command Agent for SOA will execute the workload deployed on the same physical server and return any messages or data back to the Universal Command Manager.

Distributed Server Deployment (DSD)

Distributed Server Deployment (DSD) is where:

  • Universal Broker and Universal Command Agent for SOA are located together on one physical server.
  • Target workload is located on a different physical server.

Note

The target workload location is user-defined. The SERVICE_URL option specifies how Universal Command Agent for SOA knows where to look for the target workload.


The following figure illustrates the Distributed Server Deployment (DSD).
 

 

DSD Deployment Flow of Events

The flow is nearly the same as with the Single Server Deployment except that the location of the target workload is not localhost.