Executing a business process by a standard business process engine

• US 8,935,173 B2
• Filed: 10/16/2013
• Issued: 01/13/2015
• Est. Priority Date: 04/12/2011
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Breiter, Gerd, Kloppmann, Matthias, Spatzier, Thomas
• Primary Examiner(s): Singh, Gurkanwaljit
• Application Number:
  US14/055,613
• Publication Number:
  US 20140058788A1
• Time in Patent Office: 454 Days
• Field of Search: None
• US Class Current: 705/7.13
• CPC Class Codes: G06F 8/20 Software design
• 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/06316 Sequencing of tasks or work
• CPC Class Codes: G06Q 10/0633 Workflow analysis

Abstract

Executing a business process can include providing a context data object including a payload data structure for storing a payload data and automatically splitting an annotated context data object into one or more utility data objects. Responsive to creating a second utility data object, a pre-processing task can be injected into the business process, the pre-processing task using a copy of a first mapping to read data from the predefined data structure instance and to store the read data as payload data in the payload data structure of the first utility data object. Responsive to creating a third utility object, a post-processing task can be injected into the business process. The post-processing task can use a copy of the second mapping to write the payload data of the first utility data object to elements of a predefined data structure instance.

Claims

1. A computer-implemented method of executing a business process by a standard business process engine, comprising:

automatically splitting a context data object including a payload data structure, using a processor and upon the context data object being annotated with a first mapping, into a plurality of utility data objects including;

a first utility data object including the payload data structure;

a second utility data object including a copy of the first mapping; and

injecting a pre-processing task into the business process, wherein

the pre-processing task uses the copy of the first mapping to

read data from a predefined data structure instance and

store the read data as payload data in the payload data structure of the first utility data object.

2. The method of claim 1, wherein

the payload data conforms to a standard data object definition processable by the standard business process engine;

and

the standard data object definition does not include a specification of the predefined data structure instance.

3. The method of claim 1, wherein

each of the plurality of utility data objects conform to a standard data object definition,

the context data object is annotated with the first mapping and a second mapping,

the first mapping connects elements of the predefined data structure instance to elements of the payload data structure,

the second mapping connects elements of the payload data structure instance to elements of the predefined data structure, and

the context data object does not conform to the standard data object definition.

4. The method of claim 1, wherein

the predefined data structure instance is an instance of a schema.

5. The method of claim 1, wherein

the predefined data structure instance acts as I/O interface of a service, and

the predefined data structure is an instance of a schema processable by the service.

6. The method of claim 1, wherein

each of the plurality of utility data objects conform to a standard data object definition,

the payload data structure is an XML data structure, and

the standard data object definition is an XML schema.

7. The method of claim 1, wherein

the standard business process engine is a program operable to interpret and execute only business processes having been defined in BPMN and/or BPEL.

8. The method of claim 1, further comprising

deploying a business process definition to a runtime environment within which the business process is executed, wherein

the business process definition being a document comprising one or more task specifications each specifying a task to be executed by the standard business process engine upon executing the business process, and

the injecting the pre-processing task is executed during the deploying the business process definition.

9. The method of claim 8, wherein

the injecting the pre-processing task includes inserting an additional task specification into the business process definition.

10. The method of claim 8, wherein

the runtime environment is a service container.

11. A computer-implemented method of executing a business process by a standard business process engine, comprising:

automatically splitting a context data object including a payload data structure, using a processor and upon the context data object being annotated with a second mapping, into a plurality of utility data objects including;

a first utility data object including the payload data structure;

a third utility data object including a copy of the second mapping; and

injecting a post-processing task into the business process, wherein

the post-processing task uses the copy of the second mapping to write payload data in the first utility data object to a predefined data structure instance.

12. The method of claim 11, wherein

the payload data conforms to a standard data object definition processable by the standard business process engine;

and

the standard data object definition does not include a specification of the predefined data structure instance.

13. The method of claim 11, wherein

each of the plurality of utility data objects conform to a standard data object definition,

the context data object is annotated with the first mapping and a second mapping,

the first mapping connects elements of the predefined data structure instance to elements of the payload data structure,

the second mapping connects elements of the payload data structure instance to elements of the predefined data structure, and

the context data object does not conform to the standard data object definition.

14. The method of claim 11, wherein

the predefined data structure instance is an instance of a schema.

15. The method of claim 11, wherein

the predefined data structure instance acts as I/O interface of a service, and

the predefined data structure is an instance of a schema processable by the service.

16. The method of claim 11, wherein

each of the plurality of utility data objects conform to a standard data object definition,

the payload data structure is an XML data structure, and

the standard data object definition is an XML schema.

17. The method of claim 11, wherein

the standard business process engine is a program operable to interpret and execute only business processes having been defined in BPMN and/or BPEL.

18. The method of claim 11, further comprising

deploying a business process definition to a runtime environment within which the business process is executed, wherein

the business process definition being a document comprising one or more task specifications each specifying a task to be executed by the standard business process engine upon executing the business process, and

the injecting the post-processing task is executed during the deploying the business process definition.

19. The method of claim 18, wherein

the injecting the post-processing task includes inserting an additional task specification into the business process definition.

20. The method of claim 18, wherein

the runtime environment is a service container.