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

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 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 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;
• 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;
• 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.

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;
• receiving, by the data source plug-in component, part of a physical execution plan generated by the federated data source manager, with the part of the physical execution plan including at least one query to the added data source;
• generating, by the data source plug-in component, a physical query to the added data source based on the part of the physical execution plan;
• and
• returning, by the data source plug-in component, a result set to the federated data source manager in response to the physical query.

A method, performed by a connection pool plug-in component executed by a data source server, with the connection pool plug-in component associated with an added connection pool type that is not supported by native code of a federated data source manager, the method comprising:

• outputting, by the connection pool plug-in component, metadata of the added connection pool type to be used by the federated data source manager to construct a logical query utilizing the added connection pool type;
• receiving, by the connection pool plug-in component, part of a physical execution plan generated by the federated data source manager, with the part of the physical execution plan requiring the added connection pool type;
• generating, by the connection pool plug-in component, a physical query using the added connection pool type and based on the part of the physical execution plan;
• and
• returning to the federated data source manager, by the connection pool plug-in component, a result set using the added connection pool type.

A computer system including one or more processors configured to execute federated data source manager program code, wherein the computer system is configured to receive a logical query to a federated database, wherein the federated database aggregates a predetermined set of data sources into a logical model and with the federated data source manager program code, when executed by the one or more processors, causing the computer system to perform the steps of:

• retrieving metadata from a data source cartridge, with the data source cartridge configured to supply metadata of an added data source associated with the data source cartridge, where the added data source is not included in the predetermined set of data sources;
• generating a physical execution plan, 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 data source;
• providing 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;
• receiving, from the data source cartridge, a result set from the physical query to the added data source;
• and
• wherein the federated data source manager program code does not include program code for generating a physical query to the added data source.

A computer system including one or more processors configured to execute plug-in framework program code, wherein a federated data source manager functional component is configured to federate only a predetermined set of 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, with the plug-in framework program code, when executed by the one or more processors, causing the computer system to perform the steps of:

• providing to the analytics component of the federated data source manager 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 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;
• receiving the physical execution plan from the analytics component;
• transferring 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 a result set from the data source cartridge, with the result set being a response from the added data source to the physical query;
• and
• transferring the result set to the analytics component to facilitate the generation of a response to the logical query.

A computer system including one or more processors configured to execute data source plug-in component program code, wherein the data source plug-in component program code is associated with an added data source that is not supported by native code of a federated data source manager and with the data source plug-in component program code, when executed by the one or more processors, causing the computer system to perform the steps of:

• outputting 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;
• receiving part of a physical execution plan generated by the federated data source manager, with the part of the physical execution plan including at least one query to the added data source;
• generating a physical query to the added data source based on the part of the physical execution plan;
• and
• returning a result set to the federated data source manager in response to the physical query.

A computer system including one or more processors configured to execute connection pool plug-in component program code, wherein the connection pool plug-in component is associated with an added connection pool type that is not supported by native code of a federated data source manager and with the connection pool plug-in component program code, when executed by the one or more processors, causing the computer system to perform the steps of:

• outputting metadata of the added connection pool type to be used by the federated data source manager to construct a logical query utilizing the added connection pool type;
• receiving part of a physical execution plan generated by the federated data source manager, with the part of the physical execution plan requiring the added connection pool type;
• generating a physical query using the added connection pool type and based on the part of the physical execution plan;
• and
• returning to the federated data source manager a result set using the added connection pool type.