Administrative tool and physical execution plan interface for plug-in architecture of business intelligence platform using data source cartridges

• US 10,108,744 B2
• Filed: 03/31/2015
• Issued: 10/23/2018
• Est. Priority Date: 10/07/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Park, Hoyong, Bolsius, Roger, Dhakar, Ashok Kumar, Velusamy, Muthukumar
• Primary Examiner(s): Bowen, Richard
• Application Number:
  US14/675,628
• Publication Number:
  US 20160098492A1
• Time in Patent Office: 1,302 Days
• CPC Class Codes: G06F 16/8365 Query optimisation
• CPC Class Codes: G06F 16/8373 Query execution

Abstract

Embodiments implement a plug-in architecture supporting adding new data sources to a legacy federated database without the need to recode a federated database manager software module. The federated database manager software module includes an administrative tool and 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 administrative tool generates presentation panes including new data sources added to the legacy federated database.

Claims

1. A method performed by a federated database manager functional component executed by a computer system, where the federated database manager functional component includes a code generation functional component and a framework functional component, the method comprising:

receiving, by the federated database manager functional component, a logical query to an updated federated database where the updated federated database includes a legacy federated database of data sources and an added data source not included in the legacy federated database;

retrieving, by the framework functional component, metadata from a data source cartridge functional component associated with the added data source, wherein the metadata includes a feature table and configuration parameters of a plug-in framework model and wherein a different type of data source cartridge functional component is used for different types of added data sources;

generating, by the federated database manager functional component and using at least a portion of the metadata retrieved from the data source cartridge functional component, a physical execution plan for the logical query with the physical execution plan including at least one logical query to the added data source;

processing, by the code generation functional component, the physical execution plan to produce physical queries in native form to communicate with data sources in the legacy federated database;

branching, by the federated database manager functional component, the at least one logical query to the added data source to the framework functional component which converts a branched logical query to an extensible markup language (XML) representation; and

transferring, by the framework functional component, the XML representation to the data source cartridge functional component which processes the XML representation to produce a physical query in native form to the added data source.

2. The method of claim 1 further comprising:

receiving, by the federated database manager functional component and from the data source cartridge functional component, a result set from the physical query to the added data source.

3. A computer system including one or more processors configured to execute federated database manager functional program code, where the federated database manager functional program code includes a code generation functional component and a framework functional component, with the federated database manager functional program code, when executed by the one or more processors, causing the computer system to perform the steps of:

receiving, by the federated database manager functional program code, a logical query to an updated federated database where the updated federated database includes a legacy federated database of data sources and an added data source not included in the legacy federated database;

retrieving, by the framework functional component, metadata from a data source cartridge functional component associated with the added data source, wherein the metadata includes a feature table and configuration parameters of a plug-in framework model and wherein a different type of data source cartridge functional component is used for different types of added data sources;

generating, by the federated database manager functional program code and using at least a portion of the metadata retrieved from the data source cartridge functional component, a physical execution plan for the logical query with the physical execution plan including at least one logical query to the added data source;

processing, by the code generation functional component, the physical execution plan to produce physical queries in native form to communicate with data sources in the legacy federated database;

branching, by the federated database manager functional program code, the at least one logical query to the added data source to the framework functional component which converts a branched logical query to an extensible markup language (XML) representation; and

transferring, by the framework functional component, the XML representation to the data source cartridge functional component which processes the XML representation to produce a physical query in native form to the added data source.

4. The computer system of claim 3 with the federated database manager functional program code, when executed by the one or more processors, further causing the computer system to perform the step of:

receiving, from the data source cartridge functional component, a result set from the physical query to the added data source.

5. A method performed by a federated database manager functional component executed by a computer system, where an updated federated database includes a legacy federated database of data sources and an added data source not included in the legacy federated database, where, the method comprising:

providing the federated database manager functional component that includes an administrative tool functional component having a file layer representing tables and columns of data sources in the legacy federated database and a framework functional component;

retrieving, by the framework functional component, metadata of the added data source from a data source cartridge functional component associated with the added data source wherein a different type of data source cartridge functional component is used for different types of added data sources;

updating, by the administrative tool functional component, the file layer to include the metadata of the added data source; and

presenting, by the administrative tool functional component, tables and columns of data sources included in both the legacy federated database and the added data source.

6. The method of claim 5 with presenting further comprising:

presenting, by the administrative tool functional component, a physical presentation pane, depicting the physical structure of the updated federated database.

7. The method of claim 5 with presenting further comprising:

presenting, by the administrative tool functional component, a logical presentation pane depicting the logical structure of the updated federated database.

8. A computer system including one or more processors configured to execute federated database manager functional program code, where an updated federated database includes a legacy federated database of data sources and an added data source not included in the legacy federated database, where the federated database manager functional program code includes an administrative tool functional component having a file layer representing tables and columns of data sources in the legacy federated database and a framework functional component, with the federated database manager functional program code, when executed by the one or more processors, causing the computer system to perform the steps of:

retrieving, by the framework functional component, metadata of the added data source from a data source cartridge functional component associated with the added data source;

updating, by the administrative tool functional component, the file layer to include the metadata of the added data source; and

presenting, by the administrative tool functional component, tables and columns of data sources included in both the legacy federated database and the added data source.

9. The computer system of claim 8 with the federated database functional code, when executed by the one or more processors, causing the computer to perform the step of:

presenting, by the administrative tool functional component, a physical presentation pane depicting the physical structure of the updated federated database.

10. The computer system of claim 8 with the federated database manager functional program code, when executed by the one or more processors, further causing the computer system to perform the step of:

presenting, by the administrative tool functional component, a logical presentation pane depicting the logical structure of the updated federated database.

11. One or more non-transitory computer readable storage media storing federated database manager functional program code for execution by one or more processors, where the federated database manager functional program code includes a code generation functional component and a framework functional component, where the federated database manager functional program code, when executed by the one or more processors, performs the following acts:

receiving, by the federated database manager functional program code, a logical query to an updated federated database where the updated federated database includes a legacy federated database of data sources and an added data source not included in the legacy federated database;

retrieving, by the framework functional component, metadata from a data source cartridge functional component associated with the added data source, wherein the metadata includes a feature table and configuration parameters of a plug-in framework model and wherein a different type of data source cartridge functional component is used for different types of added data sources;

generating, by the federated database manager functional program code and using at least a portion of the metadata retrieved from the data source cartridge functional component, a physical execution plan for the logical query with the physical execution plan including at least one logical query to the added data source;

processing, by the code generation functional component, the physical execution plan to produce physical queries in native form to communicate with data sources in the legacy federated database;

branching, by the federated database manager functional program code, the at least one logical query to the added data source to the framework functional component which converts a branched logical query to an extensible markup language (XML) representation; and

transferring, by the framework functional component, the XML representation to the data source cartridge functional component which processes the XML representation to produce a physical query in native form to the added data source.