System architecture for business process development and execution with introspection and generic components

• US 7,562,339 B2
• Filed: 01/15/2002
• Issued: 07/14/2009
• Est. Priority Date: 01/15/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Gabeiras, Emilio L., Racca, Felix G.
• Primary Examiner(s): Kang; Insun
• Application Number:
  US10/050,316
• Publication Number:
  US 20080307392A1
• Time in Patent Office: 2,737 Days
• Field of Search: 717114-124, 717101-109, 707/1, 707/10, 707102-1041, 705/1, 705/7
• US Class Current: 717/102
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 8/34 Graphical or visual programming
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

A system for designing a business process includes an introspection module that transforms implementation-specific components into generic components. The implementation-specific components are associated with a number of implementations. A component manager defines the generic components. A process designer selects at least one of the generic components from the component manager, and generates a business process that uses the at least one of the generic components.

Claims

1. A system for designing and executing processes, said system comprising:

an introspection module in a generic introspection framework that automatically generates a catalog of generic components by introspecting a set of exposed application programming interfaces (APIs) of a plurality of heterogeneous applications created in different programming languages and transforming a plurality of implementation-specific components of said heterogeneous applications into the generic components of said catalog by binding identifiers of the generic components with identifiers of the implementation-specific components wherein the catalog contains a series of entries in a binding table automatically created during the introspection of the APIs, each entry representing a generic component which, when invoked, is bound to at least one of the implementation-specific components of said heterogeneous applications upon execution of the processes, the catalog further containing a module comprising the generic components associated with a folder comprising an XML file when the implementation-specific components are saved in the catalog as the generic components;

an implementation module that includes procedures to access the APIs and maps the implementation-specific components to the generic components by using its own introspection mechanism and sends the mapped implementation-specific components to the generic introspection framework;

a component manager coupled to the introspection module and configured to manage said catalog automatically generated by the introspection module by defining and organizing the generic components in said catalog; and

a process designer coupled to the component manager and configured to;

select at least one of the generic components from said catalog managed by the component manager; and

graphically construct a process definition for the processes that includes a series of graphically represented activities linked by one or more transitions and associated with abstract roles specified for the activities wherein at least one activity of said process definition invokes the selected generic component from said catalog;

whereby a single process is assembled from the implementation-specific components of the different programming languages, the implementation-specific components being compiled modular routines of the heterogeneous applications that have been previously created in different programming languages; and

a repository for storing the process definition; and

one or more process engines that execute said process definition to instantiate a process instance, wherein the process instance interacts with the plurality of heterogeneous applications by invoking the generic components in said catalog and wherein the process instance integrates the plurality of heterogeneous applications into the single process by invoking services from the plurality of heterogeneous applications during execution of the activities of said processes;

wherein during execution of the process instance, the compiled modular routines of the heterogeneous applications are invoked in order to complete the activities of said process instance.

2. The system of claim 1, further comprising an organizational repository that includes said catalog, organizational data and a plurality of processes generated by said process designer.

3. The system of claim 1, further comprising a debugger coupled to the process designer and configured to detect an error of the process definition.

4. The system of claim 1, further comprising:

a data warehouse coupled to the one or more process engines and configured to store transactional data describing the process instance; and

a data server coupled to the data configured to organize the transactional data.

5. The system of claim 1 wherein said implementation module is used to access implementation-specific components associated with at least one of:

JAVA, Standard Query Language (SQL), Automation, Enterprise JavaBeans (EJB), CORBA, Remote Method Invocation (RMI), Extensible Markup Language (XML) schemas, Web Services and JAVA Naming and Directory Interface (JNDI).

6. The system of claim 1 wherein said process definition is published to the repository before being deployed to the one or more process engines.

7. The system of claim 1 wherein the entries of the catalog include metadata that describes at least one of the plurality of implementation-specific components.

8. The system of claim 1 wherein an activity of said process definition connects to a subprocess.

9. The system of claim 1 wherein said transitions indicate a next activity that is to be initiated after executing a previous activity.

10. The system of claim 1, further comprising:

a warehouse server that consolidates data from multiple process engines, wherein the warehouse server generates an N-dimensional cube to organize said data, wherein dimensions of the cube represent organizational data and measures of the cube represent transactional data of process instances.

11. The system of claim 10, wherein the measures of said cube are filtered by the dimensions of said cube in order to generate an analytical representation.

12. The system of claim 11 wherein the measures are identified with one or more of the following:

a number of process instances in activities, the number of instances completed by said single process, execution time of a process instance and an average wait time for an activity.

13. The system of claim 11 wherein the dimensions are associated with one or more of the following:

an organizational unit, a role, a user and time.

14. A computer implemented method for designing and executing processes, said method comprising:

automatically generating a catalog of generic components in a generic introspection framework by introspecting a set of exposed application programming interfaces (APIs) of a plurality of heterogeneous applications implemented in multiple different programming languages and transforming implementation-specific components of the plurality of heterogeneous applications into the generic components of said catalog by binding identifiers of the generic components with identifiers of the implementation-specific components, wherein the catalog contains a series of entries in a binding table automatically created during the introspection of the APIs, each entry representing a generic component which, when invoked, is bound to at least one of the implementation-specific components of said heterogeneous applications upon execution of the processes, the catalog further containing a module comprising the generic components associated with a folder comprising an XML file when the implementation-specific components are saved in the catalog as the generic components;

providing an implementation module that includes procedures to access the APIs and maps the implementation-specific components to the generic components by using its own introspection mechanism and sends the mapped implementation-specific components to the generic introspection framework;

selecting at least one of the generic components from the catalog;

graphically constructing one or more processes definitions for the processes, each process definition including a series of graphically represented activities linked by one or more transitions and associated with abstract roles specified for the activities wherein at least one activity of said processes invokes the at least one generic component selected from said catalog, whereby a single process is assembled from the implementation-specific components of the multiple different programming languages, the implementation-specific components being compiled modular routines of the heterogeneous applications that have been previously created in the multiple different programming languages; and

executing the constructed one or more process definitions at one or more process engines in order to instantiate a process instance, wherein the process instance interacts with the plurality of heterogeneous applications by invoking the generic components of said catalog and wherein the process instance integrates the plurality of heterogeneous applications into the single process by invoking services from the plurality of heterogeneous applications during execution of the activities of said processes.

15. The method of claim 14, further comprising:

providing an organizational repository that includes said catalog, organizational data and the one or more process definitions.

16. The method of claim 14, further comprising:

detecting an error of the one or more process definitions by using a debugger.

17. The method of claim 14, further comprising:

storing transactional data describing the process instance in a data warehouse;

and organizing the transactional data at a data server.

18. The method of claim 14 wherein the implementation module is used to access implementation-specific components associated with at least one of:

JAVA, Standard Query Language (SQL), Automation, Enterprise JavaBeans (EJB), CORBA, Remote Method Invocation (RMI), Extensible Markup Language (XML) schemas, Web Services and JAVA Naming and Directory Interface (JNDI).

19. The method of claim 14, further comprising:

consolidating data from multiple process engines by a warehouse server, wherein the warehouse server generates an N-dimensional cube to organize said data, wherein dimensions of the cube represent organizational data and measures of the cube represent transactional data of process instances.

20. A computer having one or more processors to design and execute processes, wherein instructions executed by the one or more processors cause the computer to perform the steps of:

automatically generating a catalog of generic components in a generic introspection framework by introspecting a set of exposed application programming interfaces (APIs) of a plurality of heterogeneous applications implemented in multiple different programming languages and transforming implementation-specific components of the plurality of heterogeneous applications into the generic components of said catalog by binding identifiers of the generic components with identifiers of the implementation-specific components, wherein the catalog contains a series of entries in a binding table automatically created during the introspection of the APIs, each entry representing a generic component which, when invoked, is bound to at least one of the implementation-specific components of said heterogeneous applications upon execution of the processes, the catalog further containing a module comprising the generic components associated with a folder comprising an XML file when the implementation-specific components are saved in the catalog as the generic components;

providing an implementation module that includes procedures to access the APIs and maps the implementation-specific components to the generic components by using its own introspection mechanism and sends the mapped implementation-specific components to the generic introspection framework;

selecting at least one of the generic components from the catalog;

graphically constructing one or more processes definitions for the processes, each process definition including a series of graphically represented activities linked by one or more transitions and associated with abstract roles specified for the activities wherein at least one activity of said processes invokes the at least one generic component selected from said catalog, whereby a single process is assembled from the implementation-specific components of the multiple different programming languages, the implementation-specific components being compiled modular routines of the heterogeneous applications that have been previously created in the multiple different programming languages; and

executing the constructed one or more process definitions at one or more process engines in order to instantiate a process instance, wherein the process instance interacts with the plurality of heterogeneous applications by invoking the generic components of said catalog and wherein the process instance integrates the plurality of heterogeneous applications into the single process by invoking services from the plurality of heterogeneous applications during execution of the activities of said processes.