Browse Prior Art Database

Method for Building Extensible Business Process Execution Language Workflows Without Changing Existing Code

IP.com Disclosure Number: IPCOM000188751D
Original Publication Date: 2009-Oct-21
Included in the Prior Art Database: 2009-Oct-21
Document File: 2 page(s) / 31K

Publishing Venue

IBM

Abstract

Method for building Business Process Execution Language (BPEL) workflows which can be extended without changing existing code.

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 2

Method for Building Extensible Business Process Execution Language Workflows Without Changing Existing Code

Disclosed method introduces extension points in Business Process Execution Language (BPEL) workflows with the help of a set of sub-workflows which implement or adapt a common web service interface. Content and context based assertions in dynamic service mediation are used as conditions for invoking sub-workflows from the existing BPEL workflow. BPEL workflows built using this method allow new endpoints and new conditions to be added to the existing BPEL workflow without changing the existing workflow or existing sub-workflow. The new endpoints with new sub-workflows execute new behavior thus extending the existing BPEL workflow while the changes to the existing workflow are only limited to the existing assertions. In contrast, known solutions require code changes to the existing BPEL workflow and/or to the existing services.

The steps are explained through an example in Fig 1 which shows an existing BPEL workflow where step X2, step X3 require frequent changes.

Step 1: Extract step X2, step X3 and replace with a sub-workflow web service invocation step X. Create sub-workflows for other behavior variations with different end-points which implement or adapt the same interface. Store the end-points in a database as shown in Fig 2 as sub-workflows: 1 and 2.

Step 2, Add assertions to each sub-workflow endpoint to describe the capabilities of the endpoint. For example in Fig 2, Endpoint 1 has a CreditScoreAssertion with two properties: MinC...