System and method for specifying metadata extension input for extending data warehouse

• US 9,535,965 B2
• Filed: 05/03/2011
• Issued: 01/03/2017
• 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): Saeed, Usmaan
• Assistant Examiner(s): WILLIS, AMANDA LYNN
• Application Number:
  US13/100,248
• Publication Number:
  US 20110295791A1
• Time in Patent Office: 2,072 Days
• Field of Search: 707/E17.018, 707/999.003, 707/802, 707/E17.014, 707/620, 707/694, 707/770, 707/E17.002, 707/E17.005, 707/E17.03, 707/E17.032, 707/E17.044, 707/600, 707/736, 707/769, 707/966, 707/999.101, 707/999.104, 707/999.107, 707/602
• US Class Current: 1/1
• 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 input extension specification can be generated, via an administration tool on a business intelligence (BI) server, for an extender associated with a data warehouse in order to extend the data warehouse. The administration tool can request for data flow information of the data warehouse from the extender. The data flow information indicates the mapping relationship between one or more source data objects and one or more target tables in the data warehouse. The administration tool further allows a user to select said one or more target tables in the data warehouse to be extended based on the data flow information, and builds the input extension specification for the extender.

Claims

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

providing an extender associated with a data warehouse, wherein the extender is implemented in Java and wrapped by a remote service, and communicates with an administration tool on the BI server through a Java host;

providing, from the extender, data flow information to the administration tool, wherein the data flow information includes dependencies between target tables in the data warehouse, and specifies mapping relationships between a plurality of source data objects and the target tables in the data warehouse;

receiving, from the administration tool, an input extension specification that includes one or more changes in the source data object, and one or more target tables to be extended using the one or more changes, wherein the input extension specification is constructed by the administration tool based on the one or more changes and the data flow information, wherein the extender receives the input extension specification as values of a plurality of input parameters of a function call from a Java client, which forwards the function call from the Java host in response to the administration tool making a call to the remote service through the Java host;

retrieving, via the extender, a metadata for a repository model of the data warehouse, and an extract, transform and load (ETL) metadata for the data warehouse, from a metadata server associated with the BI server;

extending the ETL metadata using the input extension specification and the metadata for the repository model of the data warehouse;

invoking, via the extender, an implementation module specific to the data warehouse to extend the one or more target tables in accordance with the extended ETL metadata;

generating, by the extender, an 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 output document to the administration tool, wherein the output document is configured to be used by the administration tool to modify the repository model of the data warehouse stored in the metadata service.

2. The method according to claim 1, wherein the data flow is generated by the extender that

receives a source data store document, and tracks data flows from source data objects defined in the source data store document towards one or more target tables in the data warehouse, or

receives a data warehouse document, and obtains data flow from one or more source data objects that result in a particular target table defined in the data warehouse document.

3. The method according to claim 1, wherein the data flow information is represented in an XML file.

4. The method according to claim 1, wherein the input extension specification specifies information on one or more dimensions before specifying information on one or more facts in physical repositories associated with the one or more target tables.

5. The method according to claim 1, wherein the input extension specification separates specifications for key and descriptive flex associated with the one or more table tables.

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

using the input extension specification to perform at least one of;

creating a new flex based dimension,

creating a new foreign key on a dimension,

providing a fact with a new foreign key to a dimension,

providing a fact with new attributes, and

propagating extension changes to post load process facts.

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

using a container-mapping configuration to restrict a scope of extension to the particular warehouse.

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

one or more microprocessors;

an administration tool on the BI server, running on the one or more microprocessors,

an extender associated with the data warehouse, wherein the extender is implemented in Java and wrapped by a remote service, and communicates with an administration tool on the BI server through a Java host, and wherein the extender operates to

provide data flow information to the administration tool, wherein the data flow information includes dependencies between target tables in the data warehouse and, and specifies mapping relationships between a plurality of source data objects and the target tables in the data warehouse;

receive, from the administration tool, an input extension specification that includes one or more changes in the source data object, and one or more target tables to be extended using the one or more changes, wherein the input extension specification is constructed by the administration tool based on the one or more changes and the data flow information, wherein the extender receives the input extension specification as values of a plurality of input parameters of a function call from a Java client, which forwards the function call from the Java host in response to the administration tool making a call to the remote service through the Java host;

retrieve, via the extender, a metadata for a repository model of the data warehouse, and an extract, transform and load (ETL) metadata for the data warehouse, from a metadata server associated with the BI server;

extend the ETL metadata using the input extension specification and the metadata for the repository model of the data warehouse;

invoke, via the extender, an implementation module specific to the data warehouse to extend the one or more target tables in accordance with the extended ETL metadata;

generate, by the extender, an 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

provide the output document to the administration tool, wherein the output document is configured to be used by the administration tool to modify the repository model of the data warehouse stored in the metadata service.

9. The system according to claim 8, wherein the data flow information is generated by the extender that receives a source data store document, and tracks data flows from source data objects defined in the source data store document towards one or more target tables in the data warehouse, or receives a data warehouse document, and obtains data flow from one or more source data objects that result in a particular target table defined in the data warehouse document.

10. The system according to claim 8, wherein the data flow information is represented in an XML file.

11. The system according to claim 8, wherein the input extension specification specifies—

information on one or more dimensions before specifying information on one or more facts in physical repositories associated with the one or more target tables.

12. The system according to claim 8, wherein the input extension specification separates specifications for key and descriptive flex associated with the one or more table tables.

13. The system according to claim 8, further comprising:

using the input extension specification to perform at least one of;

creating a new flex based dimension, creating a new foreign key on a dimension, providing a fact with a new foreign key to a dimension, providing a fact with new attributes, and propagating extension changes to post load process facts.

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

providing an extender associated with a data warehouse, wherein the extender is implemented in Java and wrapped by a remote service, and communicates with an administration tool on the BI server through a Java host;

providing, from the extender, data flow information to the administration tool, wherein the data flow information includes dependencies between target tables in the data warehouse and, and specifies mapping relationships between a plurality of source data objects and the target tables in the data warehouse;

receiving, from the administration tool, an input extension specification that includes one or more changes in the source data object, and one or more target tables to be extended using the one or more changes, wherein the input extension specification is constructed by the administration tool based on the one or more changes and the data flow information, wherein the extender receives the input extension specification as values of a plurality of input parameters of a function call from a Java client, which forwards the function call from the Java host in response to the administration tool making a call to the remote service through the Java host;

retrieving, via the extender, a metadata for a repository model of the data warehouse, and an extract, transform and load (ETL) metadata for the data warehouse, from a metadata server associated with the BI server;

extending the ETL metadata using the input extension specification and the metadata for the repository model of the data warehouse;

invoking, via the extender, an implementation module specific to the data warehouse to extend the one or more target tables in accordance with the extended ETL metadata;

generating, by the extender, an 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 output document to the administration tool, wherein the output document is configured to be used by the administration tool to modify the repository model of the data warehouse stored in the metadata service.

15. The non-transitory machine readable storage medium according to claim 14, wherein the data flow information is generated by the extender that

receives a source data store document, and tracks data flows from source data objects defined in the source data store document towards one or more target tables in the data warehouse, or

receives a data warehouse document, and obtains data flow from one or more source data objects that result in a particular target table defined in the data warehouse document.

16. The non-transitory machine readable storage medium according to claim 14, wherein the data flow information is represented in an XML file.

17. The non-transitory machine readable storage medium of claim 14, wherein the input extension specification specifies information on one or more dimensions before specifying information on one or more facts in physical repositories associated with the one or more target tables.

18. The non-transitory machine readable storage medium according to claim 14, wherein the input extension specification separates specifications for key and descriptive flex associated with the one or more table tables.

19. The non-transitory machine readable storage medium according to claim 14, further comprising:

using the input extension specification to perform at least one of;

creating a new flex based dimension,

creating a new foreign key on a dimension,

providing a fact with a new foreign key to a dimension,

providing a fact with new attributes, and

propagating extension changes to post load process facts.

20. The non-transitory machine readable storage medium according to claim 14, further comprising

using a container-mapping configuration to restrict a scope of extension to the particular warehouse.