What is the MetadataManager?

The MetadataManager bean provides access to OLAP data. The MetadataManager creates a client-side representation (an MDObject) of each metadata object in the database. Through these MDObject objects, a Java program can get information about the metadata in the database.

In addition, the MetadataManager interacts with the persistence service, so that you can store persistable components in the BI Beans Catalog, through the MetadataManager. Not only can you store graphs and crosstabs, but you can also save selections (favorites) in the BI Beans Catalog. Custom measures (calculations) are also saved in the Catalog, through the CalcBuilder.

Because the MetadataManager can access both OLAP data and Catalog data, the MetadataManager presents a consolidated view of your data. For example, in the QueryBuilder, the measures obtained from Oracle OLAP and the custom measures, obtained from the BI Beans Catalog, appear together.

The QueryManager, QueryBuilder, and CalcBuilder beans all depend on the MetadataManager for access to data from Oracle OLAP.

Where objects are stored

OLAP metadata is stored in an Oracle database. The MetadataManager has access to these objects through the use of the OLAP API. A database administrator (DBA) uses a product such as Oracle Warehouse Builder to create and maintain the Oracle data warehouse on which the OLAP metadata relies. The DBA uses Oracle Enterprise Manager to create and maintain OLAP metadata.

Java components are stored in the Catalog. These objects must implement the Persistable interface, which is defined in the oracle.dss.util.persistence package.