SOA ORCHESTRATION IMPLEMENTATION

Completion of an ESB provides your organization with an extremely flexible set of services to be used freely by any client. Since an ESB intentionally does not supply any form of control over which services are called by which other services and in which order, most organizations go on to add a set of Orchestration Services to control this flow. This allows business analysts to develop abstract process models with languages like Business Process Execution Language (BPEL).

Such Process Modeling is typically the first step in implementing this third level of an SOA. The underlying ESB allows the actual processing details of the target service to be isolated from the Orchestration Services. The technical implementation of the Orchestration Service then consists of providing an Orchestration runtime that can interpret the process model and then binding individual activities in the process to the Services that will execute them.

Orchestration Implementation deliverables:

• Process implementations deploy and tested on based upon supplied BPEL models
• Knowledge transfer on Orchestration Implementation and Service Binding.

Orchestration Implementation prerequisites:

• You have BPEL based models accurately describing the processes to be implemented. If you do not already have such models, see QAT’s Process Modeling engagement.
• You have an existing operational SOA Orchestration Server environment and fundamental knowledge of its operation. If you do not have such an environment, QAT will help you decide and implement an operational Orchestration Server.
• System administrators and Orchestration Server administrators for the target Orchestration Server system are available to the consultant to provide logins and necessary system resources.  

Duration: Highly variable according to project scope.

< previous | next >