Chapter 2 Getting Started with the Business Process Model
When analysis is over you can generate your model into an executable BPM. The executable BPM corresponds to the implementation phase of business process modeling. It allows you to retrieve the analysis work and to refine it by specifying the implementation of atomic processes.
You can start the executable implementation using the SOA business process language.
SOA is a logical executable process language that allows you to orchestrate your processes without being linked to any platform or language, you can start implementing your processes in a BPM for SOA.
For more information, see the "Working with Service Oriented Architecture (SOA)" chapter.
You can choose to generate for different business languages like Sybase Integration Orchestrator, Sybase WorkSpace Business Process, BPEL4WS, or WS-BPEL. This generation enables several levels of abstraction so the analyst can regenerate the executable model several times; it also performs some, but not all, transformations to adapt the source model to the constraints of the selected executable process language.
The remaining transformations need to be applied manually by correcting the errors and warnings highlighted during check model.
You can then specify the implementation of atomic processes in order for them to be executed by the process language engine you have selected when you generated the executable BPM.
This phase occurs once your BPM is validated, optimized, and that you know exactly what to do to implement the process. Each step within the process corresponds to a single business activity that is implemented as an interaction with a Web service. For each given activity, you need to check whether you can reuse an existing distributed component. If yes, you import the corresponding WSDL, otherwise you create a component in the OOM, then import it.
For more information, see "Importing WSDL in an Executable BPM" in the "Building an Executable BPM: Working with Service Description Objects" chapter.
Once the Web services are imported, you may want to have a global and graphical view of them all. To do so you have to create a process service diagram and drag the retrieved service providers from the Browser to drop them in the process service diagram window. You can then design their dependencies if any using extended dependencies and publish a report on this diagram using the Report Creation Wizard from the Report menu.
For more information, see the Building a Process Service Diagram chapter.
You need to indicate the way to implement each atomic process of the executable BPM using Web service operations and messages. You can then work on data exchange and define the overall choreography of the model.
For more information, see the "Building an executable BPM: Managing Data and Choreography" chapter.
The technical user can generate the code of the executable BPM using generation targets that describe the business process in a way the required engine can process it. The executable BPM can help you reduce implementation time. It is a bridge to your choice of implementation environment, as it allows you to generate XML formats or code artifacts for specific process engines. You will not have to redefine the BPM again within the target process engine. The BPM can be executed using generation targets that describe the business process in a way the required engine can process it.
For more information, see the "Generating for a Process Language" chapter.
You know that your process will be executed using a process engine, but you want to start by designing the decomposition and choreography of tasks at a business level. You can start designing your model using the BPMN process language instead of the Analysis process language. This standardized notation allows you to describe the logic of your process execution and to bridge the gap to executable languages such as BPEL4WS or Sybase WorkSpace Business Process.
The remaining steps are globally the same as the ones when using the Analysis process language, except that you do not need to perform any transformations to adapt the BPMN model to the constraints of the selected executable process language.
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |