|
Extended Enterprise::Exposed Serial Process application pattern::Runtime patterns
On this page, two categories of Runtime patterns are described:
Generic Exposed Serial Process runtime patterns
The Runtime pattern shown below represents a basic topology for the implementation of the Entended Enterprise::Expsoed Serial Process application pattern. It can be further enhanced by clustering the key nodes to imporove the availability characteristics.
Exposed Serial Process application pattern::Runtime pattern
(Click a node to get a detailed explanation.)
Design Last Updated: 11-11-2005
This basic topology leverages the following nodes with their associated responsibilities:
-
Exposed 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.
This node is also responsible for invoking target applications as necessary through their associated connectors.
-
Connector nodes
Connector nodes between the process manager and application server/services nodes are not explicitly modeled in this Runtime pattern. This allows us to focus on the partner to partner connection. A standard pattern of path connectors (firewalls and network infrastructure) is shown, but other variations exist with fewer or more firewalls.
The secure zone connector is primarily concerned with logical connection of the path connector to the application services. Therefore, it is often modeled as an adapter connector.
Less secure applications and connectors may be placed within the DMZ, depending on local security policies. They are usually placed as shown in the figure above.
The Connector in the Enterprise Demilitarized Zone may or may not be modelled. It provides connectivity from the Enterprise Secure Zone to the Inter-enterprise Zone. It may be a low level component (e.g. TCP/IP infrastructure) which is omitted from the diagram or it may have more advanced capabilities such as caching of reusable content (e.g. a Web server).
The Directory and Security Services supplies authentication and authorization
services. It also holds the user ID and password and related privileges. This
node typically leverages LDAP-based directories. It also contains configuration
information needed to support secure access between the enterprise and partner
services.
SOA profile
In this second section we specialize the Router pattern for the SOA environment using the SOA profile. The SOA profile terminology is indicated using the [SOA] qualifier.
The generic Exposed Process Manager, Rules Directory and Partner Infrastructure in the figure above are specialized in the SOA profile to:
- an Exposed ESB Gateway (supporting the Exposed requirement)
- an ESB (supporting the SOA infrastructure requirement for service location transparency and interoperability, encapsulated reusable business function and explicit implementation-independent interfaces)
- a BSC node (supporting the Process Manager requirement)
- Service Consumers and Providers representing the Partner infrastructure
[SOA]Exposed Serial Process runtime pattern (aka Exposed ESB Gateway, BSC composite pattern)
(Click a node to get a detailed explanation.)
Design Last Updated: 11-11-2005
Next, review product mappings for this Runtime design.
| 
