4-18 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
■
See Importing Metadata from XML Data Sources
for XML.
■
See Importing Metadata from Relational Data Sources
for ODBC 2.0, OCI 10g11g
, and DB2 CLI Unicode.
■
See Chapter 5, Working with ADF Business Component Data Sources
for
OracleADF_HTTP .
When you have finished providing information in the Select Data Source screen, click Next.
3.
For Oracle RPAS data sources only, the Select Metadata Types screen is displayed. For Oracle RPAS, select Tables, Keys, and Foreign Keys. Then, click Next.
See About Importing Metadata from Oracle RPAS Data Sources
for more information.
4.
In the Select Metadata Objects screen, select the objects you want to import in the Available
list and move them to the Selected list, using the Import selected or Import all buttons. You can also move objects from the Selected list back to
the Available list, using the Remove selected and Remove all buttons. To search for a particular item, enter a keyword in the Find box and then click
Find Down or Find Up.
Select Show complete structure to view all objects, including those that have already been imported. Deselecting this option shows only the objects that are
available for import. When this option is selected, objects that have already been imported appear grayed out
For Essbase data sources, select Import UDAs if you want to import UDAs user-defined attributes.
5. Click Finish.
If some objects could not be imported, a list of warning messages appears. In the dialog displaying the messages, you can perform the following actions:
– To search for specific terms, click Find and then Find Again.
– To copy the contents of the window so that you can paste the messages in
another file, click Copy.
After you import metadata, you should check to ensure that your database and connection pool settings are correct. In rare cases, the Oracle BI Server cannot
determine the exact database type during import and instead assigns an approximate type to the database object. See
Setting Up Database Objects and
Creating or Changing Connection Pools
for more information about working with these objects. It is also a good practice to visually inspect the imported data in the Physical layer,
such as physical columns and hierarchical levels, to ensure that the import completed successfully.
For Essbase data sources, all hierarchies are imported as Unbalanced by default. Review the Hierarchy Type property for each physical hierarchy and change the value
if necessary. Supported hierarchy types for Essbase are Unbalanced, Fully balanced, and Value.
About Importing Metadata from Oracle RPAS Data Sources
This section provides important information about using the Administration Tool to import metadata from Oracle RPAS, as follows:
■
Oracle RPAS schemas can only be imported on Windows.
Importing Metadata and Working with Data Sources 4-19
■
Before you import RPAS schemas, you must set the Normalize Dimension Tables field value in the ODBC DSN Setup page to Yes for the following reasons:
– Setting this value to Yes uses an appropriate schema model the snowflake
schema that creates joins correctly and enables drill down in the data.
– Setting this value to No uses a less appropriate schema model the star
schema that creates joins between all of the tables, causing drill down to not work correctly. Many of the joins created in this way are unwanted, and
would need to be removed manually.
See Setting Up ODBC Data Source Names DSNs
for more information.
■
When you import RPAS schemas in the Administration Tool, you must import the data with joins. To do this, select the metadata types Keys and Foreign Keys in the
Import Metadata Wizard.
■
After you have imported RPAS schemas, you must change the Normalize Dimension Tables
field value in the ODBC DSN Setup page back to No. You need to revert this setting back to No after import to enable the Oracle BI Server to
correctly generate optimized SQL against the RPAS driver.
Note: If you do not change the Normalize Dimension Tables setting value to No,
most queries will fail with an error message similar to the following: [nQSError: 16001] ODBC error state: S0022 code: 0 message: [Oracle Retail][RPAS
ODBC]Column:YEAR_LABEL not found..[nQSError: 16014] SQL statement preparation failed. Statement execute failed.
■
If Oracle RPAS is the only data source, you must set the value of NULL_VALUES_ SORT_FIRST to ON in the NQSConfig.INI file. See Oracle Fusion Middleware System
Administrators Guide for Oracle Business Intelligence Enterprise Edition for more information about setting values in NQSConfig.INI.
Importing Metadata from XML Data Sources
This section describes the use of the Extensible Markup Language XML as a data source. XML is the universal format for structured documents and data on the Web. It
can also be used as a database to store structured data.
The Oracle BI Server supports various XML access modes, including access through the Oracle BI Server XML Gateway, as well as access through an XML ODBC driver.
This section contains the following topics:
■
About Using XML as a Data Source
■
Importing Metadata from XML Data Sources Using the XML Gateway
■
Importing Metadata from XML Data Sources Using XML ODBC
■
Examples of XML Documents
About Using XML as a Data Source
The Oracle BI Server supports the use of XML data as a data source for the Physical layer in the repository. Depending on the method used to access XML data sources, a
data source may be represented by a URL pointing to one of the following sources:
■
A static XML file or HTML file that contains XML data islands on the Internet including intranet or extranet. For example:
tap:216.217.17.176[DE0A48DE-1C3E-11D4-97C9-00105AA70303].XML
4-20 Metadata Repository Builders Guide for Oracle Business Intelligence Enterprise Edition
■
Dynamic XML generated from a server site. For example: tap:www.aspserver.comexample.asp
■
An XML file or HTML file that contains XML data islands on a local or network drive. For example:
d:xmldirexample.xml d:htmldirisland.htm
You can also specify a directory path for local or network XML files, or you can use the asterisk as a wildcard with the filenames. If you specify a directory
path without a filename specification like d:xmldir, all files with the XML suffix are imported. For example:
d:xmldir d:xmldirexam.xml
d:htmldirexam.htm d:htmldirexam.html
■
An HTML file that contains tables, defined by a pair of table and table tags. The HTML file may reside on the Internet including intranet or extranet, or on a
local or network drive. See Accessing HTML Tables
for more information. URLs can include repository or session variables, providing support for HTTP data
sources that accept user IDs and passwords embedded in the URL. For example: http:somewebservercgi.pl?userid=valueofsession_variable1password=
valueofsession_variable2 This functionality also lets you create an XML data source with a location that is
dynamically determined by some run-time parameters. For more information about variables, see
Chapter 18 .
If the Oracle BI Server needs to access any nonlocal files network files or files on the Internet, for example, you must run the Oracle BI Server using a valid user ID and
password with sufficient network privileges to access these remote files.
Importing Metadata from XML Data Sources Using the XML Gateway
Using the Oracle BI Server XML Gateway, the metadata import process flattens the XML document to a tabular form using the stem of the XML filename that is, the
filename without the suffix as the table name and the second level element in the XML document as the row delimiter. All leaf nodes are imported as columns
belonging to the table. The hierarchical access path to leaf nodes is also imported.
The Oracle BI Server XML Gateway uses the metadata information contained in an XML schema. The XML schema is contained within the XML document, or is
referenced within the root element of the XML document.
Where there is no schema available, all XML data is imported as text data. In building the repository, you can alter the data types of the columns in the Physical layer,
overriding the data types for the corresponding columns defined in the schema. The gateway converts the incoming data to the desired type as specified in the Physical
layer. You can also map the text data type to other data types in the Business Model and Mapping layer of the Administration Tool, using the CAST operator.
The Oracle BI Server XML Gateway does not support:
Importing Metadata and Working with Data Sources 4-21
■
Resolution of external references contained in an XML document other than a reference to an external XML schema, as demonstrated in the example file in
Examples of XML Documents Generated by the Oracle BI Server XML Gateway .
■
Element and attribute inheritance contained within the Microsoft XML schema.
■
Element types of a mixed content model such as XML elements that contain a mixture of elements and CDATA, such as p hello bJoeb, how are you
doing?p.
To import XML data using the Oracle BI Server XML Gateway: 1.
In the Administration Tool, select File, then select Import Metadata. The Import Metadata Wizard appears.
Figure 4–3 shows the Import Metadata Wizard.
Figure 4–3 Import Metadata Wizard: XML Data Source
Note that the Map to Logical Model and Publish to Warehouse screens in the Import Metadata Wizard are reserved for a future release. Check the Oracle
Business Intelligence chapter in Oracle Fusion Middleware Release Notes for updates about the functionality in these two screens.
2. In the Select Data Source screen, select XML for Connection Type. Then, provide
