# US 2008/0189534 A1 · Apparatus and method for policy-driven business process exception handling

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2008/0189534 A1
- Document ID: US20080189534A1
- Status: Published application
- Kind: A1
- Application number: 12/061,089
- Filed: 2008-04-02
- Published: 2008-08-07
- Earliest claimed: 2004-05-26
- Assignees: International Business Machines Corporation
- Inventors: Jun-Jang JENG; Hui Lei; Liangzhao Zeng; Hung-yang Chang; Santhosh Kumaran; Jen-Yao Chung
- Web page: https://patentgrep.com/patent/US20080189534A1

## CPC

- G06Q 10/067: Enterprise or organisation modelling
- G06Q 10/06375: {Prediction of business process outcome or impact based on a proposed change}
- G06Q 10/06395: {Quality analysis or management}
- G06Q 10/0674: {using process simulation}
- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A model-driven and QoS-aware infrastructure facilitates the scalable composition of Web services in highly dynamic environments. An exception management framework supports two modes of exception management for business processes, providing a novel policy-driven approach to exception management implemented in the system infrastructure. Exception management is implemented in the system infrastructure, with exception handling policies supplied by individual business processes. Using the exception management framework, developers define exception policies in a declarative manner. Before a business process is executed, the service composition middleware integrates the exception policies with normal business logic to generate a complete process schema. This policy driven-approach can significantly reduce the development time of business processes through its separation of the development of the business logic and the exception handling policies.

## Claims

### Claim 1

A system for executing business process and handling runtime exceptions, comprising:
an aggregator that is able to integrate normal business logic with exception handling knowledge to generated extended business process definition; and
a business process engine that is able to execute business process definitions that contains knowledge on runtime exception handling.

### Claim 2 (depends on 1)

The system in claim 1, further comprising an exception handling policy repository that contains exception handling policies.

### Claim 3 (depends on 2)

The system in claim 2, wherein said exception handling policies includes said runtime exception specifications and exception handling action specifications

### Claim 4 (depends on 2)

The system in claim 2, wherein said business process engine can understand runtime exception specifications, detect runtime exceptions and execute exception handling actions.

### Claim 5

A method for executing business processes and handling runtime exceptions, comprising the steps of:
specifying exception handling knowledge from normal business process logic;
integrating normal business logic with exception handling knowledge to generate extended business process definitions;
executing business process definition that contains runtime exception handling knowledge;
detecting runtime exceptions; and
executing exception handling actions.

### Claim 6 (depends on 5)

The method in claim 5, further comprising the step of defining exception specification.

### Claim 7 (depends on 5)

The method in claim 5, further comprising the step of defining exception handling knowledge as exception handling policies.

### Claim 8 (depends on 5)

The method in claim 5, further comprising the step of checking the compatibility between the exception handling policies and normal business logic.

### Claim 9 (depends on 5)

The method in claim 5, further comprising the step of checking the conflicts among the exception handling policies.
