DataProvider Properties

Oracle® OLAP Java API Reference
11g Release 1 (11.1)
B28128-01

DataProvider Settings

The following table lists the keys and the case-sensitive values for the settings that you can specify in a Properties object or XML string for a DataProvider or a UserSession and provides a brief description of them.

Properties Key or
Setting Name Value Property Description

Properties Key or Setting Name	Value	Property Description
`HierarchyValueType`	`unique` `local`	Specifies whether to use unique or local values for members of dimension hierarchies. The use of `Model` objects requires unique dimension hierarchy values. For more information on unique and local values, see the Overview of this documentation. The `unique` value specifies using a three part value that identifies the dimension hierarchy, the level in the hierarchy, and the local value of the dimension member in the level. It is the default value for the setting. The `local` value specifies using only the local dimension member value.
`MetadataReaderMode`	`11_ONLY` `10_ONLY` `10103AWONLY` `CWM2ONLY` `NONE`	Specifies the type of metadata recognized by the `MdmMetadataProvider` provided by the `DataProvider`. The `11_ONLY` value specifies that the `MdmMetadataProvider` recognizes only Oracle OLAP 11g metadata model objects. It is the default value for the setting. The `10_ONLY` value specifies that the `MdmMetadataProvider` recognizes only CWM2 metadata and 10g standard form analytic workspace metadata. The `10103AWONLY` value specifies that the `MdmMetadataProvider` recognizes only 10g standard form analytic workspace metadata. This metadata is generated for an analytic workspace by the Oracle OLAP Analytic Workspace Java API and by Analytic Workspace Manager in Oracle Database 10g releases. Oracle OLAP first used this type of metadata in Oracle Database 10g Release 1 (10.1.0.3). The `CWM2ONLY` value specifies that the `MdmMetadataProvider` recognizes only OLAP Catalog metadata. The `NONE` value specifies that the `MdmMetadataProvider` does not recognize any pre-existing metadata objects. The `MdmMetadataProvider` recognizes only the transient metadata objects that an application creates in the current session.
`SupportMTM`	`NO` `YES`	Specifies whether Oracle OLAP supports the mapping of metadata objects to source data by the use of the classes in the `oracle.olapi.metadata.mapping` package or by the use of the deprecated classes in the `oracle.olapi.metadata.mtm` package. The `NO` value specifies that Oracle OLAP supports the mapping of metadata objects to source data by the classes in the `oracle.olapi.metadata.mapping` package. It is the default value of the setting. The `NO` value is required for the `11_ONLY` metadadata reader mode. In that mode an application can create permanent metadata objects and map them to data sources. It can also create transient custom metadata objects that represent data that is specified by an `Expression`. For the other metadata reader modes, a `NO` value specifies that Oracle OLAP uses the `oracle.olapi.metadata.mapping` classes to map metadata objects to source data. In those other modes, all metadata objects than an application creates are transient. The `YES` value specifies that the Oracle OLAP supports the mapping of metadata objects to source data by the deprecated classes in the `oracle.olapi.metadata.mtm` package. This setting provides backward compatibility for applications that use `mtm` package classes. An application can create transient metadata objects and map them using `mtm` classes.

HierarchyValueType

unique
local

Specifies whether to use unique or local values for members of dimension hierarchies. The use of Model objects requires unique dimension hierarchy values. For more information on unique and local values, see the Overview of this documentation.

The unique value specifies using a three part value that identifies the dimension hierarchy, the level in the hierarchy, and the local value of the dimension member in the level. It is the default value for the setting.

The local value specifies using only the local dimension member value.

MetadataReaderMode

11_ONLY
10_ONLY
10103AWONLY
CWM2ONLY
NONE

Specifies the type of metadata recognized by the MdmMetadataProvider provided by the DataProvider.

The 11_ONLY value specifies that the MdmMetadataProvider recognizes only Oracle OLAP 11g metadata model objects. It is the default value for the setting.

The 10_ONLY value specifies that the MdmMetadataProvider recognizes only CWM2 metadata and 10g standard form analytic workspace metadata.

The 10103AWONLY value specifies that the MdmMetadataProvider recognizes only 10g standard form analytic workspace metadata. This metadata is generated for an analytic workspace by the Oracle OLAP Analytic Workspace Java API and by Analytic Workspace Manager in Oracle Database 10g releases. Oracle OLAP first used this type of metadata in Oracle Database 10g Release 1 (10.1.0.3).

The CWM2ONLY value specifies that the MdmMetadataProvider recognizes only OLAP Catalog metadata.

The NONE value specifies that the MdmMetadataProvider does not recognize any pre-existing metadata objects. The MdmMetadataProvider recognizes only the transient metadata objects that an application creates in the current session.

SupportMTM

NO
YES

Specifies whether Oracle OLAP supports the mapping of metadata objects to source data by the use of the classes in the oracle.olapi.metadata.mapping package or by the use of the deprecated classes in the oracle.olapi.metadata.mtm package.

The NO value specifies that Oracle OLAP supports the mapping of metadata objects to source data by the classes in the oracle.olapi.metadata.mapping package. It is the default value of the setting.

The NO value is required for the 11_ONLY metadadata reader mode. In that mode an application can create permanent metadata objects and map them to data sources. It can also create transient custom metadata objects that represent data that is specified by an Expression. For the other metadata reader modes, a NO value specifies that Oracle OLAP uses the oracle.olapi.metadata.mapping classes to map metadata objects to source data. In those other modes, all metadata objects than an application creates are transient.

The YES value specifies that the Oracle OLAP supports the mapping of metadata objects to source data by the deprecated classes in the oracle.olapi.metadata.mtm package. This setting provides backward compatibility for applications that use mtm package classes. An application can create transient metadata objects and map them using mtm classes.