Systems and methods for an enterprise services framework using a state model

• US 20070143247A1
• Filed: 12/19/2005
• Published: 06/21/2007
• Est. Priority Date: 12/19/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Rau, Stefan, Hartig, Martin, Brunswig, Frank, Viegener, Johannes
• Granted Patent: US 7,844,615 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

Embodiments consistent with the principles of the invention check, before the data underlying a changed primary object is persistently save, for related objects whose data is also affected by the change. The related objects may be two or more degrees removed from the primary object. The changed primary object and all its changed related objects are then persistently saved together, so that the saved data is consistent across the related objects. Embodiments consistent with the principles of the invention also provide a state model for controlling access to services by clients and for making services available by servers.

Claims

1. A method, performed by a processor, for saving business objects comprising:

receiving a modified business object;

determining a set of related business objects traceable from the modified business object;

modifying the set of related business objects based on a modification of the modified business object;

determining whether both the modified business object and the modified set of related business objects can be saved; and

saving both the modified business object and the modified set of related business objects upon a determination that both can be saved.

2. The method of claim 1, wherein saving comprises:

committing data corresponding to the modified business object and the modified set of related business objects to at least one database.

3. The method of claim 1, wherein determining whether both can be saved comprises:

sending a pre-commit command to at least one database manager;

receiving a response from the at least one database manager; and

analyzing the response.

4. The method of claim 1, wherein determining a set of related business objects comprises:

analyzing a set of method calls from the modified business object to identify a set of called business objects.

5. The method of claim 1, wherein modifying the set of related business objects comprises:

changing data in at least one business object from the set of related business objects such that the changed data is consistent with the modification of the modified business object.

6. A system for saving business objects comprising:

means for receiving a modified business object;

means for determining a set of related business objects traceable from the modified business object;

means for modifying the set of related business objects based on a modification of the modified business object;

means for facilitating determining whether both the modified business object and the modified set of related business objects can be saved; and

means for facilitating saving both the modified business object and the modified set of related business objects upon a determination that both can be saved.

7. The system of claim 6, wherein the means for saving comprises:

means for committing data corresponding to the modified business object and the modified set of related business objects to at least one database.

8. The system of claim 6, wherein the means for determining whether both can be saved comprises:

means for sending a pre-commit command to at least one database manager;

means for receiving a response from the at least one database manager; and

means for analyzing the response.

9. The system of claim 6, wherein the means for determining a set of related business objects comprises:

means for analyzing a set of method calls from the modified business object to identify a set of called business objects.

10. The system of claim 6, wherein the means for modifying the set of related business objects comprises:

means for changing data in at least one business object from the set of related business objects such that the changed data is consistent with the modification of the modified business object.

11. A computer program product for saving business objects, comprising code for causing a processor to perform operations comprising:

receiving a modified business object;

determining a set of related business objects traceable from the modified business object;

modifying the set of related business objects based on a modification of the modified business object;

determining whether both the modified business object and the modified set of related business objects can be saved; and

saving both the modified business object and the modified set of related business objects upon a determination that both can be saved.

12. The computer program product of claim 11, wherein saving comprises:

committing data corresponding to the modified business object and the modified set of related business objects to at least one database.

13. The computer program product of claim 11, wherein determining whether both can be saved comprises:

sending a pre-commit command to at least one database manager;

receiving a response from the at least one database manager; and

analyzing the response.

14. The computer program product of claim 11, wherein determining a set of related business objects comprises:

analyzing a set of method calls from the modified business object to identify a set of called business objects.

15. The computer program product of claim 11, wherein modifying the set of related business objects comprises:

changing data in at least one business object from the set of related business objects such that the changed data is consistent with the modification of the modified business object.

16. A server for saving business objects comprising:

a receiver that receives a save request specifying a business object to be saved;

a processor, communicatively connected to the receiver, adapted for;

entering a software-controlled state in which receiving a service request will trigger failure processing,

identifying a set of related business objects affected by data in the business object to be saved, and

modifying data in the set of related business objects to be consistent with the data in the business object to be saved; and

a transmitter, communicatively connected to the processor, that sends a plurality of pre-save checks to at least one database manager for the data in the business object to be saved and the data in the set of related business objects, and

sends a command to commit the data in the business object to be saved and a command to commit the data in the set of related business objects to at least one database controlled by the at least one database manager;

wherein the processor is further adapted to exit the state in which receiving a service request will trigger failure processing after the commands to commit are sent.

17. The server of claim 16, further comprising:

a transmitter, communicatively connected to the processor, for transmitting a completion notification to an entity that transmitted the save request specifying the business object to be saved.

19. The system of claim 17, further comprising:

means for transmitting a completion notification to an entity that transmitted the save request specifying the business object to be saved.

18. A system for saving business objects comprising:

means for receiving a save request specifying a business object to be saved;

means for entering a software-controlled state in which receiving a service request will cause failure processing;

means for identifying a set of related business objects affected by data in the business object to be saved;

means for modifying data in the set of related business objects to be consistent with the data in the business object to be saved;

means for sending a plurality of pre-save checks to at least one database manager for the data in the business object to be saved and the data in the set of related business objects;

means for facilitating committing the data in the business object to be saved and the data in the set of related business objects to at least one database controlled by the at least one database manager; and

means for exiting the software-controlled state in which receiving a service request will cause failure processing.

20. A computer program product for saving business objects, comprising code for causing a processor to perform operations comprising:

receiving a save request specifying a business object to be saved;

entering a software-controlled state in which receiving a service request will cause failure processing to occur;

identifying a set of related business objects affected by data in the business object to be saved;

modifying data in the set of related business objects to be consistent with the data in the business object to be saved;

sending a plurality of pre-save checks to at least one database manager for the data in the business object to be saved and the data in the set of related business objects;

committing the data in the business object to be saved and the data in the set of related business objects to at least one database controlled by the at least one database manager; and

exiting the software-controlled state in which receiving a service request will cause failure processing to occur.