FLEXIBLE MULTI-TENANT SUPPORT OF METADATA EXTENSION

• US 20100161648A1
• Filed: 12/19/2008
• Published: 06/24/2010
• Est. Priority Date: 12/19/2008
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Said, Baré, Eberlein, Peter, Baeuerle, Stefan A.
• Application Number:
  US12/339,392
• Publication Number:
  US 20100161648A1
• Time in Patent Office: Days
• US Class Current: 707/769
• CPC Class Codes: G06F 16/24573 using data annotations, e.g. user-defined metadata
• CPC Class Codes: G06F 9/4488 Object-oriented

Abstract

A system may include reception, from a client, of a request for access to an instance of an object model, identification of extension metadata associated with the object model and associated with the client in a metadata repository, identification of client-independent metadata of the object model in the metadata repository, merging of the client-independent metadata and the extension metadata associated with the client to create a merged object model, and access of the instance based on the merged object model.

In some aspects, an extension object model including the extension metadata associated with the object model is created in a namespace of the metadata repository associated with the client, a client-specific object model associated with the object model and including an association to the extension object model is created in the namespace of the metadata repository associated with the client, and, in response to the received request, the client-specific object model is identified in the namespace of the metadata repository associated with the client. According to these aspects, identification of the extension metadata comprises identification of the extension object model in the namespace of the metadata repository associated with the client based on the association to the extension object model included in the client-specific object model.

Claims

1. A computer-implemented method comprising:

receiving, from a client, a request for access to an instance of an object model;

identifying extension metadata associated with the object model and associated with the client in a metadata repository;

identifying client-independent metadata of the object model in the metadata repository;

merging the client-independent metadata and the extension metadata associated with the client to create a merged object model; and

accessing the instance based on the merged object model.

2. A method according to claim 1, wherein identifying client-independent metadata of the object model comprises:

identifying metadata associated with the object model and associated with a client-independent key in the metadata repository,

wherein identifying the extension metadata comprises;

identifying metadata associated with the object model and associated with a client key in the metadata repository, and

wherein the client key is associated with the client.

3. A method according to claim 1, further comprising storing the merged object model in a runtime metadata buffer.

4. A method according to claim 1, further comprising:

creating, in a namespace of the metadata repository associated with the client, an extension object model including the extension metadata associated with the object model;

creating, in the namespace of the metadata repository associated with the client, a client-specific object model associated with the object model and including an association to the extension object model; and

identifying, in response to the received request, the client-specific object model in the namespace of the metadata repository associated with the client, and

wherein identifying the extension metadata comprises identifying the extension object model in the namespace of the metadata repository associated with the client based on the association to the extension object model included in the client-specific object model.

5. A method according to claim 4, wherein identifying the client-independent metadata of the object model in the metadata repository comprises identifying the object model in a client-independent namespace of the metadata repository

6. A method according to claim 4,

wherein the object model is an instance of an object metadata model and the extension object model is an instance of an extension object metadata model, and

wherein the object metadata model and the extension object metadata model are instances of a same meta-metadata model.

7. A method according to claim 6,

wherein the client-specific object model is an instance of an object metadata model.

8. A system comprising:

a metadata repository;

a persistent storage to store instances of a plurality of object models;

executable program code of an application platform to;

receive, from a client, a request for access to an instance of an object model;

identify extension metadata associated with the object model and associated with the client in the metadata repository;

identify client-independent metadata of the object model in the metadata repository;

merge the client-independent metadata and the extension metadata associated with the client to create a merged object model; and

accessing the instance in the persistent storage based on the merged object model.

9. A system according to claim 8, wherein identification of the client-independent metadata of the object model comprises:

identification of metadata associated with the object model and associated with a client-independent key in the metadata repository,

wherein identification of the extension metadata comprises;

identification of metadata associated with the object model and associated with a client key in the metadata repository, and

wherein the client key is associated with the client.

10. A system according to claim 8, the application further to store the merged object model in a runtime metadata buffer.

11. A system according to claim 8, the application further to:

create, in a namespace of the metadata repository associated with the client, an extension object model including the extension metadata associated with the object model;

create, in the namespace of the metadata repository associated with the client, a client-specific object model associated with the object model and including an association to the extension object model; and

identify, in response to the received request, the client-specific object model in the namespace of the metadata repository associated with the client, and

wherein identification of the extension metadata comprises identification of the extension object model in the namespace of the metadata repository associated with the client based on the association to the extension object model included in the client-specific object model.

12. A system according to claim 11, wherein identification of the client-independent metadata of the object model in the metadata repository comprises identification of the object model in a client-independent namespace of the metadata repository

13. A system according to claim 11,

wherein the object model is an instance of an object metadata model and the extension object model is an instance of an extension object metadata model, and

wherein the object metadata model and the extension object metadata model are instances of a same meta-metadata model.

14. A system according to claim 13,

wherein the client-specific object model is an instance of an object metadata model.