The first time you sign into developerWorks, a profile is created for you. Select information in your profile (name, country/region, and company) is displayed to the public and will accompany any content you post. You may update your IBM account at any time.

All information submitted is secure.

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerworks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

All information submitted is secure.

My developerWorks:

My notifications:

Sign out

Select a language:

Implementing web services transactions in WebSphere Process Server V7

Learn how to implement a Web Services Atomic Transaction scenario with a business process and external web service

Rajiv Madassery (rajiv.madassery@in.ibm.com), Principal Software Engineer, IBM

Rajiv Madassery is a Principal Software Engineer at IBM and works for the WebSphere Process Server Level 2 Support Team. Rajiv came to IBM in 2003 and has worked with the WebSphere Business Integration Adapters Functional Verification Test team and WebSphere Application Server Level 2 Support team. Rajiv is a developerWorks Contributing Author in the WebSphere Process Server space.

Summary: This tutorial provides instructions to implement a transaction between an IBM® WebSphere® Process Server V7 business process and an external web service running on WebSphere Application Server V7. The tutorial will provide steps to be carried out in IBM WebSphere Integration Developer V7 while developing the business process module and the web service, followed by instructions to configure WebSphere Process Server and WebSphere Application Server to enable Web Services Atomic Transaction. The latter part demonstrates the transaction commit and rollback scenarios to complete the tutorial.

Date: 24 Nov 2010
Level: Intermediate
PDF: A4 and Letter (1043 KB | 29 pages)Get Adobe® Reader®

Activity: 28265 views
Comments:

Introduction

Web Services Atomic Transaction (WS-AT) support in WebSphere Application Server (hereafter called Application Server) enabled web services applications to participate in transactions. With this support, business process applications running in WebSphere Process Server (hereafter called Process Server) can participate in distributed transactions.

To learn more about the web services transaction support, see the Information Center.

In this tutorial

This tutorial provides an illustration of WS-AT based distributed transaction between a business process running on WebSphere Process Server and a Java™ API for XML web services (JAX-WS) based service, residing on an external WebSphere Application Server. The tutorial is follow-on to a previous article, Transactionally integrate Web services with BPEL processes in WebSphere Process Server. That article is intended for Version 6.0.2 of WebSphere Process Server. The focus of this article will be on WS-AT configuration in Version 7.0.

There are two applications developed in the tutorial, a business process application called “ABCBPEL”, which contains a business process and a web services import, and a web service application called “ABCService”, as shown in Figure 1. The business process component in ABCBPEL module invokes the web service in ABCService. ABCService receives a parameter from the business process and uses it as data to insert a row into the database. The business process also has a snippet component, which you can use to raise a fault and to demonstrate a global transaction rollback.

A sample Project Interchange file, WS-ATProjectInterchange.zip, is provided for you to download with this tutorial.

Figure 1. WS-AT context
WS-AT context

The tutorial is divided into the following sections:

Preparing the application development setup

Developing the Web Service application

Developing the business process application

Deploying the applications

Configuring the servers

Testing the transactional behavior

Prerequisites

You will need:

Previous development experience in WebSphere Integration Developer.
Knowledge of basic administration of WebSphere Process Server and WebSphere Application Server.

System requirements

Microsoft® Windows® XP Professional Desktop with at least 2 GB of RAM
IBM WebSphere Integration Developer V7.0.0.2 with WebSphere Process Server Test Environment V7.0.0.2, WebSphere Application Server V7.0.0.9
Database server, such as IBM DB2® Express

Duration

Approximately 1 to 2 hours

Comments