Patterns: Extended Enterprise SOA and Web Services

Chapter 15. Exposed Serial Process runtime pattern: SOA profile 471

9. Save the WarehouseBP.bpel file. There should be no errors in the

WarehouseBusinessProcess project (although there will be errors in the

WarehouseBusinessProcessEJB project which we will fix next).

15.3.6 Generate deployment code and export the process

To generate deployment code for the new business process, perform the

following:

1. Right click WarehouseBP.bpel and select Enterprise Services → Generate

Deploy Code.

2. In the Generate BPEL Deploy Code window, click OK to generate the

deployment code.

3. There should be no errors in the Tasks view.

You can optionally export the deployed business process to an EAR file if you

intend to deploy it to WebSphere Business Integration Server Foundation. To

export the WarehouseBusinessProcess enterprise application:

1. Click File → Export.

2. In the Export wizard, highlight EAR file and click Next.

3. In the EAR project pull-down menu, select

WarehouseBusinessProcessEAR. Click Browse and locate a directory to

where you want to store the enterprise application. Click Save. The enterprise

application is called WarehouseBusinessProcess.ear by default.

4. Click Finish to generate WarehouseBusinessProcessEAR.ear.

15.4 Runtime guidelines

This section describes how to test and deploy the Warehouse business process

built in 15.3, “Development guidelines” on page 465.

It contains the following sections:

򐂰 Configuring the ESB

򐂰 Configuring the Exposed ESB Gateway

򐂰 Testing the business process with ITSO Good

As shown in Figure 15-4 on page 472, the ITSO Good application remains split

into two applications: one with the Warehouse running as a WS-BPEL business

process in WebSphere Business Integration Server Foundation V5.1, and the

other with Retailer, SCMSampleUI, and LoggingFacility running in WebSphere

Application Server Network Deployment V6.

472 Patterns: Extended Enterprise SOA and Web Services

Figure 15-4 Runtime deployment topology

The Warehouse application deployed in WebSphere Business Integration Server

Foundation V5.1 is invoked by the Retailer application running in WebSphere

Application Server Network Deployment V6.0.2. The Warehouse application then

invoke the Manufacturer or Manufacturers if required with the ESB and the Web

services gateway. The Web services gateway includes a mediation service which

checks the incoming message from the Warehouse and identifies the relevant

Manufacturers to be called. It also then aggregates the response messages from

the various Manufacturers and creates a single message which is returned to the

Warehouse for logging.

15.4.1 Configuring the ESB

This section describes how to configure the ESB implemented by the ESBBus

service integration bus.

You need to perform the following tasks:

򐂰 Define an outbound service to point to the Manufacturer Gateway service.

򐂰 Reconfigure the Manufacturer inbound service to point to the Manufacturer

outbound service.

Manufacturer C

CICS

Manufacturer B

.NET

WebSphere Application Server Network Deployment

WebSphere Application

Server

Manufacturer A

WebSphere Business Integration

Server Foundation

ITSO Good

Web

Services

Gateway

Enterprise

Service

Bus

Mediation

Service

Logging

Facility

Warehouse

Retailer

SCMSampleUI

Chapter 15. Exposed Serial Process runtime pattern: SOA profile 473

Defining a Manufacturer outbound service

Perform the following in the ITSOGoodProfile server administrative console,

where the ITSOGood enterprise application is installed:

1. Click Service integration → Buses → ESBBus → Outbound Services.

2. Define a new outbound service called

ManufacturerGatewayOutboundService as follows:

a. Click New.

b. In the WSDL location field enter the location of the Manufacturer Gateway

service WSDL file, which should be

http://appsrv1a.itso.ral.ibm.com/wsdl/ExposedESBGatewayBus.Manufa

cturerGatewayServiceService.wsdl

c. Click Next, Next, and Next.

d. Set the Outbound service name to ManufacturerGatewayOutboundService,

the Service destination name to

ManufacturerGatewayOutboundServiceDestination, and the Port

destination name to ManufacturerGatewayOutboundPort.

e. Click Next, then Finish.

3. Save your changes.

Reconfiguring the Manufacturer inbound service

Reconfigure the Manufacturer inbound service so that it points to the destination

used by the Manufacturer outbound service. Perform the following:

1. Click Service integration → Buses → ESBBus → Inbound Services.

2. Click ManufacturerInboundService.

3. Set the Service destination name to

ManufacturerGatewayOutboundServiceDestination and click OK.

4. Save your changes.

15.4.2 Configuring the Exposed ESB Gateway

This section describes how to configure the Exposed ESB Gateway which is

implemented by the ExposedESBGateway Web services gateway.

You need to perform the following tasks:

򐂰 Install the mediation and define the request and response mediations.

򐂰 Assign the mediations to the Web services gateway service.