You can generate an orchestration BPM from another orchestration BPM in order to execute your BPM in a specific application or to use a language standard format. Most of the time you will perform the following types of generation:
The following transformations are performed when you generate a Sybase WorkSpace Business Process BPM from an orchestration BPM (SOA or any of the BPEL languages):
Operation - Each language can restrict the type of operations that can be attached to a process. In Sybase WorkSpace Business Process, the following operation types are supported:
Top-level process - In Sybase WorkSpace Business Process, the top-level process is not supported. The flow chart is moved to the top-level diagram and must contain at least a start, a process and an end. In case of multiple top-level processes, these are all associated with the same start and end.
Package - In Sybase WorkSpace Business Process, packages are not supported, as the model can contain only one process.
Additional transformations - The following additional transformations are performed from a BPEL BPM to a Sybase WorkSpace Business Process BPM:
|
BPEL |
WorkSpace Business Process |
|---|---|
|
Flow with <<link>> stereotype. |
Not supported. |
|
Single process with multiple output flows. |
Split between the single process and the multiple output flows. |
|
Single process with multiple input flows. |
Join between the single process and the multiple input flows. |
|
Start with multiple output flows. |
Choice between the start and the multiple output flows. |
|
End with multiple input flows. |
Join between the end and the multiple input flows. |
|
"Receive request and reply" action type for operation. |
"Receive request" action type for operation. |
|
Switch decision. |
SingleRule decision with "If-Then-Else" expression. |
|
Event handler (flow chart of processes to handle an event). |
Composite process (containing the flow chart) with appropriate event handler stereotype. |