SYSTEMS AND METHODS FOR ENTERPRISE-LEVEL CONTEXT MANAGEMENT

• US 20140067480A1
• Filed: 09/05/2012
• Published: 03/06/2014
• Est. Priority Date: 09/05/2012
• Status: Abandoned Application

• Current Assignee: Rocket Software Incorporated
• Original Assignee: Rocket Software Incorporated
• Inventors: Carter, James R.
• Application Number:
  US13/604,224
• Publication Number:
  US 20140067480A1
• Time in Patent Office: Days
• US Class Current: 705/7.36
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing

Abstract

A new approach is proposed that contemplates systems and methods to facilitate enterprise-level context management, which is a construct used to manage access and changes to business entities at the enterprise level instead of application level, where the business entities are used by many legacy applications and the underlying data is stored across multiple systems of record of data. An enterprise context manager is a software layer that secures exclusive access to a collection of related, yet disparate applications and resources ahead of a coordinated multiphase commit. The enterprise context manager provides a complete view of a business entity by presenting various aspects of data of the business entity through a single, unified user interface. It commits changes made to the data managed by two or more legacy applications together or rolls the data back to a pre-commit status if all changes cannot be applied.

Claims

1. A system to facilitate enterprise-level context management, comprising:

an enterprise context manager, which in operation,

requests and acquires data of a business entity used by a plurality of legacy applications, wherein the data is stored across multiple systems of record of data;

acquires and secures a context for exclusive access by a user to the data of the entity managed by the plurality of legacy applications for duration of a work flow of one or more interactive business processes that operate the data;

enables operations to the data of the business entity during execution of the work flow by the one or more interactive business processes;

commits changes made to the data of the business entity stored across the multiple systems of record of data by the operations via a coordinated multiphase commit or rolls the data back to a pre-commit status if the changes to all of the multiple systems of record cannot be applied; and

releases the context for access to the data of the entity used by the plurality of legacy applications.

2. The system of claim 1, further comprising:

an integration component, which in operation, provides the user with access to the legacy applications under a plurality of protocols.

3. The system of claim 2, wherein:

the integration component provides abstract service definitions and concrete services implementation, thereby exposing the data elements and business logic of the legacy applications to the user.

4. The system of claim 1, further comprising:

an application graphical user interface (GUI) for presenting aspects of the business entity of data and the work flow through a single, unified user interface via screen-based protocols.

5. The system of claim 1, wherein:

the context has a scope that applies to at least a subset of data elements of the business entity.

6. The system of claim 5, wherein:

the enterprise context manager does not permit the context to be acquired if another context having a matching scope already exists for the same entity.

7. The system of claim 1, wherein:

the enterprise context manager attaches metadata to the context for the duration of the work flow.

8. The system of claim 1, wherein:

the enterprise context manager implements changes made to the data managed by two or more of the legacy applications, each having different commit logic.

9. The system of claim 1, wherein:

the enterprise context manager participates in a Service Oriented Architecture (SOA) in the context of the one or more business processes that utilize the data.

10. The system of claim 1, wherein:

the enterprise context manager provides an abstract interface for securing the context for exclusive access to the data elements, thereby enabling multiphase commit operations.

11. The system of claim 1, wherein:

the enterprise context manager acts as a virtual lock server for all of the plurality of applications at the same time.

12. The system of claim 1, wherein:

the enterprise context manager enables transactional services within the plurality of legacy applications that do not support transactional updates.

13. The system of claim 1, wherein:

the enterprise context manager applies existing standards for implementing Web service as transactions to expose business logic and data from the plurality of applications.

14. The system of claim 13, wherein:

the enterprise context manager provides awareness of the context under which the transactions operate for state-less, concrete services built over the plurality of applications.

15. The system of claim 1, wherein:

the enterprise context manager provides an authorization mechanism which define those operations that are allowed to be performed on the data within the work flow.

16. A method to facilitate enterprise-level context management, comprising:

requesting and acquiring data of a business entity used by a plurality of legacy applications, wherein the data is stored across multiple systems of record of data;

acquiring and securing a context for exclusive access by a user to the data of the entity managed by the plurality of legacy applications for duration of a work flow of one or more interactive business processes that operate the data;

enabling operations to the data of the business entity during execution of the work flow by the one or more interactive business processes;

committing changes made to the data of the business entity stored across the multiple systems of record of data by the operations via a coordinated multiphase commit or rolls the data back to a pre-commit status if the changes to all of the multiple systems of record cannot be applied; and

releasing the context for access to the data of the entity used by the plurality of legacy applications.

17. The method of claim 16, further comprising:

providing abstract service definitions and concrete services implementation, thereby exposing the data elements and business logic of the legacy applications to the user.

18. The method of claim 16, further comprising:

presenting aspects of the business entity of data and the work flow through a single, unified user interface via screen-based protocols.

19. The method of claim 16, further comprising:

not permitting the context to be acquired if another context having a matching scope already exists for the same entity, wherein the scope of the context applies to at least a subset of data elements of the business entity.

20. The method of claim 16, further comprising:

attaching metadata to the context for the duration of the work flow.

21. The method of claim 16, further comprising:

implementing the changes made to the data managed by two or more of the legacy applications, each having different commit logic.

22. The method of claim 16, further comprising:

participating in a Service Oriented Architecture (SOA) in the context of the one or more business processes that utilize the data.

23. The method of claim 16, further comprising:

providing an abstract interface for securing the context for exclusive access to the data elements, thereby enabling multiphase commit operations.

24. The method of claim 16, further comprising:

providing a virtual lock server for all of the plurality of applications at the same time.

25. The method of claim 16, further comprising:

enabling transactional services within the plurality of legacy applications that do not support transactional updates.

26. The method of claim 16, further comprising:

applying existing standards for implementing Web service as transactions to expose business logic and data from the plurality of applications.

27. The method of claim 26, further comprising:

providing awareness of the context under which the transactions operate for state-less, concrete services built over the plurality of applications.

28. The method of claim 16, further comprising:

providing an authorization mechanism which define those operations that are allowed to be performed on the data within the work flow.

29. A machine readable medium having software instructions stored thereon that when executed cause a system to:

request and acquire data of a business entity used by a plurality of legacy applications, wherein the data is stored across multiple systems of record of data;

acquire and secure a context for exclusive access by a user to the data of the entity managed by the plurality of legacy applications for duration of a work flow of one or more interactive business processes that operate the data;

enable operations to the data of the business entity during execution of the work flow by the one or more interactive business processes;

commit changes made to the data of the business entity stored across the multiple systems of record of data by the operations via a coordinated multiphase commit or rolls the data back to a pre-commit status if the changes to all of the multiple systems of record cannot be applied; and

release the context for access to the data of the entity used by the plurality of legacy applications.