Application Integration::Serial Process application pattern::Runtime patterns

On this page, two categories of Runtime patterns are described:

• Generic
• SOA profile

Generic DC runtime patterns

Serial Process application pattern::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 Application Integration::Serial Process application pattern. It can be further enhanced by clustering the key nodes to improve the availability characteristics.

This basic topology leverages the following nodes with their associated responsibilities:

• Process manager node
  This node contains the process flow execution engine. It provides the capability for model-driven business process automation. It also enables tracking by leveraging the process execution rules stored in the associated database.
  These processes can span multiple applications and organizational boundaries within an enterprise. The node maintains state and tracks sequencing through the process flow. In doing so, it often leverages the associated repository to store intermediate results. It is also responsible for invoking target applications as necessary through their associated connectors.
• 
  
  
• Connector nodes
  A connector node is used to provide connectivity between:
  • The application server/services node and the process manager node
    This allows a source application to communicate with a process manager. Process managers usually support multiple connector types.
  • The process manager node and an application server/services node
    This allows a process manager to communicate with a target application. Process managers usually offer multiple connector types.
  
  
• Rules Directory 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 Serial Process pattern for the SOA environment using the SOA profile. The SOA profile terminology is indicated using the [SOA] qualifier.

[SOA]Serial Process runtime pattern (aka BSC runtime pattern)
(Click a node to get a detailed explanation.)
Design Last Updated: 04-29-2005

The Business Service Choreography (BSC) runtime pattern allows for the development and execution of business process flow logic which governs the sequence and control of service invocations.
The business process is centrally controlled and not part of the program logic in individual applications. Therefore, rather than having the business process defined in multiple applications and within the interactions between these multiple applications, it can be modelled and implemented by a central function. This facilitates the implementation of changes to the business process and monitoring and analysis of business process execution.

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.