The DSB comes with some BPEL management API in order to be able to deploy BPEL processes and manage them. The current section provides all the information on how to use this feature.
Architecture
Really simple view:
- The BPEL runtime is provided by the JBI BPEL component
- The WS API is provided by the kernel
- The WS implementation takes the BPEL file(s), calls a SA generator and deploy the SA on the BPEL component
- Note that for now the BPEL generator is a dedicated JBI component which is called by the kernel. This is manly due to some classloader problems since the DSB and the BPEL stuff do not use the same libraries versions.
Deploy BPEL process
DSB Web service
The DSB provides a Web service API to deploy and manage your BPEL process. The deployment operation takes the BPEL file and its associated resources (WSDL and/or XSD) as input parameters (attachments). The DSB web service, analyze the input data and deploy the BPEL process on the BPEL component is possible.
The Web service endpoint is available at http://HOST:7600/petals/ws/BPELDeployer and provides the deploy operation which takes BPEL and associated resources as input data.For more information, you can check the BPEL deployer API modules available in the dsb-kernel-bpelwsapi module.
Java Client
A Java client based on Apache CXF is available to deploy and manage your BPEL processes. It uses the previous mentioned DSB Web service and works like this:
Where the address is the DSB node management root URL (generally http://HOST:7600/petals/ws/).
The Java client is bundled in the dsb-kernel-bpelwsclient library, you can get it as Maven dependency:
Download
The BPEL component is available at
- http://maven.petalslink.com/public-snapshot/org/petalslink/research/petals/petals-se-bpel/1.1-SNAPSHOT/petals-se-bpel-1.1-SNAPSHOT.zip
- Or is directly shipped within the DSB distribution under the artifacts/components folder. In this case, it is automatically started by the DSB when needed.