Increasing data accessibility across system architecture environments

• US 10,565,094 B1
• Filed: 11/07/2018
• Issued: 02/18/2020
• Est. Priority Date: 11/07/2018
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Schaude, Horst F.
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US16/183,553
• Time in Patent Office: 468 Days
• CPC Class Codes: G06F 11/36 Preventing errors by testing or debugging software
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

Techniques for increasing accessibility of data across different environments of a computer system architecture are disclosed. In some example embodiments, a computer-implemented method comprises detecting that a production instance of a software solution has been created in a production environment of a cloud computing system, the production environment having a production namespace in which production objects of the production instance are stored, detecting that a development instance of the software solution has been created in a development environment of the cloud computing system, the development environment having a development namespace in which development objects of the development instance are stored, and copying the production objects from the production namespace of the production environment into the development namespace of the development environment based on the detecting that the production instance and the development instance have been created, with the copied production objects being stored in the development namespace.

Claims

1. A computer-implemented comprising:

detecting, by at least one hardware processor, that a production instance of a software solution has been created in a production environment of a cloud computing system architecture, the production environment making the production instance of the software solution accessible for use by end users of the cloud computing system architecture and having a production namespace in which production objects of the production instance are stored, the production objects generated by use of the production instance of the software solution in the production environment;

detecting, by the at least one hardware processor, that a development instance of the software solution has been created in a development environment of the cloud computing system architecture, the development environment restricting access to the development instance of the software solution to only one or more administrative users of the cloud computing system and having a development namespace in which development objects of the development instance are stored, the one or more administrative users being different than the end users;

copying, by the at least one hardware processor, the production objects from the production namespace of the production environment into the development namespace of the development environment based on the detecting that the production instance has been created and the detecting that the development instance has been created, the copied production objects being stored in the development namespace; and

testing, by the at least one hardware processor, the development instance of the software solution in the development environment using the copied production objects stored in the development namespace.

2. The computer-implemented method of claim 1, wherein the cloud computing system architecture comprises a production tenant and a development tenant, the production environment isolating the production objects within the production tenant, and the development environment isolating the development objects within the development tenant.

3. The computer-implemented method of claim 1, wherein the software solution comprises a multi-tiered software application, and the production objects comprise entities within the multi-tiered software application that work in conjunction with a data access layer and a domain logic layer to transport data across tiers of the multi-tiered software application.

4. The computer-implemented method of claim 1, wherein the production objects comprise a set of data for at least one automated workflow.

5. The computer-implemented method of claim 1, wherein the development instance of the software solution comprises a software patch, and the detecting that the development instance of the software solution has been created is performed subsequent to the detecting that the production instance of the software solution has been created.

6. The computer-implemented method of claim 1, wherein the production namespace comprises a prefix for one or more database tables in which the production objects of the production instance are stored, and the development namespace comprises a prefix for one or more database tables in which the development objects of the development instance are stored.

7. The computer-implemented method of claim 1, wherein the copying the productions objects from the production namespace into the development namespace is triggered by the creation of the development instance.

8. The computer-implemented method of claim 1, wherein the copying the productions objects from the production namespace into the development namespace comprises:

accessing a metadata repository;

identifying all persistency database tables for the production instance of the software solution based on the accessing the metadata repository; and

for each one of the identified persistency database tables for the production instance;

identifying a prefix representing the production namespace for the one of the identified persistency database tables;

identifying a corresponding name of the one of the identified persistency database tables for the production instance using the identified prefix representing the production namespace; and

copying all of the production objects in the one of the identified persistency database tables into another persistency database table using a prefix representing the development namespace for the other persistency database table and using the identified corresponding name of the one of the identified persistency database tables as a corresponding name of the other persistency database table.

9. A system comprising:

at least one processor; and

a non-transitory computer-readable medium storing executable instructions that, when executed, cause the at least one processor to perform operations comprising;

detecting that a production instance of a software solution has been created in a production environment of a cloud computing system architecture, the production environment making the production instance of the software solution accessible for use by a plurality of end users of the cloud computing system architecture and having a production namespace in which production objects of the production instance are stored, the production objects having been generated by use of the production instance of the software solution in the production environment;

detecting that a development instance of the software solution has been created in a development environment of the cloud computing system architecture, the development environment restricting access to the development instance of the software solution to only one or more administrative users of the cloud computing system and having a development namespace in which development objects of the development instance are stored, the one or more administrative users being different than the plurality of end users;

copying the production objects from the production namespace of the production environment into the development namespace of the development environment based on the detecting that the production instance has been created and the detecting that the development instance has been created, the copied production objects being stored in the development namespace; and

testing the development instance of the software solution in the development environment using the copied production objects stored in the development namespace.

10. The system of claim 9, wherein the cloud computing system architecture comprises a production tenant and a development tenant, the production environment isolating the production objects within the production tenant, and the development environment isolating the development objects within the development tenant.

11. The system of claim 9, wherein the software solution comprises a multi-tiered software application, and the production objects comprise entities within the multi-tiered software application that work in conjunction with a data access layer and a domain logic layer to transport data across tiers of the multi-tiered software application.

12. The system of claim 9, wherein the production objects comprise a set of data for at least one automated workflow.

13. The system of claim 9, wherein the development instance of the software solution comprises a software patch, and the detecting that the development instance of the software solution has been created is performed subsequent to the detecting that the production instance of the software solution has been created.

14. The system of claim 9, wherein the production namespace comprises a prefix for one or more database tables in which the production objects of the production instance are stored, and the development namespace comprises a prefix for one or more database tables in which the development objects of the development instance are stored.

15. The system of claim 9, wherein the copying the productions objects from the production namespace into the development namespace is triggered by the creation of the development instance.

16. The system of claim 9, wherein the copying the productions objects from the production namespace into the development namespace comprises:

accessing a metadata repository;

identifying all persistency database tables for the production instance of the software solution based on the accessing the metadata repository; and

for each one of the identified persistency database tables for the production instance;

identifying a prefix representing the production namespace for the one of the identified persistency database tables;

identifying a corresponding name of the one of the identified persistency database tables for the production instance using the identified prefix representing the production namespace; and

copying all of the production objects in the one of the identified persistency database tables into another persistency database table using a prefix representing the development namespace for the other persistency database table and using the identified corresponding name of the one of the identified persistency database tables as a corresponding name of the other persistency database table.

17. A non-transitory machine-readable storage medium, tangibly embodying a set of instructions that, when executed by at least one processor, causes the at least one processor to perform operations comprising:

detecting that a production instance of a software solution has been created in a production environment of a cloud computing system architecture, the production environment making the production instance of the software solution accessible for use by a plurality of end users of the cloud computing system architecture and having a production namespace in which production objects of the production instance are stored, the production objects having been generated by use of the production instance of the software solution in the production environment;

detecting that a development instance of the software solution has been created in a development environment of the cloud computing system architecture, the development environment restricting access to the development instance of the software solution to only one or more administrative users of the cloud computing system and having a development namespace in which development objects of the development instance are stored, the one or more administrative users being different than the plurality of end users;

copying the production objects from the production namespace of the production environment into the development namespace of the development environment based on the detecting that the production instance has been created and the detecting that the development instance has been created, the copied production objects being stored in the development namespace; and

testing the development instance of the software solution in the development environment using the copied production objects stored in the development namespace.

18. The non-transitory machine-readable storage medium of claim 17, wherein the cloud computing system architecture comprises a production tenant and a development tenant, the production environment isolating the production objects within the production tenant, and the development environment isolating the development objects within the development tenant.

19. The non-transitory machine-readable storage medium of claim 17, wherein the software solution comprises a multi-tiered software application, and the production objects comprise entities within the multi-tiered software application that work in conjunction with a data access layer and a domain logic layer to transport data across tiers of the multi-tiered software application.

20. The non-transitory machine-readable storage medium of claim 17, wherein the production objects comprise a set of data for at least one automated workflow.