This example illustrates a formal obligations (or interactions) verification using a service choreography specification (in the form of WS-CDL) and partners of the choregraphy implementation (in the form of WS-BPEL).

The example represents a solution to Test 1 where the partner (PoliceEnquiry) of a choreography did not have receive_requestenquiry as a first activity and caused a violation.  The solution moves the receive_requestenquiry activity to the first step.

To perform the verification:

1  In LTSA WS-Engineer switch to the Obligations tab 
2. Drag-and-drop the pito.bpel on to the tab page.
3. Under the role for BPEL select the POLICENQUIRY role.
4. Drag-and-drop the pitoenquiry.cdl on to the tab page.
5. Under the role for CDL select the POLICENQUIRY role.
6. Switch the property to use as "Partner".
7. Click Verify and note that a violation occurs at the receive_requestenquiry action.

No violations should occur.