Checkpoint flow processing system for on-demand integration of distributed applications

• US 20070255713A1
• Filed: 04/26/2006
• Published: 11/01/2007
• Est. Priority Date: 04/26/2006
• Status: Abandoned Application

• Current Assignee: Bayhub Incorporated
• Original Assignee: Bayhub Incorporated
• Inventors: Li, John, Wang, Lin
• Application Number:
  US11/411,411
• Publication Number:
  US 20070255713A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

In one embodiment, an application integration system collects business application information and generates and stores certain business flow and state information for the application, its involved users and shared business content within the system. This automation process defines the collaboration models between the content, process and users involved in the collaboration project. The automation process uses specific information pertaining to the involved users and applications of the system, the process flows of the application program, and the shared content to automate the integration of the distributed computer applications by defining the integration flow as a process checkpoint flow consisting of numerous checkpoints through which the business content transitions.

Claims

1. A method of integrating a plurality of separate business applications used in an enterprise project comprising:

defining process steps associated with each business application;

identifying business content data used by each business application;

deriving metadata from the business content used by each business application;

defining role based access control privileges associated with each user of a plurality of users of the content;

identifying a team of users for each business application;

associating access privileges for each user of the team of users with respect to the business content based on a role and identity of each user;

deriving an overall process flow based on the process steps associated with each business application, the overall process flow including one or more checkpoints defining a version of the business content.

2. The method of claim 1, wherein the one or more checkpoints include approval requirements from one or more users having appropriate role and identity privilege.

3. The method of claim 2, wherein the metadata comprises a descriptor for one or more types of data objects representing the business content data.

4. The method of claim 3, wherein each business application is an application program executed on a client computer operated by a first user team.

5. The method of claim 4, wherein the business content is modified by the first user team or a second user team, the second user team comprising one or more users with access privileges allowing modification of the business content.

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

tracking the version of the business content;

storing historical data associated with the business content including a state of the business content at a version earlier than a present version.

7. The method of claim 6, wherein the business content is stored in a data store connected to a server computer coupled to the client computer.

8. The method of claim 2, further comprising the step of locking the business content during a checkpoint so that no modification of the business content is allowed by either of the first user team and the second user team.

9. A method comprising:

receiving checkpoint flow information for an enterprise system, the checkpoint flow modifying content used in the enterprise application, wherein the checkpoint flow includes one or more checkpoints, each checkpoint causing modification of shared content used by a plurality of applications within the enterprise system;

defining the shared content in terms of content object types comprising the shared content;

tagging the shared content with version information representing instances of the shared content based upon processing of the content at each checkpoint.

10. The method of claim 9, further comprising the steps of:

defining role based access control privileges associated with each user of a plurality of users of the content; and

tagging the shared content with access filters that limit access to the shared content based on the role based access control privilege of each user.

11. The method of claim 10, further comprising the steps of:

tagging the shared content with identifier information including source information identifying an application program and user information identifying a modifying user; and

incorporating version history information into the shared content, the version history information including at least one of creation time, modification time, and modification source.

12. The method of claim 11, wherein at least one checkpoint of the one or more checkpoints includes an interactive processing step, the method further comprising the step of transitioning the shared content from a first transition point to a second transition point in accordance with the interactive process step.

13. The method of claim 12, wherein the interactive process step comprises obtaining content approval based on a hierarchical privilege of a user of the plurality of users.

14. The method of claim 11, further comprising the step of locking the shared content during a checkpoint so that no modification of the shared content is possible.

15. A method comprising:

defining business content data used in a business application as metadata definitions describing one or more types of data objects representing the business content data;

defining role based access control privileges with each user of a plurality of users of the business content data;

defining one or more transition points of the business application; and

combining the metadata definitions, the role based access control privileges and the transition points in an automated process to implement the business application as a runtime executable program.

16. The method of claim 15, wherein the runtime executable program is executed by the plurality of users over a distributed computer network.

17. The method of claim 16, wherein each transition point causes modification of the business content data by one or more users of the business application, and further comprising a versioning process that associates a current version of the business content object with the transition point and a modifying user.

18. The method of claim 16, wherein the role based access control privileges define which users are allowed to cause modification of the business content data.

19. The method of claim 15, wherein the transition points comprise one of a checkpoint along the checkpoint flow and a sub-checkpoint associated with a checkpoint.

20. The method of claim 19, wherein the transition points further comprise an approval chain requiring approval of the business content at the transition points by a user with appropriate role based access control privilege.