| ProfileLab-1109PhotosBlogLists |  Tools  Help |
|
|
June 18 A Problem about Modeling Process After completing a process model by Modeler, Business analyst will simulate the process.
The tool adds a simulation snapshot as a child element of the process in the project tree. A simulation saapshot is a record of the complete process model at the moment when you simulated the process. This record contains a copy of all the elements of your project Within the simulation snapshot, the tool also cretes two folders: Default-----Containing a set of local preferences for simulation attributes. Profile-----Each simulation snapshot contains an initial simulation profile which contains a copy of the process model at the time that you creted the simulation snapshot. You can customize process contained in this simulation profile, and you can create additional simulation profiles within the same simulation snapshot. Today, I follow these steps to complete the simulation of the process. There is a problem. For a local task, the flow is ok. The tool simulates the process correctly. But when the process includes a local process, the problem comes out. The flow is "stop in the local process". There is not outcome and the following task won't be carried out. I try the example which also includes a local process on the book. The result is suprising. Most of the flows is "stop in the local process". But when performing many times, some flow can go through the process. What lead the problem? -------------------------------------------------------------------------------------------------------------------
Davis Xu June 05 BPEL精炼之谈ActiveBPEL开源网站上对BPEL的解释可谓精练，比起读那又臭又长的《Business Process Execution Language for Web Services Version 1.1 》，心情都好很多，呵呵！
BPELBPEL is an XML language for describing business process behavior based on Web services. The BPEL notation includes flow control, variables, concurrent execution, input and output, transaction scoping/compensation, and error handling. A BPEL process describes a business process. Processes often invoke Web services to perform functional tasks. A process can be either abstract or executable. Abstract processes are similar to library APIs: they describe what the process can do and its inputs and outputs but do not describe how anything gets done. Abstract processes are useful for describing a business process to another party that wants to use the process. Executable processes do the "heavy lifting" - they contain all of the execution steps that represent a cohesive unit of work. A process consists of activities connected by links. (A process sometimes only contains one activity but that is usually a container for more activities.) The path taken through the activities and their links is determined by many things, including the values of variables and the evaluation of expressions. The starting points are called start activities; their BPEL is layered on top of other Web technologies such as WSDL 1.1, XML Schema 1.0, XPath 1.0, and WS Addressing. A Web search for "BPEL" will return a number of useful resources, including the specification document and numerous articles.
| |
|
|
