Skip Headers
Oracle® Fusion Middleware XML Schema Reference for Oracle Business Intelligence Enterprise Edition
11g Release 1 (11.1.1)

Part Number E23950-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

10 XML Marketing, Security, and Other Elements

This chapter provides Oracle BI Server XML API reference information for Oracle Marketing Segmentation elements, security elements, and miscellaneous Oracle BI repository elements that do not fall in other categories.

This chapter contains the following topics:

10.1 XML Marketing Elements

Marketing elements are typically those elements that are related to features for the Oracle Marketing Segmentation product. For information about features and options related to Oracle Marketing Segmentation, see the administrator documentation for the Oracle Marketing Segmentation application.

Marketing elements include:

10.1.1 XML Elements: Catalog Link

The catalog link element corresponds to the conforming dimension link object in the Marketing metadata. A conforming dimension links a fact that contains target-level IDs to a fact that does not contain target-level IDs by navigating along a dimension that is shared by both fact tables.

The catalog link tag includes the following child elements:

Table 10-1 Catalog Link Child Elements

Element Name Description

From

References the presentation column that represents the primary key of the subject area from which the dimension link originates.

The primary key column is contained in a sub-element called RefPresentationColumn.

To

References the presentation column that represents the primary key of the subject area to which the dimension link points.

The primary key column is contained in a sub-element called RefPresentationColumn.


The catalog link tag does not include any attributes.

Syntax

<CatalogLink …>
   <Description />
   <From>
     <RefPresentationColumn …/>
   </From>
   <To>
     <RefPresentationColumn …/>
   </To>
</CatalogLink>

Example

<CatalogLink name="Customer Profile-&gt;Campaign Contacts" 
     id="4012:280960" uid="8032f5a3-0fac-0000-714b-e31d00000000">
   <Description>
     <![CDATA[Used by both Contact and Account Target Levels to filter with
      " Offered Product_segmentation" catalog.]]>
   </Description>
   <To>
   <RefPresentationColumn id="4010:223709" 
     uid="80312fc3-0faa-0000-714b-e31d00000000"
     qualifiedName="&quot;Campaign Contacts_segmentation&quot;..&quot;
      - Contact Profile&quot;.&quot;ROW_ID&quot;"/>
   </To>
</CatalogLink>

10.1.2 XML Elements: Target Level

The target level element corresponds to the target level object in the Marketing metadata. A target level is the entity that a marketer wants to count, typically customer types like individuals, businesses, or households.

The target level tag includes the following attributes:

Table 10-2 Target Level Tag Attributes

Attribute Name Description

hasDispName

Indicates whether this target level has a custom display name.

dispName

The value of the custom display name, if one exists for this target level.

hasDispDescription

Indicates whether this target level has a custom description.

dispDescription

The value of the custom description, if one exists for this target level.


The target level tag includes the following child elements:

Table 10-3 Target Level Child Elements

Element Name Description

PrimaryQLI

References the primary qualified list item for this target level.

The qualified list item is contained in a sub-element called RefQualifiedListItem.

PrimaryPresCatalog

References the primary segmentation catalog for this target level.

The segmentation catalog is contained in a sub-element called RefPresentationCatalog.

SamplingTables

References the physical tables used as sampling tables for this target level.

Each physical table is contained in a sub-element called RefSamplingTable.

Catalogs

References the set of segmentation catalogs for this target level.

Each segmentation catalog is contained in a sub-element called RefSegCatalog.

PresentationCatalog

References the subject area for saved result sets (the saved results catalog).

The saved results catalog is contained in a sub-element called RefPresentationCatalog.

TargetColumn

References the Target Id presentation column.

The Target Id column is contained in a sub-element called RefPresentationColumn.

NodeColumn

References the GUID presentation column.

The GUID column is contained in a sub-element called RefPresentationColumn.

PhysicalTable

References the physical table that stores the result sets for this target level.

The physical table is contained in a sub-element called RefPhysicalTable.

ConnectionPool

References the connection pool in which this target level is mapped.

The connection pool is contained in a sub-element called RefConnectionPool.

HeaderSQL

Contains the physical SQL to insert the Saved Result Header. Used when users save a result set.

DelHeaderSQL

Contains the physical SQL to delete the saved result set header. Used when users purge saved result sets.

DelDataSQL

Contains the physical SQL to delete the saved result data set. Used when users purge saved result sets.


Syntax

<TargetLevel …
     hasDispName=""
     dispName=""
     hasDispDescription=""
     dispDescription="" >
   <Description />
   <PrimaryQLI>
     <RefQualifiedListItem …/>
   </PrimaryQLI>
   <PrimaryPresCatalog>
     <RefPresentationCatalog …/>
   </PrimaryPresCatalog>
   <SamplingTables>
     <RefSamplingTable …/>
   </SamplingTables>
   <Catalogs>
     <RefSegCatalog …/>
     <RefSegCatalog …/>
   </Catalogs>
   <PresentationCatalog>
     <RefPresentationCatalog …/>
   </PresentationCatalog>
   <TargetColumn>
     <RefPresentationColumn …/>
   </TargetColumn>
   <NodeColumn>
     <RefPresentationColumn …/>
   </NodeColumn>
   <PhysicalTable>
     <RefPhysicalTable …/>
   </PhysicalTable>
   <ConnectionPool>
     <RefConnectionPool …/>
   </ConnectionPool>
   <HeaderSQL …/>
   <DelHeaderSQL …/>
   <DelDataSQL …/>
</TargetLevel>

Example

<TargetLevel name="Claims" 
     id="4014:280967" uid="803421c3-0fae-0000-714b-e31d00000000" 
     hasDispName="false" hasDispDescription="false">
   <PrimaryQLI>
     <RefQualifiedListItem id="4018:280971" 
      uid="80341f19-0fb2-0000-714b-e31d00000000" 
      qualifiedName="&quot;Claims&quot;"/>
   </PrimaryQLI>
   <PrimaryPresCatalog>
     <RefPresentationCatalog id="4004:275727"
      uid="803405cb-0fa4-0000-714b-e31d00000000" 
      qualifiedName="&quot;Insurance Claims_Segmentation&quot;"/>
   </PrimaryPresCatalog>
   <SamplingTables>
     <RefSamplingTable id="4024:281052" 
      uid="80342e79-0fb8-0000-714b-e31d00000000"
      qualifiedName="&quot;Claims&quot;.&quot;M_10C_INSCLM_D&quot;"/>
   </SamplingTables>
   <Catalogs>
     <RefSegCatalog id="4026:281080" 
      uid="803421ca-0fba-0000-714b-e31d00000000"
      qualifiedName="&quot;Claims&quot;.&quot;Claims_Insurance Claims_Segmentation
       &quot;"/>
     <RefSegCatalog id="4026:281081" 
      uid="803421cb-0fba-0000-714b-e31d00000000"
      qualifiedName="&quot;Claims&quot;.&quot;Claims_Fin Accounts and
        Ins Policies_segmentation&quot;"/>
     <RefSegCatalog id="4026:281082" 
      uid="803421c8-0fba-0000-714b-e31d00000000"
      qualifiedName="&quot;Claims&quot;.&quot;Claims_Activities_segmentation
       &quot;"/>
     <RefSegCatalog id="4026:281083" 
      uid="803421c9-0fba-0000-714b-e31d00000000"
      qualifiedName="&quot;Claims&quot;.&quot;Claims_Service Requests_segmentation
       &quot;"/>
   </Catalogs>
   <TargetColumn>
     <RefPresentationColumn id="4010:226622" 
      uid="80342e43-0faa-0000-714b-e31d00000000" 
      qualifiedName="&quot;Marketing Segmentation Cache and Saved Results
       &quot;..&quot;- Claim Result Data&quot;.&quot;Claim ID&quot;"/>
   </TargetColumn>
   <NodeColumn>
     <RefPresentationColumn id="4010:226621" 
      uid="80342e45-0faa-0000-714b-e31d00000000" 
      qualifiedName="&quot;Marketing Segmentation Cache and Saved Results
       &quot;..&quot;- Claim Result Data&quot;.&quot;GUID&quot;"/>
   </NodeColumn>
   <PhysicalTable>
     <RefPhysicalTable id="3001:100690" 
      uid="80342d47-0bb9-0000-714b-e31d00000000" 
      qualifiedName="&quot;Oracle Data Warehouse&quot;.&quot;Catalog
       &quot;.&quot;dbo&quot;.&quot;M_SR_CLAIM&quot;"/>
   </PhysicalTable>
   <HeaderSQL>
     <![CDATA[INSERT INTO M_SR_HEADER (GUID, SEGMENT_PATH, SR_CUSTOM_LABEL,
      PRIORITY, NODE_PATH, NODE_LABEL, TARGET_LEVEL, CREATED_BY, "COUNT", DATE_
      TIME, SR_PATH, CONNECTION_POOL) VALUES ('@{guid}', '@{segmentPath}',
       '@{srCustomLabel}', @{priority}, '@{nodePath}', '@{nodeLabel}',
       '@{targetLevel}','@{createdBy}', @{count},'@{createdTime}', '@{srPath}',
       '@{connectionPool}')]]>
   </HeaderSQL>
   <DelHeaderSQL>
     <![CDATA[DELETE FROM M_SR_HEADER WHERE GUID IN (@{guids})]]>
   </DelHeaderSQL>
   <DelDataSQL>
     <![CDATA[DELETE FROM M_SR_CLAIM WHERE GUID IN (@{guids})]]>
   </DelDataSQL>
</TargetLevel>

10.1.3 XML Elements: List Catalog

The list catalog element corresponds to the list catalog object in the Marketing metadata. A list catalog is an object that is used to generate a list of data at the target level.

The list catalog tag includes the following child elements:

Table 10-4 List Catalog Child Elements

Element Name Description

RefPresentationCatalog

References the subject area for this list catalog. The name of the subject area is used as the name of the list catalog.

QualifyingKeys

References the set of qualifying keys for this list catalog.

Each qualifying key is contained in a sub-element called RefQualifyingKey.


The list catalog tag does not include any attributes.

Syntax

<ListCatalog …>
   <Description />
   <RefPresentationCatalog …/>
   <QualifyingKeys>
     <RefQualifyingKey …/>
     <RefQualifyingKey …/>
   </QualifyingKeys>
</ListCatalog>

Example

<ListCatalog name="Campaign Load - Contacts" 
     id="4016:281116" uid="8032fe2c-0fb0-0000-714b-e31d00000000">
   <RefPresentationCatalog id="4004:275725"
    uid="8032fb8c-0fa4-0000-714b-e31d00000000"
    qualifiedName="&quot;Campaign Load - Contacts&quot;"/>
   <QualifyingKeys>
     <RefQualifyingKey id="4020:281006"
      uid="8032fe3d-0fb4-0000-714b-e31d00000000"
      qualifiedName="&quot;Contacts&quot;.&quot;Qualifying Key#29&quot;"/>
     <RefQualifyingKey id="4020:281037"
      uid="8032fe3e-0fb4-0000-714b-e31d00000000"
      qualifiedName="&quot;Accounts&quot;.&quot;Qualifying Key#30&quot;"/>
   </QualifyingKeys>
</ListCatalog>

10.1.4 XML Elements: Qualified List Item

The qualified list item element corresponds to the qualified list item object in the Marketing metadata. A qualified list item is an entity that is evaluated against segment criteria so that the information related to that entity can be exported in a list file.

The qualified list item tag includes the following attributes:

Table 10-5 Qualified List Item Tag Attributes

Attribute Name Description

cacheTable

Indicates whether this qualified list item is cached.


The qualified list item tag includes the following child elements:

Table 10-6 Qualified List Item Child Elements

Element Name Description

CacheCatalog

References the subject area for the cache for this qualified list item.

The subject area is contained in a sub-element called RefPresentationCatalog.

CacheConnPool

References the connection pool for the cached table.

The connection pool is contained in a sub-element called RefConnectionPool.

TargetColumn

References the Target Id presentation column.

The Target Id column is contained in a sub-element called RefPresentationColumn.

NodeColumn

References the GUID presentation column.

The GUID column is contained in a sub-element called RefPresentationColumn.

PhysicalTable

References the physical table that stores the cached qualified list item.

The physical table is contained in a sub-element called RefPhysicalTable.

DeleteSQL

Contains the physical SQL used to delete the cached results.


Syntax

<QualifiedListItem …
     cacheTable="">
   <Description />
   <CacheCatalog>
     <RefPresentationCatalog …/>
   </CacheCatalog>
   <CacheConnPool>
     <RefConnectionPool …/>
   </CacheConnPool>
   <TargetColumn>
     <RefPresentationColumn …/>
   </TargetColumn>
   <NodeColumn>
     <RefPresentationColumn …/>
   </NodeColumn>
   <PhysicalTable>
     <RefPhysicalTable …/>
   </PhysicalTable>
   <DeleteSQL>
     <!CDATA[[…]]>
   </DeleteSQL>
</QualifiedListItem>

Example

<QualifiedListItem name="Service Requests"
     id="4018:6474" uid="80caa1d3-0fb2-0000-714b-e31d00000000">
   <DeleteSQL>
     <![CDATA[DELETE FROM M_C_GENERIC WHERE GUID = '@{guid}']]>
   </DeleteSQL>
</QualifiedListItem>

10.1.5 XML Elements: Qualifying Key

The qualifying key element corresponds to the qualifying keys that are used in list catalog or segmentation catalog objects in the Marketing metadata. Qualifying keys map qualified list items to presentation columns.

The qualifying key tag includes the following child elements:

Table 10-7 Qualifying Key Child Elements

Element Name Description

RefSegCatalog

References the segmentation catalog to which this qualifying key belongs.

RefListCatalog

References the list catalog to which this qualifying key belongs.

RefPresentationColumn

References the presentation column for this qualifying key.


The qualifying key tag does not include any attributes.

Syntax

<QualifyingKey …>
   <Description />
   <RefSegCatalog ../>
   <RefListCatalog ../>
   <RefPresentatonColumn ../>
</QualifyingKey>

Example

<QualifyingKey name="MKTG_QK_4020:125971262767661"
     parentName="&quot;Customers&quot;"
     parentId="4018:6474" parentUid="80caa1d3-0fb2-0000-714b-e31d00000000"
     id="4020:12597" uid="80cab8c6-0fb4-0000-714b-e31d00000000">
   <RefSegCatalog id="4026:12596" 
    uid="80cab8c7-0fba-0000-714b-e31d00000000"
    qualifiedName="&quot;Customers&quot;.&quot;Customers_A - Sample Sales&quot;"/>
   <RefPresentationColumn id="4010:12527" 
    uid="80cab87f-0faa-0000-714b-e31d00000000"
    qualifiedName="&quot;A - Sample Sales&quot;..&quot;More Customer Objects&quot;
     .&quot;X20 Cust Key (Segmentation)&quot;"/>
</QualifyingKey>

10.1.6 XML Elements: Sampling Table

The sampling table element corresponds to the sampling table object in the Marketing metadata. Sampling tables are created and managed as part of target level objects.

The sampling table tag includes the following attributes:

Table 10-8 Sampling Table Tag Attributes

Attribute Name Description

factor

The sampling factor (for example, 10%).


The sampling table tag includes the following child elements:

Table 10-9 Sampling Table Child Elements

Element Name Description

RefPhysicalTable

References the physical table being used as the sampling table.


Syntax

<SamplingTable … 
     factor="">
   <Description />
   <RefPhysicalTable …/>
</SamplingTable>

Example

<SamplingTable name="M_10C_PERSON_D" 
     parentName="&quot;Contacts&quot;" 
     parentId="4014:280966" parentUid="802ba17b-0fae-0000-714b-e31d00000000"
     id="4024:281051" uid="80331464-0fb8-0000-714b-e31d00000000"
     factor="0.1">
   <RefPhysicalTable id="3001:86873" 
    uid="002261ab-0bb9-0000-714b-e31d00000000" 
    qualifiedName="&quot;Oracle Data Warehouse&quot;.&quot;Catalog&quot;
     .&quot;dbo&quot;.&quot;Dim_W_PARTY_PER_D_Contact&quot;"/>
</SamplingTable>

10.1.7 XML Elements: Seg Catalog

The seg catalog element corresponds to the segmentation catalog object in the Marketing metadata. Segmentation catalogs are Oracle BI subject areas that are enabled for segmentation. Segmentation catalogs provides a set of dimensions and fact measures that can be used to create segment criteria.

The seg catalog tag includes the following child elements:

Table 10-10 Seg Catalog Child Elements

Element Name Description

RefPresentationCatalog

References the subject area for this segmentation catalog.

QualifyingKeys

References the set of qualifying keys for this list catalog.

Each qualifying key is contained in a sub-element called RefQualifyingKey.


The seg catalog tag does not include any attributes.

Syntax

<SegCatalog …>
   <Description />
   <RefPresentationCatalog …/>
   <QualifyingKeys>
     <RefQualifyingKey …/>
   </QualifyingKeys>
</SegCatalog>

Example

<SegCatalog name="Customers_A - Sample Sales" 
     parentName="&quot;Customers&quot;" 
     parentId="4014:6473" parentUid="80caa1d2-0fae-0000-714b-e31d00000000"
     id="4026:12596" uid="80cab8c7-0fba-0000-714b-e31d00000000">
   <RefPresentationCatalog id="4004:12383" 
    uid="80cab7ef-0fa4-0000-714b-e31d00000000"
    qualifiedName="&quot;A - Sample Sales&quot;"/>
   <QualifyingKeys>
     <RefQualifyingKey id="4020:12597" 
      uid="80cab8c6-0fb4-0000-714b-e31d00000000"
      qualifiedName="&quot;Customers&quot;.&quot;
       MKTG_QK_4020:125971262767661&quot;"/>
   </QualifyingKeys>
</SegCatalog>

10.2 XML Security Elements

Security elements are typically those elements that are related to Oracle Business Intelligence security features, such as those related to variables, authentication, privileges, users, and application roles. Security elements include:

10.2.1 XML Elements: Variable

The variable element corresponds to the variable object in the Physical layer of the repository.

The variable tag includes the following attributes:

Table 10-11 Variable Tag Attributes

Attribute Name Description

securityMask

For session variables only. This attribute stores the value of the following options:

  • Enable any user to set the value. When selected, lets session variables be set after the initialization block has populated the value (at user login) by calling the ODBC store procedure NQSSetSessionValue(). For example, this option lets non-administrators set this variable for sampling.

  • Security Sensitive. When selected, identifies the variable as sensitive to security for virtual private databases (VPDs). When filtering cache table matches, the Oracle BI Server looks at the parent database of each column or table that is referenced in the logical request projection list. If the physical database source is a VPD, the Oracle BI Server matches a list of security-sensitive variables to each prospective cache hit. Cache hits would only occur on cache entries that included and matched all security-sensitive variables.

isSessionVar

If set to true, indicates that this variable is a session variable. Session variables are created and assigned a value when each user logs on, unlike repository variables, which have static values.


The variable tag includes the following child elements:

Table 10-12 Variable Child Elements

Element Name Description

Expr

Contains the expression that forms the definition of this variable.


Syntax

<Variable …
     securityMask=""
     isSessionVar="">
   <Description />
   <Expr>...</Expr>
</Variable>

Example

<Variable name="DYNAMIC_PRODUCT_TABLE" 
     parentName="&quot;DUAL Prod Table&quot;"
     parentId="3033:81463" parentUid="80cc200a-0bd9-0000-714b-e31d00000000"
     id="3031:7079" uid="80caa443-0bd7-0000-714b-e31d00000000"
     securityMask="2" isSessionVar="true">
   <Expr>
     <![CDATA['SAMP_PRODUCTS_D']]>
   </Expr>
</Variable>

10.2.2 XML Elements: LDAP Server

The LDAP server element corresponds to the LDAP server object in the Identity Manager dialog in the Administration Tool.

The LDAP server tag includes the following attributes:

Table 10-13 LDAP Server Tag Attributes

Attribute Name Description

hostName

The host name of the LDAP server.

port

The port number of the LDAP server (for example, 389).

baseDN

The base distinguished name (DN) that identifies the starting point of the authentication search.

bindDN

The optional DN that is required to bind to the LDAP server. This option is required if isADSI is set to true.

userNameAttrType

A value that uniquely identifies a user, such as the user ID, the RDN (relative distinguished name), or (for ADSI) sAMAccountName.

domainID

A domain identifier that uniquely identifies the domain for which the LDAP object is responsible. This is especially useful when there are multiple LDAP objects.

password

The user password associated with the Bind DN. This option is required if isADSI is set to true. Note that passwords are encrypted.

timeout

The time period after which Administration Tool import attempts or Oracle BI Server user authentication attempts against this LDAP server will time out.

cacheExpiry

The interval at which the authentication cache entry in the LDAP cache for a logged on user is refreshed.

This option corresponds to Cache refresh interval in the Repository tab of the Options dialog in the Administration Tool.

isADSI

If set to true, indicates that this is an Active Directory LDAP server.

useSSL

If set to true, indicates that the connection to the LDAP server uses Secure Sockets Layer (SSL).

keyFile

The name of the key file that holds the client certificate and Certificate Authority (CA) certificate. Required if useSSL is set to true.

This option corresponds to Key file name in the Repository tab of the Options dialog in the Administration Tool.

keyPassword

For a secure LDAP, there is a keydb file which stores the required certificates. keyPassword is the password to access the keydb file.

version

The LDAP version number of the LDAP server, either 2 or 3. The default is 3.

cacheEntries

The maximum number of entries in the authentication cache, preallocated when the Oracle BI Server starts. If the number of users exceeds this limit, cache entries are replaced using the LRU algorithm. If this value is 0, then the authentication cache is disabled.

This option corresponds to Number of Cache Entries in the Repository tab of the Options dialog in the Administration Tool.


The LDAP server tag does not include any child elements.

Syntax

<LDAPServer …
     hostName=""
     port=""
     baseDN=""
     bindDN=""
     userNameAttrType=""
     domainID=""
     password=""
     timeout=""
     cacheExpiry=""
     entities=""
     isADSI=""
     useSSL=""
     keyFile=""
     keyPassword=""
     version=""
     cacheEntries="">
   <Description />
</LDAPServer>

Example

<LDAPServer name="L1" 
     id="3035:44085" uid="c39e1310-0c00-1000-806e-0a9702490000"
     hostName="sdacns05" port="389" version="3" baseDN="name1" bindDN="name2"
     userNameAttrType="sAMAccountName"
     password="6C6F0BE01FC4111F3AC2236A364D912E6CC6E805A7729CECC34915F82D6CA5D1B19
      AF813BD5ADC908750471E8F5D151A A886F77E060E2E17F45AD8D18CAB2E4D3EFA15B75E30D8
      B4BFA8C7B2D70552BD"
     timeout="60" cacheExpiry="86400" cacheEntries="1000" 
     isADSI="true" useSSL="true"
     keyPassword="E3130008E1C4CAD47041E4AE68B048E6 7C2E35213306F12832914CBE7A9DD95
      561D771DED06484112B1FC6F27B6D0D58">
</LDAPServer>

10.2.3 XML Elements: Init Block

The init block element corresponds to the initialization block object in the Physical layer. Initialization blocks are used to initialize dynamic repository variables, system session variables, and nonsystem session variables.

The init block tag includes the following attributes:

Table 10-14 Init Block Tag Attributes

Attribute Name Description

isSessionVar

If set to true, indicates that this initialization block is a session initialization block. Session initialization blocks are used with session variables.

The default value is false.

refreshPeriod

The refresh interval for this initialization block, in seconds. For repository initialization blocks only.

The default value is 0.

baseTime

The start date and time for this initialization block. For repository initialization blocks only.

The default value is 2001-01-01 00:00:00.

isRowWiseInit

If set to true, indicates that row-wise initialization has been enabled. Row-wise initialization lets you create session variables dynamically and set their values when a session begins. For session initialization blocks only.

The default value is false.

isRowWiseCacheEnabled

If set to true, indicates that the Use caching option has been enabled. This option directs the Oracle BI Server to store the results of the query in a main memory cache. This option is only available if row-wise initialization has been enabled.

The default value is true.

isSuccRequired

Indicates that the Required for Authentication option has been selected for this initialization block in the Administration Tool.

If this option is selected, this initialization block must succeed for users to log in. In other words, users will be denied access to Oracle BI EE if the initialization block fails to execute. Failure to execute can occur if the wrong credentials have been defined in the initialization block, or if there is an error in the default initialization string.

The default value is false.

isEnabled

If set to true, indicates that this initialization block is enabled. For session initialization blocks only.

The default value is true.

isDeferredExecution

If set to true, indicates that deferred execution of this initialization block is enabled.

Deferred execution is used to speed up the server startup time, by preventing the execution of the SQL for the initialization block when the server starts. The SQL is issued and the variables are intialized only when one of the variables is used.

isDBIndependentSQL

If set to true, indicates that database independent SQL is enabled.

The SQL is logical SQL, and it is translated by Oracle BI server to database specific SQL.


The init block tag includes the following child elements:

Table 10-15 Init Block Child Elements

Element Name Description

RefConnectionPool

References the connection pool for this initialization block.

This element is only used if the data source type for this initialization block is Database or XML.

RefCustomAuthenticator

References the custom authenticator for this initialization block.

DBMap

Stores the value of database-specific strings. The <DBMap> element contains an <Item> tag, which in turn contains a <Value> tag, as follows:

<Item name="">
   <Value />
</Item>

Predecessors

References the initialization blocks, if any, that are initialized before this initialization block

Each initialization block is contained in a sub-element called RefInitBlock.

Variables

References the variables that are associated with this initialization block.

Each variable is contained in a sub-element called RefVariable.

InitString

The SQL initialization string needed to populate the variables.

This element is only used if the data source type for this initialization block is Database or XML.

LDAPServers

References the LDAP servers that are associated with this initialization block.

Each LDAP server is contained in a sub-element called RefLDAPServer.

This element is only used if the data source type for this initialization block is LDAP.


Syntax

<InitBlock …
     isSessionVar=""
     refreshPeriod=""
     baseTime=""
     isRowWiseInit=""
     isRowWiseCacheEnabled=""
     isSuccRequired=""
     isEnabled=""
     isDeferredExecution=""
     isDBIndependentSQL="">
   <Description />
   <RefConnectionPool …/>
   <RefCustomAuthenticator …/>
   <DBMap>
     <Item name="">
       <Value …/>
     </Item>
   </DBMap>
   <Predecessors>
     <RefInitBlock …/>
   </Predecessors>
   <Variables>
     <RefVariable …/>
     <RefVariable …/>
   </Variables>
   <InitString …/>
   <LDAPServers>
     <RefLDAPServer …/>
     <RefLDAPServer …/>
   </LDAPServers>
<InitBlock>

Example

<InitBlock name="DUAL Prod Table" 
     id="3033:81463" uid="80cc200a-0bd9-0000-714b-e31d00000000" 
     isSessionVar="true">
   <RefConnectionPool id="3029:1159" 
    uid="80ca62c5-0bd5-0000-714b-e31d00000000" 
    qualifiedName="&quot;01 - Sample App Data (ORCL)&quot;.&quot;
     Sample Relational Connection&quot;"/>
   <DBMap>
     <Item name="DefaultMulDB">
       <Value>
        <![CDATA[Select 'SAMP_PRODUCTS_D' From Dual]]>
       </Value>
     </Item>
   </DBMap>
   <Variables>
     <RefVariable id="3031:7079" 
      uid="80caa443-0bd7-0000-714b-e31d00000000"
      qualifiedName="&quot;DUAL Prod Table&quot;.&quot;
       DYNAMIC_PRODUCT_TABLE&quot;"/>
   </Variables>
   <InitString>
     <![CDATA[Select 'SAMP_PRODUCTS_D' From Dual]]>
   </InitString>
</InitBlock>

10.2.4 XML Elements: Custom Authenticator

The Custom Authenticator element corresponds to the Custom Authenticator object in the Identity Manager dialog in the Administration Tool.

The Custom Authenticator tag includes the following attributes:

Table 10-16 Custom Authenticator Tag Attributes

Attribute Name Description

cacheExpiry

The interval at which the authentication cache entry for a logged on user is refreshed for this custom authenticator.

path

The path and name of the authenticator plug-in dll.

configParam

Lists any parameters for this custom authenticator that have been explicitly exposed for configuration.

hiddenParam

Lists any parameters for this custom authenticator that have been encrypted, such as passwords.

cacheEntries

The maximum number of entries in the authentication cache for this custom authenticator, preallocated when the Oracle BI Server starts. If the number of users exceeds this limit, cache entries are replaced using the LRU algorithm. If this value is 0, then the authentication cache is disabled.

csfKey

This attribute is not used.


The Custom Authenticator element does not include any child elements.

Syntax

<CustomAuthenticator …
     cacheExpiry=""
     path=""
     configParam=""
     hiddenParam=""
     cacheEntries="">
   <Description />
</CustomAuthenticator>

Example

<CustomAuthenticator name="NEWCA" 
     id="3047:44086" uid="c467a4a0-0c00-1000-806e-0a9702490000"
     cacheExpiry="86400" cacheEntries="1000" 
     path="authenticate.dll"
     configParam="ABC"
     hiddenParam="D7EDED84BC624A917F5B462A4DCA05CDCE256EEEEEDC97D5B383E1888393F558
      5DA9CAC25EA1FA59">
</CustomAuthenticator>

10.2.5 XML Elements: Privilege Package

The privilege package element is a container for other privileges. It corresponds to a set of permissions that applies to a particular user or application role object in the repository metadata. The privilege package element contains the information available on the Object Permissions, Data Filters, and Query Limits tabs of the User/Application Role Permissions dialog in the Administration Tool.

Because privilege packages can be associated with more than one user or application role, the total number of privilege packages may not equal the total number of users and application roles.

Note:

You can also set permissions for a privilege package without specifying values in the Administration Tool. For more information, see Section 10.2.11, "XML Elements: SetPermission."

The privilege package tag includes the following attributes:

Table 10-17 Privilege Package Tag Attributes

Attribute Name Description

isFineGrainedMode

Reserved for Oracle internal use only.


The privilege package tag includes the following child elements:

Table 10-18 Privilege Package Child Elements

Element Name Description

QueryPrivileges

References any query privileges that belong to this privilege package, along with the corresponding database.

Each pair of query privileges and database name is contained in a sub-element called Mapping.

Each Mapping sub-element contains two additional sub-elements: RefDatabase, which references the database name, and RefQueryPrivilege, which references the query privilege.

See the syntax for the privilege package element to see the complete hierarchy for the QueryPrivileges child element.

Filters

References any data filters that belong to this privilege package by mapping an object name with the filter expression.

Each pair of object name and filter expression is contained in a sub-element called Mapping. This sub-element has one attribute called Status. Valid values are Enabled, Disabled, and Ignored.

Each Mapping sub-element contains two additional sub-elements: RefObject, which references the metadata object name, and Expr, which contains the filter expression.

See the syntax for the privilege package element to see the complete hierarchy for the Filters child element.

ObjectPrivileges

References any object privileges that belong to this privilege package.

Each object privilege is contained in a sub-element called RefObjectPrivilege.


Note that the schema lists attributes for none, read, write, readwrite, delete, grant, and all, but these attributes are not used. Instead, these permissions are exposed as part of the child element definitions.

Syntax

<PrivilegePackage …
     isFineGrainedMode="">
   <Description />
   <QueryPrivileges>
     <Mapping>
       <RefDatabase …/>
       <RefQueryPrivilege …/>
     </Mapping>
   </QueryPrivileges>
   <Filters>
     <Mapping status="">
       <RefObject …/>
       <Expr …/>
     </Mapping>
   </Filters>
   <ObjectPrivileges>
     <RefObjectPrivilege …/>
   </ObjectPrivileges>
</PrivilegePackage>

Example

<PrivilegePackage name="PrivPack_4209:3417381144981469"
     id="4209:281602" uid="808626e7-1071-0000-714b-e31d00000000">
   <QueryPrivileges>
     <Mapping>
       <RefDatabase id="3023:68561" 
        uid="0023840a-0bcf-0000-714b-e31d00000000" 
        qualifiedName="&quot;Oracle Data Warehouse&quot;"/>
       <RefQueryPrivilege id="4204:281350" 
        uid="808626e8-106c-0000-714b-e31d00000000"
        qualifiedName="&quot;QueryPriv_4204:3417391144981469&quot;"/>
     </Mapping>
   </QueryPrivileges>
   <Filters>
     <Mapping status="disable">
       <RefObject id="2035:365983" 
        uid="80d105ed-07f3-0000-714b-e31d00000000"
        qualifiedName="&quot;Core&quot;.&quot;Fact - Sourcing - Response&quot;"/>
       <Expr>
        <![CDATA[cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE)
         = valueof(NQ_SESSION.PRC_BU_MANAGE_NEG) AND ("Core"."Dim - Purchase
         Buyer"."Purchase Buyer Login" = valueof(NQ_SESSION."USER") OR
         cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE)=
         valueof(NQ_SESSION.PRC_BU_MANAGE_NEG_ViewOthers))]]>
       </Expr>
     </Mapping>
     <Mapping status="disable">
       <RefObject id="2035:366000" 
        uid="80d105fe-07f3-0000-714b-e31d00000000"
        qualifiedName="&quot;Core&quot;.&quot;Fact - Sourcing - Negotiation Award
         &quot;"/>
       <Expr>
        <![CDATA[cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE)
         = valueof(NQ_SESSION.PRC_BU_MANAGE_NEG) AND ("Core"."Dim - Purchase
         Buyer"."Purchase Buyer Login" = valueof(NQ_SESSION."USER") OR
         cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE) =
         valueof(NQ_SESSION.PRC_BU_MANAGE_NEG_ViewOthers))]]>
       </Expr>
     </Mapping>
     <Mapping status="disable">
       <RefObject id="2035:366038" 
        uid="80d10624-07f3-0000-714b-e31d00000000"
        qualifiedName="&quot;Core&quot;.&quot;Fact - Sourcing - Negotiation
         &quot;"/>
       <Expr>
        <![CDATA[cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE)
         = valueof(NQ_SESSION.PRC_BU_MANAGE_NEG) AND ("Core"."Dim - Purchase
         Buyer"."Purchase Buyer Login" = valueof(NQ_SESSION."USER") OR
         cast("Core"."Dim - Procurement Business Unit"."Key Id" AS DOUBLE) =
         valueof(NQ_SESSION.PRC_BU_MANAGE_NEG_ViewOthers))]]>
       </Expr>
     </Mapping>
   </Filters>
   <ObjectPrivileges>
     <RefObjectPrivilege id="1500:281254" 
      uid="808626e9-05dc-0000-714b-e31d00000000" 
      qualifiedName="&quot;ObjPriv_1500:3417401144981469&quot;"/>
   </ObjectPrivileges>
</PrivilegePackage>

10.2.6 XML Elements: Object Privilege

The object privilege element corresponds to the set of object permissions you can apply to metadata objects such as logical or presentation columns. In the Administration Tool, you can set object permissions in the Presentation layer, or in the Object Permissions tab of the User/Application Role Permissions dialog.

Note:

You can also set permissions for an object privilege without specifying values in the Administration Tool. For more information, see Section 10.2.11, "XML Elements: SetPermission."

The object privilege tag includes the following attributes:

Table 10-19 Object Privilege Tag Attributes

Attribute Name Description

type

Contains the type of privilege applied to the objects. Valid values are:

  • read: corresponds to the Read privilege in theAdministration Tool

  • readWrite: corresponds to the Read/Write privilege in the Administration Tool

  • none: corresponds to the No Access privilege in the Administration Tool

This attribute can contain the following other values: delete, write, grant, and all. These other values are for internal use.


The object privilege tag includes the following child elements:

Table 10-20 Object Privilege Child Elements

Element Name Description

Objects

References the set of objects for which this privilege type applies.

Each object is contained in a sub-element called RefObject.


Syntax

<ObjectPrivilege …
     type="">
   <Description />
   <Objects>
     <RefObject …/>
     <RefObject …/>
   </Objects>
</ObjectPrivilege>

Example

<ObjectPrivilege name="ObjPriv_1500:64621257864270" 
     id="1500:6462" uid="80caa1bb-05dc-0000-714b-e31d00000000" 
     type="read">
   <Objects>
     <RefObject id="4008:43061" 
      uid="80cb6a2f-0fa8-0000-714b-e31d00000000" 
      qualifiedName="&quot;Sample Sales&quot;..&quot;Time&quot;"/>
     <RefObject id="4008:43085" 
      uid="80cb6a47-0fa8-0000-714b-e31d00000000" 
      qualifiedName="&quot;Sample Sales&quot;..&quot;More Time Objects&quot;"/>
     <RefObject id="4008:43103" 
      uid="80cb6a59-0fa8-0000-714b-e31d00000000" 
      qualifiedName="&quot;Sample Sales&quot;..&quot;Products&quot;"/>
   </Objects>
</ObjectPrivilege>

10.2.7 XML Elements: Query Privilege

The query privilege element corresponds to the set of query privileges you can apply to users or application roles. In the Administration Tool, you can set query privileges in the Query Limits tab of the User/Application Role Permissions dialog.

The query privilege tag includes the following attributes:

Table 10-21 Query Privilege Tag Attributes

Attribute Name Description

maxExecTime

The maximum number of minutes queries can run on a database.

maxExecTimePrivilege

Specifies the status of the maximum query run time limit. Valid values are:

  • Enable: Limits the time to the value specified in maxExecTime.

  • Disable: Disables any limits set in maxExecTime.

  • Warn: Does not enforce limits, but logs queries that exceed the set time limit in the Query log.

  • Ignore: Inherits limits from the parent application role. If there is no time limit to inherit, no limit is enforced.

maxRows

The maximum number of rows for users to retrieve from a database.

maxRowsPrivilege

Specifies the status of the maximum number of rows limit. Valid values are:

  • Enable: Limits the number of rows to the value specified. If the number of rows exceeds the maxRows value, the query is terminated.

  • Disable: Disables any limits set in maxRows.

  • Warn: Does not enforce limits, but logs queries that exceed the set limit in the Query log.

  • Ignore: Inherits limits from the parent application role. If there is no row limit to inherit, no limit is enforced.

populatePrivilege

Specifies whether the Populate privilege is granted or denied for a database. The Populate stored procedure writes the Cache/Saved Result Set value to the database when a criteria block is cached. Valid values are:

  • Allow: Explicitly grants the Populate privilege.

  • Disallow: Explicitly denies the Populate privilege.

  • Ignore: Inherits limits from the parent application role. If there is no limit to inherit, then the Populate privilege is allowed or disallowed based on the property Allow populate queries by default for the database object.

execPhysicalPrivilege

Specifies whether direct database requests can be executed by default. Valid values are:

  • Allow: Explicitly grants the ability to execute direct database requests.

  • Disallow: Explicitly denies the ability to execute direct database requests.

  • Ignore: Inherits limits from the parent application role. If there is no limit to inherit, then direct database requests are allowed or disallowed based on the property Allow direct database requests by default for the database object.


The query privilege tag includes the following child elements:

Table 10-22 Query Privilege Child Elements

Element Name Description

ExecTimeTable

If database access has been restricted to particular time periods, lists the time periods and whether access is allowed or disallowed.

Each time period is contained in a sub-element called Item. The Item child element has three attributes: allow (true or false), startTime, and endTime.


Syntax

<QueryPrivilege …
     maxExecTime=""
     maxExecTimePrivilege=""
     maxRows=""
     maxRowsPrivilege=""
     populatePrivilege=""
     execPhysicalPrivilege="">
   <Description />
   <ExecTimeTable>
     <Item allow="" startTime="" endTime=""/>
     <Item allow="" startTime="" endTime=""/>
   </ExecTimeTable>
</QueryPrivilege>

Example

<QueryPrivilege name="QueryPriv_4204:275811265643135" 
     id="4204:27581" uid="80cb1ae1-106c-0000-714b-e31d00000000" 
     maxExecTime="600" maxRows="100000"
     populatePrivilege="enable" execPhysicalPrivilege="enable">
</QueryPrivilege>

10.2.8 XML Elements: User

The user element corresponds to the user object in the repository. These objects represent the metadata repository copies or versions of externally managed user objects.

The user tag includes the following attributes:

Table 10-23 User Tag Attributes

Attribute Name Description

fullName

The full name of this user.

loggingLevel

The logging level for this user.

logStatisticsStatus

This attribute is not used.

guid

Global unique identifier for a given user, which is independent of the user name.


The user tag includes the following child elements:

Table 10-24 User Child Elements

Element Name Description

RefPrivilegePackage

References the privilege package, or set of object privileges, data filters, and query privileges, that apply to this user.

Groups

References the application roles to which this user belongs.

Each application role is contained in a sub-element called RefGroup.

DBSignOnList

References database login user names and passwords, along with the corresponding database, if this user has database-specific logins defined.

Each pair of database credentials and database name is contained in a sub-element called Mapping.

Each Mapping sub-element contains two additional sub-elements: RefDBSignOn, which references the database credentials, and RefDatabase, which references the database name. Note that passwords are encrypted.

See the syntax for the user element to see the complete hierarchy for the DBSignOnList child element.


Syntax

<User …
     fullName=""
     loggingLevel=""
     guid="">
   <Description />
   <RefPrivilegePackage …/>
   <Groups>
     <RefGroup …/>
     <RefGroup …/>
   </Groups>
   <DBSignOnList>
     <Mapping>
       <RefDBSignOn …/>
       <RefDatabase …/>
     </Mapping>
   </DBSignOnList>
</User>

Example

<User name="mgr" id="1501:577531" 
     uid="80ca34ae-05dd-0000-714b-e31d00000000"
     guid="D289B2F1E54411DEBFF92BEEA2576FF2">
   <RefPrivilegePackage id="4209:588476" 
    uid="80d92bbd-1071-0000-714b-e31d00000000" 
    qualifiedName="&quot;PrivPack_4209:5884761253725358&quot;"/>
   <Groups>
     <RefGroup id="4206:577530" 
      uid="80ca34b7-106e-0000-714b-e31d00000000" 
      qualifiedName="&quot;Mgr&quot;"/>
   </Groups>
</User>

10.2.9 XML Elements: Group

The group element corresponds to the application role object in the repository metadata.

The group tag includes the following attributes:

Table 10-25 Group Tag Attributes

Attribute Name Description

displayName

The custom Display Name for this application role.

logLevel

This attribute is not used.

logStatisticsStatus

This attribute is not used.

guid

Global unique identifier for a given application role, which is independent of the role name.


The group tag includes the following child elements:

Table 10-26 Group Child Elements

Element Name Description

RefPrivilegePackage

References the privilege package, or set of object privileges, data filters, and query privileges, that apply to this application role.

ChildGroups

References the set of application roles that belong to this application role.

Each child application role is contained in a sub-element called RefGroup.


Syntax

<Group …>
     displayName=""
     guid="">
   <Description />
   <RefPrivilegePackage …/>
   <ChildGroups>
     <RefGroup …/>
   </ChildGroups>
</Group>

Example

<Group name="Marketing Analytics User" id="4206:10"
     uid="0023e1a4-106e-0000-714b-e31d00000000"
     guid="Marketing Analytics User">
   <RefPrivilegePackage id="4209:281517"
    uid="0023e206-1071-0000-714b-e31d00000000" 
    qualifiedName="&quot;PrivPack_4209:651191007624440&quot;"/>
   <ChildGroups>
     <RefGroup id="4206:26" 
      uid="0023e1b5-106e-0000-714b-e31d00000000"
      qualifiedName="&quot;CM Marketing Analytics User&quot;"/>
   </ChildGroups>
</Group>

10.2.10 XML Elements: DB Sign-On

The DB sign-on element corresponds to the information provided in the Logons tab of the user object. If the repository has been set up for database-specific login IDs and passwords, you can set up database-specific credentials to allow privileged users to connect to the underlying databases at the level of authority granted to those users in the databases.

The DB sign-on tag includes the following attributes:

Table 10-27 DB Sign-on Tag Attributes

Attribute Name Description

user

The user name for the underlying database.

password

The corresponding password for the underlying database. Note that passwords are encrypted.


The DB sign-on tag does not include any child elements.

Syntax

<DBSignOn … 
     user=""
     password="">
   <Description />
</DBSignOn>

Example

<DBSignOn name="LOGON_4211:2559932074113" 
     id="4211:158" uid="309a5c29-0bf7-1000-8f7c-0ae593260000"
     user="my_db_user"
     password="BA0EAAB163">
</DBSignOn>

10.2.11 XML Elements: SetPermission

The SetPermission element is a special element, in that it does not represent a repository object. Its purpose is to define permissions to be automatically added to the Object Privilege and Privilege Package objects, without the requirement to explicitly define those objects. For more information on the objects for which these permissions can be defined, see Section 10.2.5, "XML Elements: Privilege Package" and Section 10.2.6, "XML Elements: Object Privilege."

The SetPermission element is effectively a command that is designed to set permissions on objects to users and roles.

Depending on the sub-elements chosen, SetPermission can be used to add or suppress user and role permissions on a variety of presentation and marketing objects, namely:

  • Presentation Catalog

  • Presentation Table

  • Presentation Column

  • Presentation Hierarchy

  • Presentation Level

  • Target Level

  • List Catalog

The SetPermission element, with selected sub-element and sub-element values, is first added to the XML file which is input to the XML command-line tools biserverxmlexec and biserverxmlcli. For more information on the command-line tools, see Section 6.2, "Generating and Executing XML".

When those tools are executed, SetPermission sets the appropriate permissions in the Object Privilege and Privilege Package objects that are generated automatically in output RPD. If these Object Privilege and Privilege Package objects already exist in the RPD, they will be overwritten by the execution of the SetPermission command.

Note:

The SetPermission element is only used to add information into a repository; it will not appear in the output XML file that can be generated from the Administration Tool for a repository.

The minimum requirement for a SetPermission element is that it must consist of at least one object and one role or user. The objects that are specified can exist in either in the XML input file or the RPD or both. The roles and users must be in the security realm and must also be present in the RPD or XML input file or both.

The SetPermission tag does not include any attributes.

The SetPermission tag includes the following child elements:

Table 10-28 SetPermission Child Elements

Element Name Description

Objects

References the set of objects for which this SetPermission applies.

Each object is contained in one of the following sub-elements: RefPresentationCatalog, RefPresentationTable, RefPresentationColumn, RefPresentationHierarchy, RefPresentationLevel, RefTargetLevel, RefListCatalog, each of which references its associated object type.

Role

Contains the attributes name and permission. The permission values can be read, write, none, or default.

User

Contains the attributes name and permission. The permission values can be read, write, none, or default.


Syntax

<SetPermission>
   <Objects>
     <RefPresentationCatalog…/>
     <RefPresentationTable…/>
     <RefPresentationColumn…/>
     <RefPresentationHierarchy…/>
     <RefPresentationLevel…/>
     <RefTargetLevel…/>
     <RefListCatalog…/>
   </Objects>
   <Role name="" permission=""/>
   <User name="" permission=""/>
</SetPermission>

Example

<SetPermission>
   <Objects>
     <RefPresentationCatalog
       qualifiedName="&quot;custExt3c2ce61c_0dc2_420c_b785_cf6b451deda5&quot;" /> 
   </Objects>
   <Role name="SALES_EXECUTIVE_TRANSACTION_ANALYSIS_DUTY" permission="none" /> 
   <Role name="SALES_CAMPAIGN_TRANSACTION_ANALYSIS_DUTY" permission="read" /> 
   <Role name="SALES_MANAGERIAL_TRANSACTION_ANALYSIS_DUTY" permission="read" /> 
   <Role name="SALES_TRANSACTION_ANALYSIS_DUTY" permission="read" /> 
</SetPermission>

10.2.12 XML Elements: FMW Security

The FMW security element is not used.

10.3 Other XML Elements

The elements described in this section are miscellaneous elements that do not fit into any other category. These elements include:

10.3.1 XML Elements: Project

The project element corresponds to the project object in the repository metadata. Projects support multiuser development by enabling developers to work on projects in their area of responsibility.

The project tag includes the following child elements:

Table 10-29 Project Child Elements

Element Name Description

Catalogs

References the subject areas that belong to the project.

Each subject area is contained in a sub-element called RefPresentationCatalog.

FactTables

References the logical fact tables that belong to the project.

Each fact table is contained in a sub-element called RefLogicalTable.

Groups

References the application roles that belong to the project.

Each application role is contained in a sub-element called RefGroup.

Users

References the users that belong to the project.

Each user is contained in a sub-element called RefUser.

Variables

References the variables that belong to the project.

Each variable is contained in a sub-element called RefVariable.

InitBlocks

References the initialization blocks that belong to the project.

Each initialization block is contained in a sub-element called RefInitBlock.

ListCatalogs

References the list catalogs that belong to the project.

Each list catalog is contained in a sub-element called RefListCatalog.

Tables

References the presentation tables that belong to the project.

Each presentation table is contained in a sub-element called RefPresentationTable.

Columns

References the presentation columns that belong to the project.

Each presentation column is contained in a sub-element called RefPresentationColumn.

Hierarchies

References the presentation hierarchies that belong to the project.

Each presentation hierarchy is contained in a sub-element called RefPresentationHierarchy.

Levels

References the presentation levels that belong to the project.

Each presentation level is contained in a sub-element called RefPresentationLevel.

ExcludedCatalogs

References any subject areas that do not belong to the project, but that are mapped to logical objects that do belong to the project.

Each subject area is contained in a sub-element called RefPresentationCatalog.

ExcludedTables

References any presentation tables that do not belong to the project, but that are mapped to logical objects that do belong to the project.

Each presentation table is contained in a sub-element called RefPresentationTable.

ExcludedColumns

References any presentation columns that do not belong to the project, but that are mapped to logical objects that do belong to the project.

Each presentation column is contained in a sub-element called RefPresentationColumn.

ExcludedHierarchies

References any presentation hierarchies that do not belong to the project, but that are mapped to logical objects that do belong to the project.

Each presentation hierarchy is contained in a sub-element called RefPresentationHierarchy.

ExcludedLevels

References any presentation levels that do not belong to the project, but that are mapped to logical objects that do belong to the project.

Each subject area is contained in a sub-element called RefPresentationLevel.


The project tag does not include any attributes.

Syntax

<Project …>
   <Description />
   <Catalogs>
     <RefPresentationCatalog…/>
   </Catalogs>
   <FactTables>
     <RefLogicalTable …/>
   </FactTables>
   <Groups>
     <RefGroup…/>
   </Groups>
   <Users>
     <RefUser …/>
   </Users>
   <Variables>
     <RefVariable …/>
   </Variables>
   <InitBlocks>
     <RefInitBlock…/>
   </InitBlocks>
   <ListCatalogs>
     <RefListCatalog …/>
   </ListCatalogs>
   <Tables>
     <RefPresentationTable…/>
   </Tables>
   <Columns>
     <RefPresentationColumn…/>
   </Columns>
   <Hierarchies>
     <RefPresentationHierarchy…/>
   </Hierarchies>
   <Levels>
     <RefPresentationLevel…/>
   </Levels>
   <ExcludedCatalogs>
     <RefPresentationCatalog…/>
   </ExcludedCatalogs>
   <ExcludedTables>
     <RefPresentationTable…/>
   </ExcludedTables>
   <ExcludedColumns>
     <RefPresentationColumn…/>
   </ExcludedColumns>
   <ExcludedHierarchies>
     <RefPresentationHierarchy…/>
   </ExcludedHierarchies>
   <ExcludedLevels>
     <RefPresentationLevel…/>
   </ExcludedLevels>
</Project>

Example

<Project name="FUSION_SPE" 
     id="4213:281691" uid="80ca6265-1075-0000-714b-e31d00000000">
   <Catalogs>
     <RefPresentationCatalog id="4004:275486"
      uid="80ca9dbb-0fa4-0000-714b-e31d00000000"
      qualifiedName="&quot;Sales Manager Dashboard - Campaign&quot;"/>
     <RefPresentationCatalog id="4004:275495"
      uid="80ca9e05-0fa4-0000-714b-e31d00000000"
      qualifiedName="&quot;Sales Manager Dashboard - Lead&quot;"/>
...
   </Catalogs>
   <FactTables>
     <RefLogicalTable id="2035:9160" 
      uid="00224fb6-07f3-0000-714b-e31d00000000"
      qualifiedName="&quot;Core&quot;.&quot;Fact - CRM - Order Item&quot;"/>
     <RefLogicalTable id="2035:9371" 
      uid="00224fb8-07f3-0000-714b-e31d00000000"
      qualifiedName="&quot;Core&quot;.&quot;Fact - CRM - Service Request&quot;"/>
...
   </FactTables>
   <Groups>
     <RefGroup id="4206:1" 
      uid="0023e1a2-106e-0000-714b-e31d00000000" 
      qualifiedName="&quot;BIAdministrators&quot;"/>
   </Groups>
   <Users>
     <RefUser id="1501:2" 
      uid="0021f847-05dd-0000-714b-e31d00000000"
      qualifiedName="&quot;Administrator&quot;"/>
   </Users>
   <Variables>
     <RefVariable id="3031:250" 
      uid="808466f1-0bd7-0000-714b-e31d00000000"
      qualifiedName="&quot;User Hierarchy Level&quot;.&quot;HIER_LEVEL&quot;"/>
     <RefVariable id="3031:337"
      uid="80c96155-0bd7-0000-714b-e31d00000000"
      qualifiedName="&quot;GetCRMCalendar&quot;.&quot;CRM_CAL_ID&quot;"/>
...
   </Variables>
   <InitBlocks>
     <RefInitBlock id="3033:68605" 
      uid="808466f2-0bd9-0000-714b-e31d00000000" 
      qualifiedName="&quot;User Hierarchy Level&quot;"/>
     <RefInitBlock id="3033:68645" 
      uid="80c9615a-0bd9-0000-714b-e31d00000000"
      qualifiedName="&quot;GetCRMCalendar&quot;"/>
...
   </InitBlocks>
   <ExcludedColumns>
     <RefPresentationColumn id="4010:1181008"
      uid="80ec06eb-0faa-0000-714b-e31d00000000"
      qualifiedName="&quot;Sales Manager Dashboard - Customer&quot;..&quot;
       Date&quot;.&quot;Day of Week&quot;"/>
     <RefPresentationColumn id="4010:1181009"
      uid="80ec06ec-0faa-0000-714b-e31d00000000" 
      qualifiedName="&quot;Sales Manager Dashboard - Customer&quot;..&quot;
       Date&quot;.&quot;Day of Year&quot;"/>
...
   </ExcludedColumns>
</Project>

10.3.2 XML Elements: Query Object

The query object element corresponds to the saved query object in the repository metadata. You can save a query from the Query Repository dialog in the Administration Tool.

The query object tag includes the following child elements:

Table 10-30 Query Object Child Elements

Element Name Description

QueryString

Contains the query string that qualifies and defines the query.


The query object tag does not include any attributes.

Syntax

<QueryObject …>
   <Description />
   <QueryString …/>
</QueryObject>

Example

<QueryObject name="samplequery" 
     id="4217:970" uid="c7fdc3b1-0c00-1000-8e0b-0a9702490000">
   <QueryString>
     <![CDATA[ (128 = "*") AND (6 = Business Model) AND (0) ]]>
   </QueryString>
</QueryObject>