Browse Prior Art Database

Cross Process Instance Serialization

IP.com Disclosure Number: IPCOM000125655D
Original Publication Date: 2005-Jun-10
Included in the Prior Art Database: 2005-Jun-10
Document File: 1 page(s) / 4K

Publishing Venue

IBM

Abstract

Business Process Execution Language for Web Services (BPEL4WS) is an evolving OASIS standard for defining business processes that orchestrate the execution of Web Services. The language provides the notion of scopes that enclose a set of activities. Scopes, among many other properties support the notion of serializability. This is indicated via the attribute variableAccessSerializable. If set to "yes" it indicates that two (parallel, peer) scopes defined with this property need to be carried out one after the other if they access at least one common variable; that means the execution of the different scopes is serialized. It is suggested that the serialization of scopes is extended to scopes that are serialized for different process instances of the same process model.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 1

Cross Process Instance Serialization Cross Process Instance SerializationCross Process Instance Serialization Cross Process Instance Serialization

Business Process Execution Language for Web Services (BPEL4WS) is an evolving OASIS standard for defining business processes that orchestrate the execution of Web Services. The language provides the notion of scopes that enclose a set of activities. Scopes, among many other properties support the notion of serializability . This is indicated via the attribute variableAccessSerializable. If set to "yes" it indicates that two (parallel, peer) scopes defined with this property need to be carried out one after the other if they access at least one common variable; that means the execution of the different scopes is serialized . The purpose of serializing the execution of parallel scopes is to guarantee that the result of the operations on the commonly accessed (shared) variables is deterministic; that means when one scope carries out operations on the shared variables, it performs the complete set of operations needed to be carried out before the other scope continues .

    The mechanism can also be used to control the access to a resource on which the different scopes need to operate . In this case, the shared variable is just a kind of a lock. By using an appropriate assign operation that accesses the shared variable, the subsequent activities have exclusive access to the underlying resource. This behavior between different...