Uniform access to entities in registered data store services
First Claim
1. At least one computer-readable storage medium having instructions stored thereon, which when executed by a processing system in conjunction with an application program, allow the application program to access a data store service catalog system maintained for one or more registered data store services of varying types, the instructions comprising:
- executing the data store service catalog system, which comprises a metadata application programming interface (API), a service execution API, and metadata describing the data store services, entities thereof, and associations between same types of entities in different types of data store services and between different types of entities in same types of data store services, the metadata also identifying methods that can be submitted to the service execution API that will invoke operations in the different types of data store services to perform the methods;
receiving, via the metadata API, a request for at least a portion of the metadata describing the one or more registered data store services and returning, via the API, the requested metadata to the client;
receiving from the client, via the metadata API, a request comprising indicia of one of the registered data store services returned to the client, and in response returning, via the metadata API, metadata identifying and describing entities stored by the different types of data services;
receiving from the client, via the metadata API, a request comprising indicia of a first one of the identified entities, the first entity being of a first entity type and residing in a first type of data service, and responding, via the metadata API, by using the metadata to identify other entities of the first entity type that reside in a second type of data service; and
receiving from the client, via the service execution API, a request comprising methods derived from the metadata to access metadata of the first entity and the second entity, wherein the data store service catalog translates the request to a form native to the first and second types of data service, communicates the translated request to the first and second types of data service, receives results therefrom, and returns the results to the client through the service execution API.
2 Assignments
0 Petitions
Accused Products
Abstract
A data store catalogue service model is disclosed for exposing disparate data store services to clients without requiring explicit knowledge on how to interact with each disparate service. The data store catalogue service model may maintain interaction details for each data store service that clients may access for interacting with those services. The model may also maintain metadata that may describe the different types of services available for access by clients, the data types used by those services, how to access the data provided by the services, and how to communicate semantically with the services for accessing the service'"'"'s data. Additionally, the data store may include metadata that enables clients to interact with one or more registered data stores in a number of ways, such as for discovering registered data store services, entities, classes, and/or any associations between related entities within the same or among disparate services.
27 Citations
13 Claims
-
1. At least one computer-readable storage medium having instructions stored thereon, which when executed by a processing system in conjunction with an application program, allow the application program to access a data store service catalog system maintained for one or more registered data store services of varying types, the instructions comprising:
-
executing the data store service catalog system, which comprises a metadata application programming interface (API), a service execution API, and metadata describing the data store services, entities thereof, and associations between same types of entities in different types of data store services and between different types of entities in same types of data store services, the metadata also identifying methods that can be submitted to the service execution API that will invoke operations in the different types of data store services to perform the methods; receiving, via the metadata API, a request for at least a portion of the metadata describing the one or more registered data store services and returning, via the API, the requested metadata to the client; receiving from the client, via the metadata API, a request comprising indicia of one of the registered data store services returned to the client, and in response returning, via the metadata API, metadata identifying and describing entities stored by the different types of data services; receiving from the client, via the metadata API, a request comprising indicia of a first one of the identified entities, the first entity being of a first entity type and residing in a first type of data service, and responding, via the metadata API, by using the metadata to identify other entities of the first entity type that reside in a second type of data service; and receiving from the client, via the service execution API, a request comprising methods derived from the metadata to access metadata of the first entity and the second entity, wherein the data store service catalog translates the request to a form native to the first and second types of data service, communicates the translated request to the first and second types of data service, receives results therefrom, and returns the results to the client through the service execution API. - View Dependent Claims (2, 3, 13)
-
-
4. At least one computer-readable storage medium having instructions stored thereon, which when executed by a processing system, cause the processing system to perform a process comprising:
-
providing, via a metadata application programming interface (API), metadata maintained for one or more registered data store services of varying types, where the metadata enables interacting with the registered data store services, the metadata describing the data store services, entities thereof, and associations between same types of entities in different types of data store services and between different types of entities in same types of data store services, the metadata also identifying methods that can be submitted to a service execution API that will invoke operations in the different types of data store services to perform the methods; responsive to a request via the metadata API from a client, using the metadata to identify to the client a first and second of the registered data store services maintained in a data store service registration repository that are associated with the request, where the first data store service is a different type of data store service than the second data store service; and responsive to a request via the metadata API from the client, providing at least a portion of the metadata associated with the first and second identified data store services that is used by the client to submit a request to the execution service API, and at least one server implements the request by translating it to a request to both the first and second data store services and by translating records of same types of entities from the first and second data store services to a common format to be returned to the client. - View Dependent Claims (5, 6, 7, 8, 9)
-
-
10. A computing device to serve as a catalog of LOB system instances, the computing device comprising metadata, one or modules configured to perform a process, the computing device comprising:
storage storing the metadata, the metadata comprising; first metadata identifying different instances of LOB systems and respective types of the instances of LOB systems, where some instances of LOB systems are different instances of a same type of LOB system, and some instances of LOB systems are instances of different types of LOB systems; second metadata describing types of entities stored by and available from the LOB system instances, where metadata of an entity has data linking it to an instance of an LOB system identified in the first metadata, and where metadata of an entity has data identifying what type of entity it is; third metadata identifying different methods and respective parameters thereof for accessing the entities, where the third metadata links the methods to respective entities described in the second metadata, and where a method linked to an entity comprises a method for retrieving corresponding data in the entity'"'"'s linked LOB system that; fourth metadata comprising first associations, where a first association comprises an association between a first entity and a second entity that are both linked to a same type of LOB instance, the two entities comprising different entity types, where the first association also identifies a method of the corresponding LOB system instance that can be used to retrieve a plurality of entities of the second type that are associated with an entity of the first type; and fifth metadata comprising second associations, where a second association comprises an association between a third entity and a fourth entity, the third and fourth entities being linked, respectively, to instances of different types of LOB system instances, the third and fourth entities comprising entities of a same entity type that is found in each of different types of LOB system instances. - View Dependent Claims (11, 12)
Specification