Advanced Concurrency Management in Enterprise Service Oriented Architecture Based Integrated Business Processing of Distributed Application Components

• US 20090063488A1
• Filed: 08/30/2007
• Published: 03/05/2009
• Est. Priority Date: 08/30/2007
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Zuber, Jacek, Daum, Andreas, Walter, Wolfgang, Thomas, Moritz
• Granted Patent: US 9,501,513 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06Q 10/00 Administration; Management

Abstract

A system and process that manages access to a resource in an enterprise service-oriented architecture environment. The system recognizes a master for each resource that has ultimate control over the respective resource. The master grants access to the resource though a lock system. If a system does not relinquish access to the resource, then the master is able to reclaim the lock to ensure the continued availability of the resource to all systems. This system ensures data coherency, while also improving performance by diminishing the amount of time a resource is unnecessarily locked and the time to obtain a lock.

Claims

1. A method comprising:

receiving a request for a lock to a resource in a service-oriented architecture from a first system, the request including a universal unique identifier (UUID); and

granting the lock statelessly to the first system with the UUID as a key to the lock.

2. The method of claim 1, further comprising:

returning an acknowledgement of the request to the first system indicating the lock has been granted.

3. The method of claim 1, further comprising:

denying a request from a second system for the lock upon determining a UUID of the second system does not result in a match of the key.

4. The method of claim 1, further comprising:

starting a timeout process upon granting the request; and

reclaiming the lock from the first system upon expiration of the timeout.

5. The method of claim 1, wherein the request includes an indicator of a length of time for using the resource.

6. The method of claim 1, further comprising:

broadcasting a release of the lock.

7. The method of claim 1, further comprising:

receiving a release message from the first system; and

releasing the lock in response to the release message.

8. The method of claim 4, further comprising:

reclaiming the lock by a master system in response to an expiration of the timeout process.

9. The method of claim 1, wherein processing of each request for the lock is asynchronous.

10. The method of claim 1, further comprising:

broadcasting that the lock has been reclaimed by a master system.

11. The method of claim 1, wherein the resource is a business object.

12. A machine readable medium having instructions stored therein, which when executed, cause a machine to perform a set of operations comprising:

receiving a first request for a lock of a business object in service-oriented architecture;

granting the lock statelessly to a requestor with a key based on an identifier in the first request; and

sending the lock to the requester.

13. The machine readable medium of claim 12 having instructions stored therein, which when executed, cause a machine to perform a set of operations further comprising:

receiving a second request;

checking availability of the lock based on a comparison of an identifier of the second request and the identifier of the first request; and

returning a denial of the request if the lock is not available.

14. The machine readable medium of claim 12 having instructions stored therein, which when executed, cause a machine to perform a set of operations further comprising:

storing a lock request duration received in the first request.

15. The machine readable medium of claim 14 having instructions stored therein, which when executed, cause a machine to perform a set of operations further comprising:

determining expiration of the lock request duration; and

reclaiming the lock at expiration of the lock request duration.

16. The machine readable medium of claim 12 having instructions stored therein, which when executed, cause a machine to perform a set of operations further comprising:

broadcasting a change in an availability of the lock.

17. The machine readable medium of claim 12, wherein processing of lock requests is asynchronous.

18. The machine readable medium of claim 12, wherein the identifier is a universal unique identifier (UUID).

19. A system comprising:

a business object representing a business resource in a service-oriented architecture; and

a master lock component to statelessly manage access to the business object in response to a request for access by a system.

20. The system of claim 19, wherein the lock is specific to a UUID of the request.

21. The system of claim 19, wherein the master lock component reclaims control of the business object upon detecting a timeout condition specified by the request.