![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
Before you start
WebSphere® Business Integration Server Foundation Version 5.0 introduced formal support for the notion of a business process implemented as a collection of services, together with a scripting language defining the overall stateful execution context within which one or more of these services will be invoked. This capability, referred to as Business Process Choreographer, includes a runtime execution environment within which the BPEL-based process definition executes.
WebSphere Application Server (Application Server) Version 6.0 Platform Messaging introduces explicit support for the implementation of the Enterprise Services Bus architectural design pattern. Implicit in this pattern is the notion of a multi-channel conduit facilitating the invocation of service providers by service requestors. Adoption of the ESB pattern leads to increased flexibility and manageability of a Service-Oriented Architecture (SOA) by decoupling the relationship between service requestor and provider, and providing a single administrative point of control for distributed service invocations. The runtime infrastructure deployed upon Application Server Version 6.0 Platform Messaging is often referred to as the Services Integration Bus (SIBus). In this tutorial we shall use the terms Platform Messaging and SIBus interchangeably.
Business Process Choreography and SIBus are complementary technologies, whose combined usage provides enterprise-class qualities of service to the powerful process composition capabilities provided by Business Process Chorographer.
The first part of this two-part tutorial presented detailed instructions illustrating the implementation of a Web service with multiple operations. In this second installment we show how the service can be deployed into a SIBus-based infrastructure within Application Server Version 6.0. We then develop a business process in WebSphere Studio Application Developer-Integration Edition Version 5.1., which manages the invocation of multiple service invocations using the Application Server Version 6.0 SIBus instance.
In the final section of the tutorial we show how the business process WSDL interface definition can be used to deploy the process as an SIBus-managed service. A generated client application is then used to invoke the business process via a call to the interface exposed by the SIBus.
At the end of this two-part tutorial we will have built a simple PurchaseTickets business process. This process will encapsulate the choreographed invocation of four Web service operations:
- GetEventID
- CheckTicketAvailability
- ProcessPayment,
- ReserveTickets
Figure 1. High level scenario overview
For convenience, we subdivide the overall development effort into a number of incremental sub-tasks. In this installment we provide a detailed walkthrough of the following subtasks :
- Implementation of PurchaseTickets Business Process: In this section we move to the WBI-Server Foundation development environment WebSphere Studio Application Developer-Integration Edition. We use provided tooling to develop the PurchaseTickets business process. Upon completion, the process is deployed into an integrated test server instance and executed using the supplied Business Process Client tooling.
- Development of PurchaseTickets Business Process Client: In this final section we show how a BPEL process deployed within WebSphere Business Integration Server Foundation Version 5.1.1 can be consumed by a service invocation from a Application Server Version 6.0 SIBus client. The PurchaseTickets business process is configured as an outbound service to the bus. We then generate an unmanaged client from the WSDL describing a corresponding inbound service and execute from within Rational® Application Developer.
The following technologies and products are used and discussed in this tutorial:
- IBM HTTP Server Version 6.0
- WebSphere Business Integration Server Foundation Version 5.1.1
- WebSphere Application Server Version 6.0
- Rational Application Developer Version 6.0
- WebSphere Studio Application Developer-Integration Edition Version 5.1.1
We assume that the Business Process Container within WebSphere Business Integration Server Foundation is configured and operational. A detailed description of the steps required to perform this configuration is outside the scope of this tutorial.
This tutorial was developed under the auspices of the IBM On Demand Operating Environment Integration Services and Application Services Focus Teams based in Hursley, England. The author gratefully acknowledges discussion and recommendations from Focus Team colleagues that have helped to refine the content of this tutorial.
Special Thanks to Fintan Mcelroy for his diligent review of this document.
Table of contents
Next steps from IBM
Tags
Use the slider bar to see more or fewer tags.
Popular tags shows the top tags for this particular content zone (for example, Java technology, Linux, WebSphere).
My tags shows your tags for this particular content zone (for example, Java technology, Linux, WebSphere).
Popular tutorial tags |
My tutorial tagsSkip to tags list
Popular tutorial tags |
My tutorial tags
