Chapter 7. Product mappings 129
Consumer and the target partner Service Provider. Interactions within the
enterprise will not be secured.
A local DB2 Universal Database database is used to store the SDO (Service
Data Object) repository.
The IBM HTTP Server V6 acts as an Adapter Connector by providing protocol
transformation to SOAP/HTTPS thus delivering transport level security between
the enterprise and the partner organizations.
7.3 Exposed Broker product mapping
For our Exposed Broker scenarios, the responsibility for implementing the
business rules to identify which external partner organization to communicate
with has been implemented with an Exposed Broker or Exposed Router node.
7.3.1 Exposed Broker: Generic profile
Figure 7-3 illustrates the Product mapping for the Exposed Broker. The Exposed
Broker includes the means to expose partner processes to internal processes.
Figure 7-3 Exposed Broker: generic profile product mapping
This Product mapping uses WebSphere Application Server V6.0.2 to host the
Application Services in the Enterprise Secure Zone.
Inter-enterprise
Zone
Enterprise
Demilitarized Zone Enterprise Secure ZonePartner Zone
App Server/
Services
App Server/
Services
Network
Infrastructure
Domain FirewallDomain Firewall
Exposed
Broker
Protocol FirewallProtocol Firewall
Connector
App Server/
Services
App Server/
Services
IBM HTTP
Server V6
Microsoft .NET
WebSphere
Application
Server V6.0.2
Internet
App Server/
Services
WebSphere
Application
Server V6.0.2
CICS
Transaction
Server V3.1
WebSphere
Application
Server V6.0.2
Rules
Directory
Directory
& Security
Services
WebSphere
Application Server
V6.0.2 Network
Deployment Web
Services Gateway
WebSphere Application
Server V6.0.2 Network
Deployment Web Services
Gateway
• Service Integration Bus &
WebSphere Administration
(part of WebSphere
Application Server V6.0.2)
• DB2 Universal Database
130 Patterns: Extended Enterprise SOA and Web Services
The Exposed Broker node is implemented with the Web services gateway that is
part of WebSphere Application Server Network Deployment V6.0.2, which
supports the exposed nature of this node by providing a standard, consistent
interface for the internal processes to access external processes.
The Rule Directory node is implemented using the service integration bus
mediation support within WebSphere Application Server Network Deployment
V6.0.2.
In the Directory and Security services node, the Web services gateway security
will be configured for all transactions to the external Partner Zone to use
WS-Security integrity and confidentiality. In this scenario, the Application
Services in the Enterprise Secure Zone do not include support for WS-Security.
WebSphere Application Server Network Deployment V6.0.2 allows you to
configure a service integration bus to use WS-Security to secure the SOAP
messages that pass between the Service Consumer and the target partner
Service Provider. Interactions within the enterprise will not be secured.
A local DB2 Universal Database database is used to store the SDO repository.
The IBM HTTP Server V6 acts as an Adapter Connector by providing protocol
transformation to SOAP/HTTPS, thus delivering transport level security between
the enterprise and the partner organizations.
7.3.2 Exposed Router variation: SOA profile
Figure 7-4 on page 131 illustrates the Product mapping for the Exposed Router
variation. The Router logic is provided by the ESB node performing intelligent
routing of messages to one target application at a time. It does not include the
simultaneous distribution or decomposition capabilities that the Broker node
provides.
Chapter 7. Product mappings 131
Figure 7-4 Exposed Router variation: SOA profile product mapping
This Product mapping uses WebSphere Application Server V6.0.2 to host the
Application Services in the Enterprise Secure Zone.
The ESB is run in a service integration bus within WebSphere Application Server
Network Deployment V6.0.2, providing service location transparency between
Service Consumers and Service Providers within the enterprise. With the
Network Deployment offering, you can implement a scalable clustering of
multiple WebSphere Application Server servers.
A local DB2 Universal Database database is used to store the SDO repository.
The WebSphere Partner Gateway acts as the Exposed ESB Gateway node
providing a standard, consistent interface for the internal processes to access
external processes. An Exposed ESB Gateway minimizes the disruption caused
by changes in the external partner infrastructure.
In the Directory and Security services node, the service integration bus within
WebSphere Application Server Network Deployment V6.0.2 is configured to
secure all transactions to the external Partner Zone to use WS-Security integrity
and confidentiality.
The IBM HTTP Server V6 acts as an Adapter Connector by providing protocol
transformation to SOAP/HTTPS thus delivering transport level security between
the enterprise and the partner organizations.
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
<Service Provider>
<Service Provider>
App Server/
Services
App Server/
Services
<Service Consumer>
IBM HTTP
Server V6
Microsoft .NET
WebSphere
Partner
Gateway V6.0
• Service Integration Bus &
WebSphere Administration
(part of WebSphere
Application Server V6.0.2)
• DB2 Universal Database
WebSphere
Application
Server V6.0.2
<Service Provider>
Internet
App Server/
Services
<Service Provider>
WebSphere
Application
Server V6.0.2
CICS
Transaction
Server V3.1
WebSphere
Application
Server V6.0.2
Directory
& Security
Services
• Service Integration Bus &
WebSphere Administration
(part of WebSphere
Application Server V6.0.2)
• DB2 Universal Database
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.
