BPEL
SecLoan SecLoan
LoanFlow process using WS-Security
Example
The example contains code for LoanFlow Using WS-Security.
The following are requirments to the caller and the process:
- The caller must supply a signed and encrypted SOAP message.
- 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.
- The 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.
- 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 LoanFlow Using WS-Security 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 'SecLoanFlow' 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.
| View the source | Action |
|---|---|
| 1. LoanFlowDemo.sql | Set the initial state |
| 2. CreditRating.vsp | Run |
| 3. LoanFlow.bpel | |
| 4. LoanFlow.sql | |
| 5. LoanFlow.wsdl | |
| 6. StarLoan.vsp | Run |
| 7. UnitedLoan.vsp | Run |
| 8. bpel.xml | |
| 9. desc.xml |
OpenLink Home
Technical Support