Skip to main content

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

Overview

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

Generic DC runtime patterns

Parallel Process application pattern::Runtime pattern

Parallel Process::Runtime pattern Application Server / Services Application Server / Services Application Server / Services Connector Connector Connector Process Manager Application Rules Directory Directory and Security Services Service Consumer and Service Providers are linked via a Process Manager and Connectors. The Process Manager node is also linked with a Rules Directory node.
Design Last Updated: 10-20-2004
(Click a node to get a detailed explanation.)

The Runtime pattern shown above represents a basic topology for the implementation of the Parallel Process Application pattern. 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 their associated responsibilities:

  • Process manager node
    This node contains the process flow execution engine. 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 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 target applications as necessary through their associated connectors.
  • 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 Parallel Process pattern for the SOA environment using the SOA profile. The SOA profile terminology is indicated using the [SOA] qualifier.

[SOA]Parallel Process

[SOA]Parallel Process Application Server / Services Application Server / Services Application Server / Services Application Server / Services Application Server / Services Application Server / Services Application Server / Services Application Server / Services Business Service Choreography Enterprise Service Bus
Service Consumers and Providers are linked via an Enterprise Service Bus and a Business Service Choreography node. Design Last Updated: 10-20-2004
(Click a node to get a detailed explanation.)

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.

Close [x]

App Server/Services

Applications rely on services provided by their hosting server to interact with other applications. These are modeled using the application server/service node. Some examples of services provided by this node include:

  • A TCP/IP pipe established using the hosting operating system
  • A servlet or Enterprise JavaBean (EJB) invoked by WebSphere Application Server
  • The Java Message Service (JMS) or Java 2 Platform, Enterprise Edition (J2EE) Connector application programming interfaces (APIs) provided by WebSphere

Close [x]

Connector

Connectors provide the connectivity between two components. A connector is always present to facilitate interaction between two components.

Depending on the required level of detail, a connector can be:

  • A primitive (or unmodelled) connector, represented by a simple line between components
  • A component (or modelled) connector, represented by a rectangle on a line between components

A connector may be an adapter connector, a path connector, or both. See the following two sections respectively.

Close [x]

Process Manager

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.

Close [x]

Rules Directory

The rules directory contains the rules generally used to control the mode of operation of an interaction, depending on external factors. Examples of such rules are:

  • Business data mapping rules (for adapter connectors)
  • Process execution rules and intermediate results
  • Autonomic rules (such as priority in a shared environment)
  • Security rules
  • Capacity and availability rules

The rules directory may or may not exist. If it exists, it can still be left off the Runtime pattern when analysis determines that interaction rules are not an important part of the solution, for example.

Close [x]

Directory and Security Services

This node supplies authentication and authorization services. It also holds the user ID and password and related privileges. This node typically leverages Lightweight Directory Access Protocol (LDAP)-based directories and contains configuration information needed to support secure and controlled access to services.

Close [x]

Business Service Choreography

Business Service Choreography (BSC) allows for the development and execution of business process flow logic, which is centrally controlled and outside application logic. This facilitates the implementation of changes to the business process and the monitoring and analysis of business process execution. The business process governs the sequence and control of service invocations.

Close [x]

ESB

The ESB is a key enabler for a SOA as it provides the capability to route and transport service requests from the service requester to the correct service provider. The true value of the ESB concept, however, is to enable the infrastructure for SOA in a way that reflects the needs of today’s enterprise: to provide suitable service levels and manageability, and to operate and integrate in a heterogeneous environment.

Furthermore the ESB needs to be centrally managed and administered and have the ability to be physically distributed.

Close [x]

SOA

The original set of PI patterns is intended to satisfy a wide generic set of integration requirements, not just SOA. The SOA profile specialises these more general patterns for the SOA environment.