Patterns: Extended Enterprise SOA and Web Services

Chapter 14. Exposed Serial Process runtime pattern: generic profile 425

This Product mapping uses WebSphere Application Server V6.0.2 to host the

Application Services in the Enterprise Secure Zone.

An application service invokes the automated process instance implemented by

the Process Manager node using the Web Services Invocation Framework

(WSIF). The Exposed Process Manager implemented using WebSphere

Business Integration Server Foundation V5.1 invokes the services provided by

the external partner application service.

The Rules Directory node implemented using WebSphere Business Integration

Server Foundation V5.1 identifies which external partner organization application

service to invoke.

In the Directory and Security services node, the service integration bus within

WebSphere Application Server Network Deployment V6.0.2 is configured 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.

14.3 Development guidelines

This section describes how to implement a serial process (WS-BPEL flow) using

Process Choreographer in WebSphere Studio Application Developer Integration

Edition.

14.3.1 Scenario implementation: Serial process interaction

We use the sample scenario implemented in Chapter 10, “Exposed Direct

Connection runtime pattern: generic profile” on page 157 as the starting point for

this chapter. We replace the Warehouse Web module with a WS-BPEL process.

None of the other applications or modules require any code change.

We use the Process Choreographer tool in WebSphere Studio Application

Developer Integration Edition to create and generate deployment code for a

business process.

Note: This section requires the use of WebSphere Studio Application

Developer Integration Edition V5.1.1 plus Cumulative Fix 010 or higher

installed.

426 Patterns: Extended Enterprise SOA and Web Services

As a result of the limitations in the Business Process Engine (BPE) and

WebSphere Studio Application Developer Integration Edition, the WSDL files

provided with the WS-I sample application do not work. Therefore, we create

Web services clients for Manufacturer services using the WS-I sample WSDL

and this service invokes the business process. Our Warehouse business process

is not be exposed directly to the Retailer application.

Because there are no WS-Security capabilities in Process Choreographer or

WebSphere Business Integration Server Foundation, we invoke the Manufacturer

services through Web services gateway, which is responsible for securing the

communication to the Manufacturer.

The scenario implementation is shown in Figure 14-3.

Figure 14-3 Scenario implementation for the Exposed Serial Process

The following components are developed in this chapter and are shown in

Figure 14-3:

򐂰 Warehouse Service

This component acts as an endpoint for the Retailer application and other

clients invoking the Warehouse application. In our scenario, this component is

implemented as a J2EE Web module and exposed as a HTTP/SOAP Web

service.

򐂰 Warehouse Business Process

Warehouse

SOAP/HTTP

Java

EJB

Warehouse Business Process

Java

Java

Java

Logging Facility

Proxy

Manufacturer

Proxy

Manufacturer

Manufacturer

Manufacturer

Warehouse

Service

Java

SOAP/HTTP

Retailer

Warehouse Business Process

Proxy (WSIF)

SOAP/HTTP

Logging Facility

Manufacturer

Service Client

Logging Facility

Service Client

Chapter 14. Exposed Serial Process runtime pattern: generic profile 427

This WS-BPEL process is a short running process (micro flow) and contains

the Warehouse application business logic.

򐂰 Warehouse Business Process Proxy

This Web Services Invocation Framework (WSIF) Java class is the proxy

used by the WarehouseService to invoke the Warehouse Business Process.

򐂰 Manufacturer Proxy and Logging Facility Proxy

These are Java classes exposed as services and are invoked from the

Warehouse Business Process when calling the Manufacturer and

LoggingFacility.

򐂰 ManufacturerGW Service Client and Logging Facility Service Client

Web services client code is generated from the WSDLs supplied from the

three Manufacturer’s and LoggingFacility. In our scenario, these Web services

clients are created in Java projects.

14.3.2 Creating the basic infrastructure

Before beginning the development guidelines, the basic infrastructure must be

configured before you can begin building the Warehouse business process.

This scenario is based on the infrastructure built in Chapter 10, “Exposed Direct

Connection runtime pattern: generic profile” on page 157. If you have already

built this infrastructure, you can reuse it here.

This section describes how to build a Warehouse business process to fit into the

topology shown in Figure 14-4 on page 428.