Chapter 6. Extended Enterprise runtime patterns 115
6.5 Exposed Router variation
The Exposed Router variation of the Exposed Broker runtime pattern applies to
solutions where the partner’s source application initiates an interaction that is
forwarded to, at most, one of multiple target applications. The selection of the
target application is controlled by the distribution rules that govern functioning of
the connector component.
6.5.1 Generic profile
In the Exposed Router variation shown in Figure 6-6, the Exposed Router node
provides the logic to perform intelligent routing of messages to one target
application at a time. It does not include the simultaneous distribution or
decomposition capabilities that the Exposed Broker node provides.
Figure 6-6 Exposed Router runtime pattern: generic profile
The Exposed Router variation of the Exposed Broker application pattern can be
thought of as an extension to the Router variation of the Broker application
pattern. It also includes functionality to include external partners in a solution by
exposing their processes to internal processes.
Inter-enterprise
Zone
Enterprise
Demilitarized Zone Enterprise Secure ZonePartner Zone
App Server/
Services
App Server/
Services
Network
Infrastructure
Domain FirewallDomain Firewall
Exposed
Router
Protocol FirewallProtocol Firewall
Connector
App Server/
Services
App Server/
Services
App Server/
Services
Rules
Directory
Directory
& Security
Services
Router
Rules
Source
Application
Exposed Broker: Router variation
Target
Application
Partner A
Target
Application
Partner B
Target
Application
Partner C
R/O
Router Rules
116 Patterns: Extended Enterprise SOA and Web Services
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.
The Application Server/Services nodes execute the logic of the target and source
applications.
6.5.2 SOA profile
In the SOA profile for the Exposed Router runtime pattern, the Exposed Router,
Rules Directory, and Partner Infrastructure are specialized as shown in
Figure 6-7 to instead become:
An Exposed ESB Gateway
An ESB
Service Consumers and Providers
Figure 6-7 Exposed Router runtime pattern: SOA profile
The Exposed ESB Gateway provides support for the exposed requirement of the
Extended Enterprise pattern. It provides a single point of access between:
Inter-enterprise
Zone
Enterprise
Demilitarized Zone Enterprise Secure ZonePartner Zone
App Server/
Services
App Server/
Services
Network
Infrastructure
ESBESBESB
Domain FirewallDomain Firewall
Exposed
ESB
Gateway
Protocol FirewallProtocol Firewall
Connector
App Server/
Services
App Server/
Services
<Service Consumer>
App Server/
Services
<Service Provider>
Directory
& Security
Services
Router
Rules
Source
Application
Exposed Broker: Router variation
Target
Application
Partner A
Target
Application
Partner B
Target
Application
Partner C
R/O
Router Rules
Get Patterns: Extended Enterprise SOA and Web Services 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.