RESOURCE OPTIMIZATION USING DATA ISOLATION TO PROVIDE SAND BOX CAPABILITY

• US 20180074814A1
• Filed: 04/13/2017
• Published: 03/15/2018
• Est. Priority Date: 09/15/2016
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ganta, Suman, Shenbagam, Sundar, Sabharwal, Nikhil
• Granted Patent: US 10,552,591 B2
• Time in Patent Office: 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 21/31 User authentication
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

According to one embodiment, data isolation is provided with respect to lifecycle phases of an application. For example, a test data isolation and a production data isolation of at least one resource are created. The test data isolation corresponds with a test lifecycle phase of the application and the production data isolation corresponds with a production lifecycle phase of the application. A first set of data is stored in the test data isolation and a second set of data is stored in the production data isolation. A test version of the application is executed in the test data isolation. A production version of the application is executed in the production data isolation. A particular executing version of the application is allowed to only access data according to a lifecycle phase selected for a user.

Claims

1. A tangible processor-readable storage device including instructions executable by a digital processor for a method of providing data isolation with respect to lifecycle phases of an application, the tangible processor-readable storage device including one or more instructions for:

creating a test data isolation and a production data isolation of at least one resource, wherein the test data isolation corresponds with a test lifecycle phase of the application and the production data isolation corresponds with a production lifecycle phase of the application;

storing a first set of data in the test data isolation and a second set of data in the production data isolation;

executing a test version of the application in the test data isolation;

executing a production version of the application in the production data isolation; and

allowing a particular executing version of the application to only access one or more of a process definition, authorization, credentials, or runtime data according to a lifecycle phase selected for a user so that a user'"'"'s login procedure to a workspace is the same regardless the selected lifecycle phase.

2. The tangible processor-readable storage device as recited by claim 1, wherein the user is not aware whether a topology of resources is a single resource or multiple resources.

3. The tangible processor-readable storage device as recited by claim 1, wherein the creating of the test data isolation and the production data isolation of the at least one resource further comprises:

sharing a single resource across the test data isolation and the production data isolation.

4. The tangible processor-readable storage device as recited by claim 1, wherein the creating of the test data isolation and the production data isolation of the at least one resource further comprises:

providing each of the test data isolation and the production data isolation with a separate resource.

5. The tangible processor-readable storage device as recited by claim 1, wherein the test data isolations further comprise a unit test data isolation and a system test data isolation.

6. The tangible processor-readable storage device as recited by claim 1, wherein the method further comprises:

isolating one or more of process definition, credentials, run time data in each of the test data isolation and the production data isolation.

7. The tangible processor-readable storage device as recited by claim 1, wherein each of the data isolations is a partition.

8. The tangible processor-readable storage device as recited by claim 1, wherein the at least one resource is a logical grouping of one or more virtual machines.

9. The tangible processor-readable storage device as recited by claim 1, wherein the method further comprises:

creating, testing and managing the lifecycle phases of the application using a composer provided by Platform as a Service (PaaS).

10. The tangible processor-readable storage device as recited by claim 1, wherein the lifecycle phase selected by the user is a first lifecycle phase and the particular executing version is a first executing version and wherein method further comprises:

allowing the second executing version of the application to only access one or more of a second process definition, a second authorization, second credentials, or second runtime data according to a second lifecycle phase selected by the user where a user'"'"'s login procedure to the workspace is the same for the first lifecycle phase and the second lifecycle phase.

11. A method of providing data isolation with respect to lifecycle phases of an application executable by a digital processor, wherein the method comprises:

creating a test data isolation and a production data isolation of at least one resource, wherein the test data isolation corresponds with a test lifecycle phase of the application and the production data isolation corresponds with a production lifecycle phase of the application;

storing a first set of data in the test data isolation and a second set of data in the production data isolation;

executing a test version of the application in the test data isolation;

executing a production version of the application in the production data isolation; and

allowing a particular executing version of the application to only access one or more of a process definition, authorization, credentials, or runtime data according to a lifecycle phase selected for a user so that a user'"'"'s login procedure to a workspace is the same regardless the selected lifecycle phase.

12. The method as recited by claim 11, wherein the user is not aware whether a topology of resources is a single resource or multiple resources.

13. The method as recited by claim 11, wherein the creating of the test data isolation and the production data isolation of the at least one resource further comprises:

sharing a single resource across the test data isolation and the production data isolation.

14. The method as recited by claim 11, wherein the test data isolations further comprise a unit test data isolation and a system test data isolation.

15. The method as recited by claim 11, wherein the method further comprises:

isolating one or more of process definition, credentials, run time data in each of the test data isolation and the production data isolation.

16. The method as recited by claim 15, wherein the process definition is stored in a run time repository, the credentials are stored in a policy store, the credentials are stored in a credential store, and the run time data is stored in a database schema.

17. The method as recited by claim 11, wherein each of the data isolations is a partition.

18. The method as recited by claim 11, wherein the at least one resource is a logical grouping of one or more virtual machines.

19. The method as recited by claim 11, wherein the method further comprises:

creating, testing and managing the lifecycle phases of the application using a composer provided by Platform as a Service (PaaS).

20. An apparatus comprising:

one or more processors; and

a tangible processor-readable storage device including instructions for;

creating a test data isolation and a production data isolation of at least one resource, wherein the test data isolation corresponds with a test lifecycle phase of an application and the production data isolation corresponds with a production lifecycle phase of the application;

storing a first set of data in the test data isolation and a second set of data in the production data isolation;

executing a test version of the application in the test data isolation;

executing a production version of the application in the production data isolation; and

allowing a particular executing version of the application to only access one or more of a process definition, authorization, credentials, or runtime data according to a lifecycle phase selected for a user so that a user'"'"'s login procedure to a workspace is the same regardless the selected lifecycle phase.