Providing cloud-based, generic OData mashup services using an on-demand service
View Patent ↗The present disclosure describes methods, systems, and computer program products for providing cloud-based, generic OData mashup services. One computer-implemented method includes parsing a received a request for service-related data to determine a subject mashup service associated with the request, retrieving a subject mashup service definition from a service repository, retrieving subservice definitions associated with the subject mashup service definition, instantiating subservices with a computer using the subservice definitions, and transmitting a request to retrieve the service-related data from the instantiated subservices.
1. A computer-implemented method comprising:
parsing a received request for service-related data to generate a lookup key used to determine a subject mashup service to service the request;
retrieving a subject mashup service definition from an entry in a service repository, wherein the mashup service definition is identified using the lookup key which includes a namespace, a service name, and a service version;
retrieving a generic mashup service provider registered in the service repository entry;
identifying, using the generic mashup service provider, a mashup subservice factory needed for instantiation and initialization of a generic entity data model (EDM) provider used to instantiate the subject mashup service;
retrieving, using the generic mashup service provider, subservice definitions of subservices associated with the subject mashup service definition;
instantiating, using a computer and the mashup subservice factory, subservices using the subservice definitions; and
transmitting a request to the generic mashup service provider to retrieve the service-related data from the instantiated subservices.
2. The method of claim 1 , comprising instantiating the subject mashup service using the generic EDM provider.
3. The method of claim 2 , further comprising the generic EDM provider transmitting a request to a mashup service repository for a service definition of the subject mashup service.
4. The method of claim 1 , further comprising formatting a service document responsive to the request for service related data, the service document formatted from entity types returned in response to the request to retrieve the service-related data from the instantiated sub services.
5. The method of claim 1 , further comprising instantiating a mashup processor following the instantiation of the subservices associated with the subject mashup service.
6. The method of claim 5 , further comprising transmitting a request to the mashup processor for a read feed using a received entity type returned in response to the request to retrieve the service-related data from the instantiated subservices.
7. The method of claim 6 , further comprising creating a read feed response responsive to the request for service-related data.
8. A non-transitory, computer-readable medium storing computer-readable instructions executable by a computer and operable to:
parse a received request for service-related data to generate a lookup key used to determine a subject mashup service to service the request;
retrieve a subject mashup service definition from an entry in a service repository, wherein the mashup service definition is identified using the lookup key which includes a namespace, a service name, and a service version;
retrieve a generic mashup service provider registered in the service repository entry;
identify, using the generic mashup service provider, a mashup subservice factory needed for instantiation and initialization of a generic entity data model (EDM) provider used to instantiate the subject mashup service;
retrieve, using the generic mashup service provider, subservice definitions of subservices associated with the subject mashup service definition;
instantiate, using the mashup subservice factory, subservices using the subservice definitions; and
transmit a request to the generic mashup service provider to retrieve the service-related data from the instantiated subservices.
9. The medium of claim 8 , comprising computer-readable instructions to instantiate the subject mashup service using the generic EDM provider.
10. The medium of claim 9 , further comprising instructions operable to instruct the generic EDM provider to transmit a request to a mashup service repository for a service definition of the subject mashup service.
11. The medium of claim 8 , further comprising instructions operable to format a service document responsive to the request for service related data, the service document formatted from entity types returned in response to the request to retrieve the service-related data from the instantiated subservices.
12. The medium of claim 8 , further comprising instructions operable to instantiate a mashup processor following the instantiation of the subservices associated with the subject mashup service.
13. The medium of claim 12 , further comprising instructions operable to transmit a request to the mashup processor for a read feed using a received entity type returned in response to the request to retrieve the service-related data from the instantiated subservices.
14. The medium of claim 13 , further comprising instructions operable to create a read feed response responsive to the request for service-related data.
15. A system, comprising:
a memory;
at least one computer interoperably coupled with the memory and configured to:
parse a received request for service-related data to generate a lookup key used to determine a subject mashup service to service the request;
retrieve a subject mashup service definition from an entry in a service repository, wherein the mashup service definition is identified using the lookup key which includes a namespace, a service name, and a service version;
retrieve a generic mashup service provider registered in the service repository entry;
identify, using the generic mashup service provider, a mashup subservice factory needed for instantiation and initialization of a generic entity data model (EDM) provider used to instantiate the subject mashup service;
retrieve, using the generic mashup service provider, subservice definitions of subservices associated with the subject mashup service definition;
instantiate, using the mashup subservice factory, subservices using the subservice definitions; and
transmit a request to the generic mashup service provider to retrieve the service-related data from the instantiated subservices.
16. The system of claim 15 , configured to instantiate the subject mashup service using the generic EDM provider.
17. The system of claim 16 , further configured to instruct the generic EDM provider to transmit a request to a mashup service repository for a service definition of the subject mashup service.
18. The system of claim 15 , further configured to format a service document responsive to the request for service related data, the service document formatted from entity types returned in response to the request to retrieve the service-related data from the instantiated sub services.
19. The system of claim 15 , further configured to instantiate a mashup processor following the instantiation of the subservices associated with the subject mashup service.
20. The system of claim 19 , further configured to transmit a request to the mashup processor for a read feed using a received entity type returned in response to the request to retrieve the service-related data from the instantiated subservices.
21. The system of claim 20 , further configured to create a read feed response responsive to the request for service-related data.