Chapter 14 Generating Other Models from a BPM


Generating an executable BPM from a collaborative BPM

You can wish to generate an executable BPM from a collaborative BPM, in order to focus on the implementation of one side of the collaboration you have defined in the collaborative BPM.

The following transformations are executed when you generate an executable BPM from a collaborative BPM. Besides, the transformations from an analysis to an executable BPM (described in the previous section) are also executed after the transformations from a collaborative to an executable BPM.

For more information on transformations from an analysis to an executable BPM, see section Generating an executable BPM from an analysis BPM.

Business Transaction

A Business Transaction represents a simple exchange of information between two partners. It is automatically replaced with an operation in the executable BPM. All operations are created under the same service provider and the same service interface.

The RequestDocument message format is considered as the input message, and the ResponseDocument message format (if any) is considered as the output document.

The Receipt and Acceptance Acknowledgements are lost.

Organization unit and Binary Collaboration

An organization unit in a collaborative BPM corresponds both to a partner and to a top-level process in an executable BPM. A Binary Collaboration stores the choreography of exchanges between the two partners.

Organization units are preserved without change to represent the partner in the executable BPM.

Binary Collaborations are converted into two top-level processes. The first one represents the collaboration implementation from the Responding Role point of view, and the second one represents the collaboration implementation from the Initiating point of view. Role associations are preserved. If you want to generate one process only, you must deselect an organization unit in the Selection page of the generation dialog box.

The choreography described inside the Binary Collaboration process is duplicated in each top-level process.

Each Business Transaction Activity is converted into a process implemented by the operation that matches the Business Transaction. The process receives messages from partners if the Business Transaction was associated with the organization unit that corresponds to the top-level process. Otherwise the process send messages to partners.

MultiParty Collaboration

The MultiParty Collaboration is not generated.

Only Binary Collaborations defined inside the MultiParty Collaboration are generated following the rules described in section Organization unit and Binary Collaboration.

 


Copyright (C) 2007. Sybase Inc. All rights reserved.