GENERATION FRAMEWORK FOR MAPPING OF OBJECT MODELS IN A DEVELOPMENT ENVIRONMENT

• US 20140019934A1
• Filed: 07/16/2012
• Published: 01/16/2014
• Est. Priority Date: 07/16/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: Daniel Figus
• Inventors: Schlarb, Uwe, Hennrich, Hans-Juergen, Niehoff, Daniel, Baeuerle, Stefan, Figus, Daniel
• Granted Patent: US 8,856,727 B2
• Time in Patent Office: Days
• 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 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 affected primary object;

comparing the list of required entities with content stored in an object mapping repository accessible to the backend model, the comparing comprising creating a target list of activities relating to creating, changing, or deleting of entities in one or more backend repositories necessary to support the affected primary object and also determining a sequence for performance of the activities in the target list;

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. A 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 affected primary object is deleted in the development environment.

3. A 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 affected primary object in the development environment.

4. A 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. A computer program product as in claim 1, wherein the comparing is performed by a delta handler.

6. A computer program product as in claim 1, wherein the change made in the development environment comprises a logic extension to the affected 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 affected primary object being extended via the logic extension, which requires a regeneration of extensions to the affected 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.

7. 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 affected primary object;

comparing the list of required entities with content stored in an object mapping repository accessible to the backend model, the comparing comprising creating a target list of activities relating to creating, changing, or deleting of entities in one or more backend repositories necessary to support the affected primary object and also determining a sequence for performance of the activities in the target list;

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.

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

9. A system as in claim 7, 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 affected primary object in the development environment.

10. A system as in claim 7, 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.

11. A system as in claim 7, wherein the comparing is performed by a delta handler.

12. A system as in claim 7, wherein the change made in the development environment comprises a logic extension to the affected 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 affected primary object being extended via the logic extension, which requires a regeneration of extensions to the affected 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.

13. 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 affected primary object;

comparing the list of required entities with content stored in an object mapping repository accessible to the backend model, the comparing comprising creating a target list of activities relating to creating, changing, or deleting of entities in one or more backend repositories necessary to support the affected primary object and also determining a sequence for performance of the activities in the target list;

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.

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

15. A computer-implemented method as in claim 13, 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 affected primary object in the development environment.

16. A computer-implemented method as in claim 13, 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.

17. A computer-implemented method as in claim 13, wherein the comparing is performed by a delta handler.

18. A computer-implemented method as in claim 13, wherein the change made in the development environment comprises a logic extension to the affected 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 affected primary object being extended via the logic extension, which requires a regeneration of extensions to the affected 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.

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