Generation framework for mapping of object models in a development environment

• US 8,856,727 B2
• Filed: 07/16/2012
• Issued: 10/07/2014
• Est. Priority Date: 07/16/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Schlarb, Uwe, Hennrich, Hans-Juergen, Niehoff, Daniel, Baeuerle, Stefan, Figus, Daniel
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Luna, Roberto E
• Application Number:
  US13/550,295
• Publication Number:
  US 20140019934A1
• Time in Patent Office: 813 Days
• Field of Search: None
• US Class Current: 717/104
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/72 Code refactoring

Abstract

A delta handler can allow calculation of difference between an already generated set of backend entities and a set of new entities necessary to support a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture. Improved stability and robustness can be provided via an approach in which a target list of activities relating to creating, changing, or deleting of entities in backend repositories necessary to support the affected primary object is created and a sequence for performance of the activities in the target list is determined in a manner that can allow handling of such activities in a unified manner rather than on a per object type basis. Related methods, systems, articles of manufacture, and the like are described.

Claims

1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

calling a compiler interface for a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture;

returning, by the compiler interface, a list of required entities in the backend model to support the primary object, the list of required entities comprising content of the primary object;

ascertaining deltas between the content of the primary object from the list of required entities and pre-existing content stored in an object mapping repository accessible to the backend model, the ascertaining comprising comparing, using a delta handler, the content of the primary object from the list of required entities and the pre-existing content stored in the object mapping repository;

creating, based at least on the ascertained deltas, a target list of activities necessary to update the pre-existing content to match the content of the primary object, the creating further comprising determining a sequence for performance of the activities in the target list, wherein the activities comprise at least one of creating, changing, or deleting of entities in one or more backend repositories necessary to support the primary object;

performing the activities in the target list according to the determined sequence; and

storing the target list along with a status of the activities in the target list in the object mapping repository.

2. The computer program product as in claim 1, wherein the comparing of the list of required entities comprises comparing the object mapping repository with an empty list when the primary object is deleted in the development environment.

3. The computer program product as in claim 1, wherein the operations further comprise:

performing an error analysis in response to occurrence of an error, the diagnosing comprising deriving, from the object mapping repository, a list of entities generated in the backend model as representatives for the primary object in the development environment.

4. The computer program product as in claim 1, wherein the operations further comprise:

determining, using the target list stored in the object mapping repository, a point in time at which the necessary operations to result in creating, changing, or deleting of the entities in the one or more backend repositories operation has failed due to an error or other interruption; and

restarting the performing of the necessary operations at the point once the error or other interruption has been corrected.

5. The computer program product as in claim 1, wherein the change made in the development environment comprises a logic extension to the primary object as part of a migration from a prior version of an enterprise services framework to a new version of the enterprise services framework, the migration causing generation of at least one extension to the prior enterprise services framework, the primary object being extended via the logic extension, which requires a regeneration of extensions to the primary object that were previously created in the prior enterprise services framework, the regeneration comprising deleting extensions created in the prior version of the enterprise services framework and creating new extensions in the new version of the enterprise services framework.

17. The computer program product as in claim 1, wherein the delta handler handles multiple activities in a unified manner.

6. A system comprising:

at least one programmable processor; and

a machine-readable medium storing instructions that, when executed by the at least one processor, cause the at least one programmable processor to perform operations comprising;

calling a compiler interface for a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture;

returning, by the compiler interface, a list of required entities in the backend model to support the primary object, the list of required entities comprising content of the primary object;

ascertaining deltas between the content of the primary object from the list of required entities and pre-existing content stored in an object mapping repository accessible to the backend model, the ascertaining comprising comparing, using a delta handler, the content of the primary object from the list of required entities and the pre-existing content stored in the object mapping repository;

creating, based at least on the ascertained deltas, a target list of activities necessary to update the pre-existing content to match the content of the primary object, the creating further comprising determining sequence for performance of the activities in the target list wherein the activities comprise at least one of creating, changing, or deleting of entities in one or more backend repositories necessary to support the primary object;

performing the activities in the target list according to the determined sequence; and

storing the target list along with a status of the activities in the target list in the object mapping repository.

7. The system as in claim 6, wherein the comparing of the list of required entities comprises comparing the object mapping repository with an empty list when the primary object is deleted in the development environment.

8. The system as in claim 6, wherein the operations further comprise:

performing an error analysis in response to occurrence of an error, the diagnosing comprising deriving, from the object mapping repository, a list of entities generated in the backend model as representatives for the primary object in the development environment.

9. The system as in claim 6, wherein the operations further comprise:

determining, using the target list stored in the object mapping repository, a point in time at which the necessary operations to result in creating, changing, or deleting of the entities in the one or more backend repositories operation has failed due to an error or other interruption; and

restarting the performing of the necessary operations at the point once the error or other interruption has been corrected.

10. The system as in claim 6, wherein the change made in the development environment comprises a logic extension to the primary object as part of a migration from a prior version of an enterprise services framework to a new version of the enterprise services framework, the migration causing generation of at least one extension to the prior enterprise services framework, the primary object being extended via the logic extension, which requires a regeneration of extensions to the primary object that were previously created in the prior enterprise services framework, the regeneration comprising deleting extensions created in the prior version of the enterprise services framework and creating new extensions in the new version of the enterprise services framework.

11. A computer-implemented method comprising:

calling a compiler interface for a primary object affected by a change made in a development environment supporting extensions to a backend model of a software architecture;

returning, by the compiler interface, a list of required entities in the backend model to support the primary object, the list of required entities comprising content of the primary object;

ascertaining deltas between the content of the primary object from the list of required entities and pre-existing content stored in an object mapping repository accessible to the backend model, the ascertaining comprising comparing, using a delta handler, the content of the primary object from the list of required entities and the pre-existing content stored in the object mapping repository;

creating, based at least on the ascertained deltas, a target list of activities necessary to update the pre-existing content to match the content of the primary object, the creating further comprising determining a sequence for performance of the activities in the target list, wherein the activities comprise at least one of creating, changing, or deleting of entities in one or more backend repositories necessary to support the primary object;

performing the activities in the target list according to the determined sequence; and

storing the target list along with a status of the activities in the target list in the object mapping repository.

12. The computer-implemented method as in claim 11, wherein the comparing of the list of required entities comprises comparing the object mapping repository with an empty list when the primary object is deleted in the development environment.

13. The computer-implemented method as in claim 11, further comprising:

performing an error analysis in response to occurrence of an error, the diagnosing comprising deriving, from the object mapping repository, a list of entities generated in the backend model as representatives for the primary object in the development environment.

14. The computer-implemented method as in claim 11, further comprising:

determining, using the target list stored in the object mapping repository, a point in time at which the necessary operations to result in creating, changing, or deleting of the entities in the one or more backend repositories operation has failed due to an error or other interruption; and

restarting the performing of the necessary operations at the point once the error or other interruption has been corrected.

15. The computer-implemented method as in claim 11, wherein the change made in the development environment comprises a logic extension to the primary object as part of a migration from a prior version of an enterprise services framework to a new version of the enterprise services framework, the migration causing generation of at least one extension to the prior enterprise services framework, the primary object being extended via the logic extension, which requires a regeneration of extensions to the primary object that were previously created in the prior enterprise services framework, the regeneration comprising deleting extensions created in the prior version of the enterprise services framework and creating new extensions in the new version of the enterprise services framework.

16. The computer-implemented method as in claim 11, wherein at least one of the calling, the returning, the comparing, the performing, and the storing is performed by at least one programmable processor.