Browse Prior Art Database

Binding Time of Deployment Descriptors

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

Publishing Venue

IBM

Abstract

Workflow-based applications consists of a process model and a set of port types. When such an application is deployed into an appropriate environment, a deployment descriptor is used to specify which ports should be used when carrying out a process instance. When a new process instance is created, the workflow management system retrieves the deployment descriptor and fixes the actual ports to be used for the individual port types; that means the deployment descriptor is bound at process instance creation time. As a result, running process instances are not affected by port changes reflected in the deployment descriptor. This behavior may be too restrictive, in particular if processes are long-running. It is proposed to add the capability of specifying the binding time to the deployment descriptor .

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

Page 1 of 2

Binding Time of Deployment Descriptors

Workflow-based applications consists of a process model and a set of port types . When such an application is deployed into an appropriate environment, a deployment descriptor is used to specify which ports should be used when carrying out a process instance. When a new process instance is created, the workflow management system retrieves the deployment descriptor and fixes the actual ports to be used for the individual port types; that means the deployment descriptor is bound at process instance creation time. As a result, running process instances are not affected by port changes reflected in the deployment descriptor . This behavior may be too restricted, in particular if processes are long-running. It is proposed to add the capability of specifying the binding time.to the deployment descriptor

    Suppose we have a simple process consisting of three activities that invoke Web Services. Using a shortened version of the Business Process Execution Language for Web Services, an upcoming OASIS standard, the definition of the process would look like the following:

<process name="myProcess>

<sequence>

<invoke name="A" portType="A" operation="oA"/>

<scope name="myScope">

<sequence>

                 <invoke name="B" portType="B" operation="oB"/> <invoke name="C" portType="C" operation="oC"/> </sequence>
</scope>
</sequence>
</process>

An appropriate deployment descriptor could then look like the following :

<deploymentDescriptor process="myProcess>

    <assign portType="A" port="http://www.porta.com"/> <assign portType="B" port="http://www.portb.com"/> <assign portType="C" port="http://www.portc.com"/> </deploymentDescriptor>

    In this case, the workflow management would fix port type A to http://www.porta.com, port type B to http://www.portb.com, and port type C to http://www.portc.com when a particular process instance...