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
Attention:
- 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. 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.
- Beginning with IBM® Business Process Manager Advanced Version 8, the SOAP/JMS API replaces the Business Process Choreographer JMS API. The Business Process Choreographer JMS API is deprecated. Use the JAX-WS-based API to implement new web service client applications.
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.