Developing Web services API client applications for BPEL processes and human tasks

You can develop client applications that access BPEL process applications and human task applications through the Business Process Choreographer Web services APIs. The client application development process consists of a number of mandatory and optional steps, including generating a Web service proxy and adding security and transaction policies to the client application.

About this task

Beginning with WebSphere® Process Server Version 7, the JAX-WS-based Web services API replaces the JAX-RPC-based Business Process Choreographer Web services API in WebSphere Process Server Version 6 (first published in release 6.0.2). The JAX-RPC-based Business Process Choreographer Web services API is deprecated. You should implement new Web service client applications using the JAX-WS-based API.

Note: The Business Process Choreographer Java™ Message Service (JMS) API can still use the WSDL and XML Schema definitions for WebSphere Process Server Version 6.

You can develop client applications in any Web services client environment. The following steps provide an overview of the actions you need to take to develop such an application.

Procedure

Decide which Web services API your client application needs to use: the Business Flow Manager API, Human Task Manager API, or both.
Export the necessary files from the Process Server environment.
In your client application development environment, generate a Web service proxy using the exported artifacts.
Develop the code for your client application.
Add any necessary security or transaction policies to your client application.