Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Explicit Deletion of BPEL Variables

IP.com Disclosure Number: IPCOM000030082D
Original Publication Date: 2004-Jul-27
Included in the Prior Art Database: 2004-Jul-27
Document File: 2 page(s) / 6K

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 for the definition of variables. These variables are used in receiving data from invoked Web Services as well as sending data to Web Services. A workflow management system typically makes those variables persistent; that means it writes the content of variables to a persistent storage when it has completed a navigation step. As persisting variables is an expensive operation, it is desirable to avoid persisting variables that are only no longer needed. It is suggested that additional information is provided for BPEL variables, which allows the workflow management system to determine when a particular BPEL variable is no longer needed.

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

Page 1 of 2

Explicit Deletion of BPEL Variables

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 for the definition of variables . These variables are used in receiving data from invoked Web Services as well as sending data to Web Services. Manipulation of the variables is via the <assign> activity. Variables are defined via the <variable> statement. The set of variables is enclosed in the <variables> element. Variables can either be of type WSDL messages or XML schema. The following code snippet defines a variable which holds, within an order process, the order number:

<variables>

<variable name="orderNumber type="xsd:integer"/>

</variables>

    A workflow management system typically writes the content of variables to some persistent store to be able for example to restart /continue navigation after some failure or after the process has been waiting for some user input /completion of some invoked application. As making variables persistent is an expensive operation it is desirable to avoid this as much as possible. In some cases, the workflow management system is able to detect when a variable is no longer needed . In many cases however, this is not possible at all and additional information needs to be provided by the process modeler. This additional information could conceptually be provided by two distinct mechanisms.

    The first mechanism adds information to activities indicating that after the activity has started or after the activity has completed, a specified variable is no longer needed. This is done by specifying a sub element <delete> wit...