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: 28280 views
Comments:

Configuring the servers

Before running the application scenarios, additional configuration on the servers are required.

The web service application uses a data source to connect to the database. You will create a data source in the WebSphere Application Server.

Create a new data source named ABCDB, scoped to the Cell, as shown in Figure 29.

Figure 29. Data source properties
Ensure that the data source is XA enabled. For participating in the global transaction context, the data source is required to be XA enabled.
Verify that the data source properties are set in compliance with the data source connection properties (Figure 30) set in ABCService.java.

Figure 30. Datasource connection properties

If security is enabled at the application servers, additional configurations are required prior to running the applications:

It is required to import the Light-weight Third Party Authentication (LTPA) tokens from Process Server to Application Server. The procedures to export and import the LTPA tokens are explained in detail in the Information Center.
It is required to import the Secure Sockets Layer (SSL) certificates from Application Server and add it to the trust store in Process Server to avoid SSL handshake errors.