Skip to end of metadata
Go to start of metadata

Although the choreography diagram (and underling model) now shows how messages are exchanged by participants in the choreography, these exchanges have not been defined in an SOA context, based on service interfaces. Therefore we also need to define (within the model) how these message exchanges are grouped into message exchange patterns (MEP) on interfaces associated with the participants.

Although this can be achieved by adding Interface and Operation components within the model, and establishing the appropriate associations from the participants to the interfaces, there is a short cut that will derive this information from the interactions in the model.

However before invoking this utility, we have one final step that needs to be done. In the preceding sections you have seen how to create messages and exchange them between participants as part of a Choreography Task. Although this is adequate information from a message passing perspective, as it defines a reference to the specific message schema that is used, it does not indicate whether the message exchange represents a fault associated with a preceding request.

Therefore it is necessary to distinguish whether a particular message type is actually a fault (or error), to enable the service interface derivation to correctly distinguish between normal and fault responses in a service operation.

For each message type that needs to be highlighted as a fault, we need to create an Error component that references the same item definition. This Error component will essentially define the fault code for the fault, which will be used when constructing the RPC operation signature.

Select the Data Items tab, from the Properties associated with the diagram canvas, and expand the Error List:

Using the 'Add' button, create a new entry and configure its details to reference the required item definition (representing the message schema) and error code:

Once all of the required Error components have been created and configured, then select the "Savara->BPMN2->Add Service Interfaces" menu item, associated with the BPMN2 choreography file, to create the appropriate interfaces and establish the necessary relationships.

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.