Chapter 13. Exposed Router runtime pattern: SOA profile 397
As shown in Figure 13-5 on page 396, the SOA profile is implemented by
introducing the ESB and the Exposed ESB Gateway component. The ESB
integrates all the service calls at an enterprise level and provides the mediation
logic built on business agreements and terms. Any interaction with an extended
enterprise is managed through the Exposed ESB Gateway component, which we
have implemented using WebSphere Partner Gateway V6.
13.4 Runtime guidelines
This section describes how to configure the runtime aspects of this scenario. It
uses the basic infrastructure of Chapter 11, “Exposed Direct Connection runtime
pattern: SOA profile” on page 237 as a starting point. In this section, you add a
WebSphere Partner Gateway configuration to act as the Exposed ESB Gateway,
and define new outbound services in the ESB to point to WebSphere Partner
Gateway configuration for each Manufacturer call.
13.4.1 Solution topology
As in the previous chapters, to represent the complete business scenario the
sample application is divided into four subapplications:
ITSOGood contains the SCMSampleUI, Retailer, Warehouse, and
Manufacturer, ManufacturerB, ManufacturerC are three individual services,
each packaged separately, and deployed to three different enterprises.
Calls to the three Manufacturer enterprise applications are sent to WebSphere
Partner Gateway V6. This application uses a SOAP pass-through to send SOAP
messages to an HTTP Server, which adds HTTP/S security to the SOAP
message and forwards the request on to the relevant Manufacturer. This is
shown in Figure 13-6 on page 398.
Note: The link between the ESB and Exposed ESB Gateway will be
configured using instructions in the Runtime guidelines section.