Oracle Warehouse Builder 10g

Metadata plays a pivotal role in any Warehouse Builder project and a lot of time and effort is spent on creating and managing metadata. While Warehouse Builder comes with a set of pre-built reports, there is more information available in the repository and the metadata access APIs allow you to customize your metadata reporting for both the design and runtime repository.

If your solution incorporates third party tools for querying or designing, these exchange APIs allow you to load metadata from Warehouse Builder into any third party tool and load data from any design tool into Warehouse Builder.

In some cases it is important to add metadata to the Warehouse Builder repository that is not natively available within the product. The extensibility APIs allow you to create custom objects and/or attributes within the repository. Once you have created or registered these new objects Warehouse Builder will allow you to report on them as if these were internal Warehouse Builder objects.

This in turn allows you to complete your lineage information or register impact on objects not defined in Warehouse Builder.

To enable customers and partners to link in their own security, Warehouse Builder provides the possibility to extend the security rules in the repository.

Much has been said about Data Quality in the past. Warehouse Builder is one of the few ETL tools in the market that allow any data quality vendor to implement a solution underneath the Warehouse Builder ETL tool.

This data quality API allows customers to choose or retain their data quality vendor of choice while utilizing the power of Warehouse Builder and the Oracle Database. Data Quality vendors can use this API to promote their products as a partner of Oracle.

The runtime management is handled out of the box by the Runtime Audit Browser. As the runtime engine is covered with Public Views customers and partners can create their own reporting environment on these SQL views. Using these SQL views the users can create their own exceptions reporting and their own statistics all on a supported set of queries.

Another part of the runtime platform is the modularity with which the platform is built. The code generators and the scheduling and process flow code are extensible and can allow the customer or partner to plug in their own adapters.

This API essentially allows anyone to create a complete warehouse management system based on out-of-the-box components.

Within Warehouse Builder you can publish a mapping or a process flow as a web service. Once you have published a mapping or process flow as a web service you can call the functionality within these components from any application.

This in turn allows you to utilize the data integration and cleansing capabilities of Warehouse Builder outside of the realm of traditional data warehouse projects. For example it will be possible to embed the name and address cleansing capabilities from mappings into a customer registration web site.

For this API you will need a combination of Oracle JDeveloper and Oracle Warehouse Builder.

One of the key requirements in ETL is to get access to various data sources. In some cases this can be achieved by gateways.

In the Warehouse Builder case, a gateway will translate the catalog and queries between a legacy system and Oracle. This way Warehouse Builder can read metadata from non-Oracle systems, and then use regular mappings (SQL and PL/SQL) to read data from the legacy system into Oracle just as if it was Oracle to Oracle data movement.

This SDK section allows you to self-certify your gateway solution with Oracle Warehouse Builder. By doing so customers can utilize your gateway in combination with a Warehouse Builder implementation.