Browse Prior Art Database

Use of Web Services and Business Process in the Deployment Descriptors of Business Processes

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

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. Binding is typically done by assigning a port to a port type. It is suggested that this binding is extended by using Web Services or Business Processes for relating a port to a port type.

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

Page 1 of 3

Use of Web Services and Business Process in the Deployment Descriptors of Use of Web Services and Business Process in the Deployment Descriptors ofUse of Web Services and Business Process in the Deployment Descriptors of Use of Web Services and Business Process in the Deployment Descriptors of

Business Processes Business ProcessesBusiness Processes Business Processes

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. Binding is typically done by assigning a port to a port type. It is suggested that this binding is extended by using Web Services or Business Processes for relating a port to a port type.

    Suppose we have a simple business process of a book store that among other things orders books at a whole seller. This fragment of the business process would be modeled in BPEL as follows :

<process name="bookOrder">

<partnerLinks>

    <partnerLink name="wholeSeller" partnerLinkType="wholeSellerPT" myRole="buyer" partnerRole="seller"/> </partnerLinks>

<invoke name="order" partnerLink="wholeSeller" operation="order" inputVariable="order"/>

<receive name="confirmOrder" partnerLink="wholeSeller" operation="confirm" inputVariable="orderConfirmation"/>

</process>

    As shown the interaction between the buyer and seller is identified via the partnerLink named wholeSeller. In the first invoke activity the buyer orders something at the wholeseller. The wholeseller answers in the second activity. The associated deployment descriptor then defines which port implements the respective port types. The following example illustrates how that could look like:

<deploymentDescriptor name="bookOrderDeployment" process="bookOrder"> <link partnerLink="wholeSeller">

<role type="myRole">

<service name="http://www.bookSeller.com"/>

1

Page 2 of 3

</role> <role type="partnerRole">

             <service name="http://w...