EXTERNAL PLATFORM EXTENSIONS IN A MULTI-TENANT ENVIRONMENT

• US 20150033217A1
• Filed: 09/03/2013
• Published: 01/29/2015
• Est. Priority Date: 07/25/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Mellor, David R.
• Granted Patent: US 9,294,482 B2
• Time in Patent Office: Days
• US Class Current: 717/171
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/1756 based on delta files
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/83 Querying
• CPC Class Codes: G06F 21/604 Tools and structures for managing or administering access control systems
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/6209 to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• 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 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers

Abstract

Methods and systems are described for allowing third party developers to add extensions to a cloud service provider'"'"'s software as a service (SaaS) services by editing an ‘empty’ config file according to a schema provided by the cloud service provider to form a delta file and then merging the delta file with an internal, full version of the config file. The full config file is then used to initialize and instantiate objects upon a restart of the cloud provider'"'"'s services.

Claims

1. A method of enforcing access control of features in a multi-tenant cloud environment, the method comprising:

reading a file schema that defines an element, a child element, and an attribute;

defining, in a config file that is compatible with the file schema, a service access rule for a feature of a service in a multi-tenant cloud environment, the defining using the element, the child element, and the attribute;

delivering a copy of the config file;

allowing editing the copy of the config file to define a service access of the feature;

determining, using a processor operatively coupled with a memory, changes to the copy of the config file made during editing to create a delta file;

packaging the delta file in an archive that is included in a shared library of class files;

merging the delta file with the config file to create an executable code config file having a feature for the service;

reading, by a service, the executable code config file;

initializing objects for the service with the feature using the executable code config file; and

instantiating objects for the feature of the service using the executable code config file.

2. The method of claim 1 wherein the delivered copy of the config file has no child elements.

3. The method of claim 1 wherein the determining changes to the copy of the config file includes tracking changes during editing.

4. The method of claim 1 wherein the determining changes to the copy of the config file includes comparing pre-edited and post-edited versions of the copy.

5. The method of claim 1 wherein the determining changes to the copy of the config file ignores blank lines.

6. The method of claim 1 wherein the determining changes to the copy of the config file ignores remarks.

7. The method of claim 1 wherein the archive includes a MAR file.

8. The method of claim 1 wherein the merging includes inserting contents of the delta file into the config file.

9. The method of claim 1 wherein the shared library is within an MDS customization file.

10. The method of claim 1 wherein the config file schema includes an extensible markup language (XML) schema and the config file conforms to the XML schema.

11. The method of claim 1 wherein the copy of the config file is in an ADF library jar file.

12. The method of claim 1 further comprising:

creating the file schema that defines an element, a child element, and an attribute.

13. The method of claim 1 further comprising:

editing the copy of the config file to define a service access of the feature.

14. The method of claim 1 further comprising:

instantiating objects for the feature of the service using the executable code config file such that multiple tenants in the multi-tenant cloud environment can access the feature of the service.

15. The method of claim 1 wherein the service includes a Java service.

16. The method of claim 1 wherein the operations are performed in the order shown.

17. A machine-readable tangible medium embodying information indicative of instructions for causing one or more machines to perform operations comprising:

reading a file schema that defines an element, a child element, and an attribute;

defining, in a config file that is compatible with the file schema, a service access rule for a feature of a service in a multi-tenant cloud environment, the defining using the element, the child element, and the attribute;

delivering a copy of the config file;

allowing editing the copy of the config file to define a service access of the feature;

determining changes to the copy of the config file made during editing to create a delta file;

packaging the delta file in an archive that is included in a shared library of class files;

merging the delta file with the config file to create an executable code config file having a feature for the service;

reading, by a service, the executable code config file;

initializing objects for the service with the feature using the executable code config file; and

instantiating objects for the feature of the service using the executable code config file.

18. The medium of claim 17 wherein the delivered copy of the config file has no child elements.

19. A computer system executing instructions, the system comprising:

at least one processor;

a memory operatively coupled with the at least one processor, the processor executing computer code stored in the memory for;

reading a file schema that defines an element, a child element, and an attribute;

defining, in a config file that is compatible with the file schema, a service access rule for a feature of a service in a multi-tenant cloud environment, the defining using the element, the child element, and the attribute;

delivering a copy of the config file;

allowing editing the copy of the config file to define a service access of the feature;

determining changes to the copy of the config file made during editing to create a delta file;

packaging the delta file in an archive that is included in a shared library of class files;

merging the delta file with the config file to create an executable code config file having a feature for the service;

reading, by a service, the executable code config file;

initializing objects for the service with the feature using the executable code config file; and

instantiating objects for the feature of the service using the executable code config file.

20. The system of claim 19 wherein the delivered copy of the config file has no child elements.