Patterns: Implementing Self-Service in an SOA Environment

62 Patterns: Implementing Self-Service in an SOA Environment

Figure 4-3 Directly Integrated Single Channel application pattern::Runtime pattern: SOA profile

In this SOA profile, the application server node becomes the service consumer

with the back-end applications acting as service providers. The service

consumer is connected to the service providers with a simple enterprise service

bus. Due to the nature of the SOA approach, the consumer and provider could

be reversed.

Implementing the SOA profile with an ESB adds extra capabilities to the runtime

pattern, for example routing and decomposition capability. Because of this, the

SOA profile for the Directly Integrated Single Channel runtime pattern can be

applicable to multiple Self-Service application patterns. This highlights the fact

that using SOA facilitates the future expansion of solution functionality without

requiring major changes to the middleware structure.

4.3 Runtime patterns for Router

The Router application pattern provides intelligent routing from multiple channels

to multiple back-end applications using a hub-and-spoke architecture. The

interaction between the user and the back-end application is a one-to-one

relation, meaning the user interacts with applications one at a time.

Internal Network

Demilitarized Zone

(DMZ)

Outside World

Protocol

Firewall

Domain

Firewall

I

N

T

E

R

N

E

T

Public Key

Infrastructure

User

Web

Server

Redirector

Domain Name

Server

Directory and

Security

Services

Presentation

Directly Integrated Single Channel application

Application

Application

Application

ESB

Application

Server

Existing

Applications

and Data

<service consumer>

<service provider>

Business

Service

Directory