Browse Prior Art Database

Setting Business Process Variables Via Deployment Descriptor

IP.com Disclosure Number: IPCOM000031800D
Original Publication Date: 2004-Oct-11
Included in the Prior Art Database: 2004-Oct-11
Document File: 3 page(s) / 47K

Publishing Venue

IBM

Abstract

Workflow-based applications consists of a process model consisting of a set of activities and a set of Web Services, where the business process is typically modeled using Business Process Execution Language (BPEL) and the Web Services are modeled as port types using the Web Services Description Language (WSDL). When such an application is deployed into an appropriate environment, a deployment descriptor (typically using a proprietary language) specifies which ports should be used when carrying out a process instance; that means the deployment descriptor binds the individual port types to ports which provide an implementation of the port type. It is suggested that the deployment descriptor is extended to provide binding for standard BPEL variables providing for increased flexibility of deployment for workflow-based applications.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 3

Setting Business Process Variables Via Deployment Descriptor Setting Business Process Variables Via Deployment DescriptorSetting Business Process Variables Via Deployment Descriptor Setting Business Process Variables Via Deployment Descriptor

Workflow-based applications consists of a process model consisting of a set of activities and a set of Web Services where the business process is typically modeled using Business Process Execution Language (BPEL) and the Web Services are modeled as port types using the Web Services Description Language (WSDL). When such an application is deployed into an appropriate environment, a deployment descriptor (typically using a proprietary language) specifies which ports should be used when carrying out a process instance; that means the deployment descriptor binds the individual port types to ports which provide an implementation of the port type. Conceptually the deployment descriptor assigns a value to a variable; in the cases of port types the individual port types are the variables and the corresponding ports are the values that are assigned to the port type variable . It is suggested that the deployment descriptor is used as a means to assign values to BPEL variables.

    Suppose we have the simple loan process as shown in the following figure . After the credit information has been collected, a check is being made to the loan amount that has been requested. If the amount exceeds $ 10.000, the loan must be approved by a financial officer which is done in the Request Approval activity.Otherwise (indicated via the 0 attached to the link from the Collect Credit Information to the Assess Risk activity.

    The first three activities, Collect Credit Information, AssessRiskj, and RequestApproval would then be defined via BPEL as follows (only showing the relevant information):

<links>

<link name="CollectCreditInformation2AssessRisk"/> <link name="CollectCreditInformation2RequestApproval"/>

</links>

<invoke name="CollectCreditInformation">

<source linkName="CollectCreditInformation2AssessRisk" transitionCondition="getVariable(request,amount) >

1

[This page contains 1 picture or other non-text object]

Page 2 of 3

10000"/>

10000"/>

<source linkName="CollectCreditInformation2RequestApproval" transitionCondition="getVariable(request,amount) LE

</invoke>

<invoke name="AssessRisk">

    <targ...