The persistence service and the MetadataManager bean provide access to data. The persistence service provides access to objects in the BI Beans Catalog. The MetadataManager provides access to OLAP metadata. The MetadataManager also works with the persistence service to provide access to the BI Beans Catalog, so that it can provide access to stored components as well as to metadata.
Both the persistence service and the MetadataManager provide naming services. They do so by implementing the Java Naming and Directory Interface (JNDI). JNDI is a standard interface for naming components that you want to save and to retrieve. The persistence service and the MetadataManager also extend JNDI to provide added functionality, such as the ability to move and copy items from one folder to another.
As the persistence service and the MetadataManager implement JNDI interfaces, they also extend the interfaces, as follows:
The Context
and DirContext
interfaces, from JNDI, represent folders.
The Context
interface supports saving and retrieving components.
The DirContext
interface extends Context
, adding support for searching.
The BIContext
interface, in the oracle.dss.bicontext
package, extends DirContext
, adding methods for copying and moving components.
The MDFolder
class, in the oracle.dss.metadataManager.common
package, implements BIContext
. It extends MDObject
, in the same package. MDObject
is a client-side representation of a metadata object in an analytic workspace.
The PersistenceManager
interface, in the oracle.dss.persistence.persistencemanager.common
package, extends BIContext
, adding functionality for exporting subcontexts to XML.
The PersistenceManagerImpl
class, in oracle.dss.persistencemanager.client
, implements the PersistenceManager
interface.
The following diagram shows these relationships.