|
Application Integration::Parallel Workflow variation::Runtime patterns
On this page, two categories of Runtime patterns are described:
Generic DC runtime patterns
Parallel Workflow variation::Runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 10-20-2004
The Runtime pattern shown above represents a basic topology for the implementation of the Parallel Workflow variation. It can be further enhanced by clustering the key nodes in order to improve the availability characteristics.
This basic topology leverages the following nodes with the associated responsibilities:
-
Workflow manager node
This node contains the workflow execution engine that coordinates the process flow across systems and people. It provides the capability for model-driven business process automation and enables tracking by leveraging the process execution rules stored in the associated database. These processes can span multiple applications and people across organizational boundaries within an enterprise. The node maintains state and tracks sequencing through the process flow. In doing so, it often leverages the associated database to store intermediate results. It is also responsible for invoking the target application as necessary through the associated connectors. Finally, when a particular task requires human interaction, this node creates a work item and identifies a particular person or a department is responsible for executing that task and adds the work item to its worklist.
-
-
Staff worklist adapter node
A specialized adapter is responsible for presenting the work items to be executed by a particular person or a department. It is the primary interface through which the humans interact within the end-to-end workflow.
-
-
Connector nodes
A connector node is used to provide connectivity between the following:
-
The App Server/Services node and the Process Manager
This allows a source application to communicate with a Process Manager.
Process Managers usually support multiple connector types.
-
The Process Manager and an App Server/Services node
This allows a Process Manager to communicate with a target application.
Process Managers usually offer multiple connector types.
-
-
Repository node
This node provides a persistent data storage and retrieval service in support of the execution of the process flow. It holds the Process Execution Rules.
SOA profile
In this second section we specialize the Workflow variation pattern for the SOA environment using the SOA profile. The SOA profile terminology is indicated using the [SOA] qualifier.
Parallel Workflow variation
(Click a node to get a detailed explanation.)
Design Last Updated: 10-20-2004
This [SOA] PI pattern will be redrawn following the next series of SOA redbooks. It will abstract the picture, removing user, internet and application representations.
The diagram illustrates how the WS-I sample business scenario is applied to this Runtime pattern. This sample business scenario shows a supply chain management process. The scenario is developed by the Web Services Interoperability Organization and is designed to test compliance with the WS-I Basic Profile.
The key benefits of using Business Service Choreography are:
- Flexibility: achieved by externalization of process logic for the individual application.
- Human interaction: facilitating various staff functions such as approval, investigation, and claim.
- Reusability of the software components or services in the process, resulting in cost savings.
- The construction of processes from services with explicit interfaces enables the easy substitution of one service interface with another.
Next, review product mappings for this Runtime design.
| 
