64 Patterns: Implementing Self-Service in an SOA Environment
primary business logic resides. This may involve activities such as message
transformation, protocol conversion, security management, and session
concentration. The integration server may use a database to look up routing
information, as a caching device, or for holding intermediary data.
4.3.2 SOA profile for Router
The Runtime pattern for the Router application pattern can be refined as shown
in Figure 4-5 to take advantage of service oriented architecture technology. 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 via a simple enterprise service bus.
Figure 4-5 Router application pattern::Runtime pattern: SOA profile
In this pattern the ESB node has replaced the integration server node. It provides
the message routing function, as well as protocol conversion, logging,
transformation, or other tasks related to the proper routing of messages.
The ESB approach:
Minimizes the number of adapters required to link service consumers to
service providers.
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
ESB
Application
Server
Existing
Applications
and Data
<service consumer>
<service provider>
Business
Service
Directory
Presentation
Router application pattern
Application
Application
Presentation
Router
Get Patterns: Implementing Self-Service in an SOA Environment now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
