Plug-in architecture of business intelligence platform using data source cartridges

Patent metadata

Field	Value
Publication number	US-10067978-B2
Application number	US-201414508148-A
Country	US
Kind code	B2
Filing date	Oct 7, 2014
Priority date	Oct 7, 2014
Publication date	Sep 4, 2018
Grant date	Sep 4, 2018

Abstract

Embodiments implement a plug-in architecture supporting adding new data sources to a federated database without the need to recode a federated database manager software module. The federated database manager software module includes a plug-in framework for interfacing with a data source cartridge. The data source cartridge supplies metadata including a feature table of a newly added data source to the framework and creates a physical query for the newly added data source based on an execution plan generated by the federated database manager software module. The data source cartridge returns the result set of the query of the new added data source to the federated database manager software module.

First claim

We claim:

1. A method performed by a federated data source manager functional component executed by a computer system, with the federated data source manager functional component configured to receive a logical query to a federated database, where the federated database aggregates a predetermined set of predetermined data sources into a logical model, the method comprising:
adding a new data source to the federated database, wherein the federated data source manager functional component includes separate gateways for each of the predetermined data sources;
plugging into a data source server that communicates with the federated data source, manager functional component, a new data source cartridge for the new data source;
retrieving, by the federated data source manager functional component, metadata from a data source cartridge, with the data source cartridge configured to supply metadata of an added date source associated with the data source cartridge, where the added data source is not included in the predetermined set of predetermined data sources;
generating physical execution plan, by the federated data source manager functional component and using at least a portion of the metadata retrieved from the data source cartridge, for the logical query with the physical execution plan including at least one query to the added date source;
providing, by the federated data source manager functional component, at least a part of the physical execution plan to the data source cartridge to facilitate generating a physical query, by the data source cartridge, to the added data source to implement the part of the physical execution plan, wherein the federated data source manager functional component does not include program code for generating a physical query to the added data source; and
receiving, by the federated data source manager functional component and from the data source cartridge, a result set from the physical query to the added data source, wherein the data source cartridge is used instead of a code generator, as execution engine, and one of the separate gateways of the federated data source manager functional component to provide the result set; and
using the code generator, the execution engine, and the separate gateways to provide result sets from the predetermined data sources.

2. The method of claim 1 wherein providing at least a part of the physical execution plan to the data source cartridge comprises:
transforming at least a portion of the physical execution plan to a first Extensible Markup Language (XML) representation.

3. The method of claim 2 wherein the added data source is a Java data source and further comprising:
transforming the first XML representation of the physical execution plan to a Java-side execution plan.

4. The method of claim 1 wherein retrieving metadata from the data source cartridge further comprises:
receiving a feature list of the added data source.

5. The method of claim 1 wherein retrieving metadata from the data source cartridge further comprises:
receiving metadata of a new connection pool type not supported by the federated data source manager functional component and wherein the physical execution plan includes at least one query utilizing the new connection pool type.

6. A method, performed by a plug-in framework functional component of a federated data source manager functional component executed by a computer system, wherein the federated data source manager functional component is configured to federate only a predetermined set of predetermined data sources into a federated database and includes an execution function component configured to generate physical queries to only data sources in the predetermined set and wherein the federated data source manager functional component includes an analytics component for creating a physical execution plan from a received logical query, the method comprising:
providing to the analytics component of the federated data source manager functional component, by the plug-in framework functional component, metadata of an added data source received from a data source cartridge associated with the added data source, where the added data source is not included in the predetermined set of predetermined data sources and where the analytics component of the federated data source manager functional component is configured to utilize the metadata to generate the physical execution plan including the added data source, wherein the federated data source manager functional component includes separate gateways for each of the predetermined data sources and wherein the data source cartridge was plugged into a data source server that communicates with the federated data source manager functional component, and communicates with the added data sources via the data source cartridge;
receiving, by the plug-in framework functional component, the physical execution plan from the analytics component;
transferring, by the plug-in framework functional component, at least a part of the physical execution plan to the data source cartridge, wherein the data source cartridge is configured to generate a physical query to the added data source based on the part of the physical execution plan;
receiving, by the plug-in framework functional component, a result set from the data source cartridge, with the result set being a response from the added data source to the physical query, wherein the data source cartridge is used instead of a code generator, an execution engine, and one of the separate gateways of the federated data source manager functional component to provide the result set and wherein the federated data source manager functional component uses the separate gateways, the code generator, and the execution engine to provide result sets from the predetermined data sources; and
transferring, by the plug-in framework functional component, the result set to the analytics component to facilitate the generation of a response to the logical query.

7. The method of claim 6 further comprising:
transforming, by the plug-in framework functional component, at least a portion of the physical execution plan to a first Extensible Markup Language (XML) representation.

8. The method of claim 7 wherein the added data source is a Java data source and further comprising:
transforming the first XML representation of the physical execution plan to a Java-side execution plan.

9. The method of claim 6 wherein providing metadata received from the data source cartridge further comprises:
providing a feature list of the added data source.

10. The method of claim 6 wherein providing metadata received from the data source cartridge further comprises:
providing metadata of a new connection pool type not supported by the federated data source manager functional component and wherein the physical execution plan includes at least one query utilizing the new connection pool type.

11. A method, performed by a data source plug-in component executed by a data source server, with the data source plug-in component associated with an added data source that is not supported by native code of a federated data source manager, the method comprising:
outputting, by the data source plug-in component, metadata of the added data source to be used by the federated data source manager to construct a logical query including the added data source, wherein the federated data source manager includes separate gateways for each of predetermined data sources and wherein the data source plug-in component was plugged into the data source server that communicates with the federated data source manager, and communicates with the added data sources via the data source plu

Assignees

• Oracle Int Corp

Inventors

• Park Hoyong
• Bolsius Roger
• Dhakar Ashok Kumar
• Velusamy Muthukumar

Classifications

• G06F16/256

  in federated or virtual databases · CPC title

• G06F16/24542 Primary

  Plan optimisation · CPC title

• G06Q10/06

  Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling · CPC title

• G06F16/24534

  Query rewriting; Transformation · CPC title

• G06F17/30448

  Physics · mapped topic