Maintaining integrity within an adaptive value chain involving cross enterprise interactions

• US 20060080117A1
• Filed: 10/12/2004
• Published: 04/13/2006
• Est. Priority Date: 10/12/2004
• Status: Active Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Carr, Derek W., Wesley, Ajamu A., Eacmen, Peter P., Pena, Ronny A.
• Application Number:
  US10/963,351
• Publication Number:
  US 20060080117A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

Abstract

The present invention is a method, system and apparatus for maintaining transactional integrity within an adaptive value chain involving cross enterprise interactions. In the present invention, transactional integrity can be maintained in a cross-enterprise business process management system by managing business transformation operations among cross-enterprise interactions to produce an adaptive value chain. At the same time, atomicity can be enforced among the business transformation operations and the cross-enterprise interactions.

Claims

1. A method for maintaining transactional integrity in a cross-enterprise business process management system, the method comprising the steps of:

managing business transformation operations among cross-enterprise interactions to produce an adaptive value chain; and

,

enforcing atomicity among said business transformation operations and said cross-enterprise interactions.

2. The method of claim 1, wherein said enforcing step comprises the steps of:

extending a business process described by said business process specification document to a business activity having each of a monitor, an activation service, a registration service and a coordination service to support business activity monitoring and transaction related protocols in order to enforce transactional semantics required to ensure business transformation operative integrity; and

,

extending a business transformation engine to support said transaction semantics to allow informed business transformation operatives to participate in atomic transaction protocols.

3. The method of claim 2, further comprising the step of further extending said business transformation engine to act as a parent scope for business activities within said adaptive value chain.

4. The method of claim 3, wherein said further extending step comprises the step of implementing a business transformation activity implementing a business agreement coordination protocol.

5. The method of claim 3, wherein said further extending step comprises the step of tunneling coordination protocol messages between parent and child scopes for said business process by defining a partner link with said monitor along with corresponding partner links to individual partner services participating in said business process.

6. The method of claim 1, wherein said managing step comprises the steps of:

deploying a partner link instance for each partner link specified in a business process specification document;

re-factoring said document to bind each said partner link to each said deployed partner link instance in lieu of a direct binding to a principal service;

adding an event handler to said business process specification document to handle a dynamic change to an endpoint reference to said principal service; and

,

registering each of said partner link instances to receive notification of a change to an endpoint reference to a principal service.

7. The method of claim 6, further comprising the steps of:

invoking said event handler;

changing an endpoint reference to a principal service bound to a deployed partner link instance;

notifying said deployed partner link instance that a change to said endpoint reference has occurred; and

,

modifying subsequent service calls to said principal service to reflect said changed endpoint reference.

8. A cross-enterprise business process management system configured for maintaining transactional integrity comprising:

a business process specification document processing engine configured to process business process specification documents, each of said documents describing a business process having a plurality of business protocols defined within said business process;

a deployment service coupled to said engine and programmed to generate and deploy service instances supporting corresponding ones of said business protocols defined in said business process;

a business transformation engine coupled to said business process specification document processing engine and configured to process transformation scripts for changing said business process by activating and deactivating selected ones of said business protocols in said business process according to registered event personas and business transformation operatives; and

,

an extension to said business transformation engine, said extension comprising a business activity configured to coordinate business transformations to maintain transactional integrity among said business protocols and said business transformations.

9. The system of claim 8, wherein said business activity implements a business agreement coordination protocol.

10. The system of claim 8, wherein said business activity comprises an aggregation of an activity monitor, an activation service, a registration service and a coordination service.

11. The system of claim 8, wherein said business process specification documents comprise business process execution language (BPEL) documents.

12. The system of claim 11, wherein said business process specification document processing engine comprises a business process execution language for Web services (BPEL4WS) run-time engine.

13. The system of claim 12, wherein said business process comprises a sequence of business activities embodied within corresponding Web services.

14. A machine readable storage having stored thereon a computer program for maintaining transactional integrity in a cross-enterprise business process management system, the computer program comprising a routine set of instructions which when executed by a machine cause the machine to perform the steps of:

managing business transformation operations among cross-enterprise interactions to produce an adaptive value chain; and

,

enforcing atomicity among said business transformation operations and said cross-enterprise interactions.

15. The machine readable storage of claim 14, wherein said enforcing step comprises the steps of:

extending a business process described by said business process specification document to a business activity having each of a monitor, an activation service, a registration service and a coordination service to support business activity monitoring and transaction related protocols in order to enforce transactional semantics required to ensure business transformation operative integrity; and

,

extending a business transformation engine to support said transaction semantics to allow informed business transformation operatives to participate in atomic transaction protocols.

16. The machine readable storage of claim 15, further comprising an additional set of instructions for causing the machine to further perform the step of further extending said business transformation engine to act as a parent scope for business activities within said adaptive value chain.

17. The machine readable storage of claim 16, wherein said further extending step comprises the step of implementing a business transformation activity implementing a business agreement coordination protocol.

18. The machine readable storage of claim 16, wherein said further extending step comprises the step of tunneling coordination protocol messages between parent and child scopes for said business process by defining a partner link with said monitor along with corresponding partner links to individual partner services participating in said business process.

19. The machine readable storage of claim 14, wherein said managing step comprises the steps of:

deploying a partner link instance for each partner link specified in a business process specification document;

re-factoring said document to bind each said partner link to each said deployed partner link instance in lieu of a direct binding to a principal service;

adding an event handler to said business process specification document to handle a dynamic change to an endpoint reference to said principal service; and

,

registering each of said partner link instances to receive notification of a change to an endpoint reference to a principal service.

20. The machine readable storage of claim 19, further comprising an additional set of instructions for causing the machine to further perform the steps of:

invoking said event handler;

changing an endpoint reference to a principal service bound to a deployed partner link instance;

notifying said deployed partner link instance that a change to said endpoint reference has occurred; and

,

modifying subsequent service calls to said principal service to reflect said changed endpoint reference.