System and method for providing data flexibility in a business intelligence server using an administration tool

• US 10,437,846 B2
• Filed: 05/03/2011
• Issued: 10/08/2019
• Est. Priority Date: 05/28/2010
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Venkatasubramanian, Raghuram, Bolsius, Roger, Pan, Harvard, Mascarenhas, Alextair, Chowdhury, Saugata, Surendran, Venugopal, Venkata, Ananth, Vigeant, Jacques
• Primary Examiner(s): Shanmugasundaram, Kannan
• Application Number:
  US13/100,245
• Publication Number:
  US 20110295793A1
• Time in Patent Office: 3,080 Days
• Field of Search: 707602
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/283 Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP

Abstract

An administration tool can be used to provide data flexibility in a business intelligence (BI) server that is associated with a data warehouse. The administration tool can display one or more data objects that are adapted to be imported from an application framework into a physical model maintained on the BI server. The administration tool can further map the one or more data objects in the physical model into a logical model, also maintained on the BI server, which corresponds to at least one target table in the data warehouse. Additionally, the administration tool can publish an extension input to an extender associated with the data warehouse based on the logical model, wherein the extender operates to generate one or more metadata extensions based on the extension input.

Claims

1. A method for providing data flexibility in a business intelligence (BI) server associated with a data warehouse, comprising:

providing an administration tool on a BI server between an application framework and a data warehouse,

wherein a definition of the data warehouse is stored in a repository model,

wherein the application framework implements a plurality of different types of BI applications and comprises a plurality of data objects, and

wherein each data object is associated with one or more of a plurality of data sources associated with the plurality of BI applications, and comprises a query that fetches a record from the one or more data sources and an implementation logic configured to manipulate the record fetched by the query;

providing, on the administration tool, a physical model and a logical model,

wherein the physical model defines relationships between the plurality of data sources, and

wherein the logical model defines data in the data warehouse and corresponds to one or more target tables in the data warehouse,

importing the plurality of data objects into the physical model;

mapping the physical model to the logical model based on a rule encapsulating an input/output mechanism comprising an input received by the BI server from an associated user of the BI server, the input comprising one or more customized mappings selected by the associated user of the BI server;

detecting, via the administration tool, changes in one or more of the plurality of imported data objects based on an output of the input/output mechanism, wherein the detected changes comprise one or more elements selected from the group consisting of modifying attributes of a data object, adding a data object, and deleting a data object;

updating the logical model in the administration tool, with the detected changes;

publishing the detected changes to an extender associated with the data warehouse, wherein the extender operates to

read extract, transform and load (ETL) metadata from a metadata service,

extend the ETL metadata by applying the detected changes thereto, and

invoke an implementation module associated with the data warehouse to update at least one of the target tables in the data warehouse using the extended ETL metadata;

generating, by the extender, an XML output document that contains information on tables created, modified, or searched in the data warehouse by the implementation module, and information on columns, keys and references associated with the tables created, modified or searched; and

providing the XML output document to the administration tool, wherein the XML output document is configured to be used by the administration tool to modify the definition of the data warehouse stored in the repository mode.

2. The method according to claim 1, further comprising:

displaying at least one data source associated with the application framework in a connection pool.

3. The method according to claim 1, wherein:

the one or more data objects are view objects (VOs); and

the rule comprises logic for mapping the physical model to the logical model comprising;

loop through the source physical objects to determine if any of the source physical objects apply to the target logical object;

selectively modify objects that can be modified;

selectively create new objects for objects that cannot be modified; and

pass along the objects to the next rule that should be run.

4. The method according to claim 1, further comprising:

processing incremental changes in the one or more data objects.

5. The method according to claim 1, further comprising:

dragging and dropping, via the administration tool, the one or more data objects from the physical model into the logical model.

6. The method according to claim 1, further comprising:

passing one or more authentication token from the administration tool to the extender.

7. The method according to claim 1, wherein the extender uses one or more templates to extend the data warehouse.

8. The method according to claim 1, wherein the extender receives an extension input that specifies both source end points and target end points, wherein the target end point describes target tables that needs to be extended, and the source end point describes data that needs to be loaded in the target tables.

9. The method according to claim 8, further comprising:

transforming the extension input into a format that is acceptable by the extender.

10. The method according to claim 1, wherein the extender includes one or more target tables in the data warehouse based on the one or more data objects.

11. The method according to claim 1, further comprising

using a framework to encapsulate rules for metadata conversions between the physical layer and the logical layer.

12. A system for providing data flexibility in a business intelligence (BI) server associated with a data warehouse, comprising:

one or more microprocessors;

a BI server running on the one or more microprocessors, wherein the BI server resides between an application framework and a data warehouse,

wherein a definition of the data warehouse is stored in a repository model,

wherein the application framework implements a plurality of different types of BI applications and comprises a plurality of data objects, and

wherein each data object is associated with one or more of a plurality of data sources associated with the plurality of BI applications, and comprises a query that fetches a record from the one or more data sources and an implementation logic configured to manipulate the record fetched by the query;

an administration tool on the BI server, wherein the administration tool comprises a physical model and a logical model,

wherein the physical model defines relationships between the plurality of data sources,

wherein the logical model defines data in the data warehouse and corresponds to one or more target tables in the data warehouse, and

wherein the administration tool is configured to

import the plurality of data objects into the physical model from the application framework,

map the physical model to the logical model based on a rule encapsulating an input/output mechanism comprising an input received by the BI server from an associated user of the BI server, the input comprising one or more customized mappings selected by the associated user of the BI server,

detect changes in one or more of the plurality of imported data objects based on an output of the input/output mechanism, wherein the detected changes comprise one or more elements selected from the group consisting of modifying attributes of a data object, adding a data object, and deleting a data object, and

update the logical model in the administration tool, with the detected changes; and

an extender, associated with the data warehouse, that operates to

receive a publication of the changes in the one or more data objects detected by the administration tool,

read extract, transform and load (ETL) metadata from a metadata service,

extend the ETL metadata by applying the detected changes thereto, and

invoke an implementation module associated with the data warehouse to update at least one of the target tables in the data warehouse using the extended ETL metadata,

wherein the extender generates an XML output document that contains information on tables created, modified, or searched in the data warehouse by the implementation module, and information on columns, keys and references associated with the tables created, modified or searched, and

wherein the extender provides the XML output document to the administration tool, wherein the XML output document is configured to be used by the administration tool to modify the definition of the data warehouse stored in the repository mode.

13. The system according to claim 12, further comprising one or more authentication tokens that are passed from the administration tool to the extender.

14. The system according to claim 12, wherein the detected changes are transformed into a format that is acceptable by the extender.

15. The system of according to claim 12, wherein the extender uses one or more templates to extend the data warehouse.

16. The system of according to claim 12, wherein the extender receives an extension input that specifies both source end points and target end points, wherein the target end point describes target tables that needs to be extended, and the source end point describes data that needs to be loaded in the target tables.

17. A non-transitory machine readable storage medium having instructions stored thereon that when executed cause a system to perform a method comprising:

providing an administration tool on a BI server between an application framework and a data warehouse,

wherein a definition of the data warehouse is stored in a repository model,

wherein the application framework implements a plurality of different types of BI applications and comprises a plurality of data objects, and

wherein each data object is associated with one or more of a plurality of data sources associated with the plurality of BI applications, and comprises a query that fetches a record from the one or more data sources and an implementation logic configured to manipulate the record fetched by the query;

providing, on the administration tool, a physical model and a logical model,

wherein the physical model defines relationships between the plurality of data sources, and

wherein the logical model defines data in the data warehouse and corresponds to one or more target tables in the data warehouse, and

importing the plurality of data objects into the physical model;

mapping the physical model to the logical model based on a rule encapsulating an input/output mechanism comprising an input received by the BI server from an associated user of the BI server, the input comprising one or more customized mappings selected by the associated user of the BI server;

detecting, via the administration tool, changes in one or more of the plurality of imported data objects based on an output of the input/output mechanism, wherein the detected changes comprise one or more elements selected from the group consisting of modifying attributes of a data object, adding a data object, and deleting a data object;

updating the logical model in the administration tool, with the detected changes;

publishing the detected changes to an extender associated with the data warehouse, wherein the extender operates to

read extract, transform and load (ETL) metadata from a metadata service,

extend the ETL metadata by applying the detected changes thereto, and

invoke an implementation module associated with the data warehouse to update at least one of the target tables in the data warehouse using the extended ETL metadata;

generating, by the extender, an XML output document that contains information on tables created, modified, or searched in the data warehouse by the implementation module, and information on columns, keys and references associated with the tables created, modified or searched; and

providing the XML output document to the administration tool, wherein the XML output document is configured to be used by the administration tool to modify the definition of the data warehouse stored in the repository mode.

18. The non-transitory machine readable storage medium according to claim 17, wherein the detected changes are transformed into a format that is acceptable by the extender.

19. The non-transitory machine readable storage medium according to claim 17, wherein the extender uses one or more templates to extend the data warehouse.

20. The non-transitory machine readable storage medium according to claim 17, wherein the extender receives an extension input that specifies both source end points and target end points, wherein the target end point describes target tables that needs to be extended, and the source end point describes data that needs to be loaded in the target tables.