BPEL

SecRMLoan SecRMLoan

This example is a combination of Secure and Reliable Loan Flow examples.

The calls to the asynchronous services must be done via WS-RM protocol.

The calls to partners must be encrypted and signed using the rules:

The caller must supply a signed and encrypted SOAP message.
The process must reply from a separate HTTP connection to the endpoint designated by the caller's ReplyTo WSA header.
The process' reply must contain a signed and encrypted SOAP message.
X.509 certificates must be used to sign the message.
The session keys can be tripple-des or AES (128, 192 or 256 bit quality).
A Session key must be encrypted with the partner's RSA public key.
The test certificates from MS WSE 2.0 toolkit can be used.

To build the example follow the steps bellow:

This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.
This example depends from the SecLoan and the RMLoan example. Make sure there are initial loads for these examples.
The example script creates services for Credit Rating, United Loan and Star Loan.
The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.
On the initial load the BPEL Secure and Reliable Loan Flow process will be deployed.

To run the example follow the steps bellow:

Login into the BPEL UI via http://host:port/BPELGUI.
To enable debugging for the process with name 'SecRMLoanFlow' check the Debug checkbox in the listing. This will cause all instances of the process to run in single-step mode, pausing at each send or receive of a message. The debug console allows interacting with instances in this mode.
To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.