Professional Documents
Culture Documents
Enterprise Edition
Hands-On Workshop
Student Handbook
Administration Tool
(Building the Physical Layer of a
Repository)
Page 1
Table of Contents
Purpose ..................................................................................................................................................... 3
Overview ................................................................................................................................................... 4
Prerequisites ............................................................................................................................................. 5
Building the Physical Layer of a Repository.............................................................................................. 6
Create a New Repository......................................................................................................... 6
Import Metadata ....................................................................................................................... 9
Verify Connection................................................................................................................... 19
Create Aliases........................................................................................................................ 23
Create Keys and Joins ........................................................................................................... 27
Page 2
Purpose
This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool to build, modify, enhance, and manage an Oracle BI
repository.
Page 3
Overview
This tutorial shows you how to build an Oracle BI metadata repository using the Oracle BI Administration Tool. You learn how to import
metadata from databases and other data sources, simplify and reorganize the imported metadata into a business model, and then structure
the business model for presentation to users who request business intelligence information via Oracle BI user interfaces.
Page 4
Prerequisites
Before starting this tutorial, you should:
1. Have access to or have Installed Oracle Business Intelligence Enterprise Edition 11g.
2. Have access to or have installed the Sample Application schema (BISAMPLE) that ships with
Oracle Business Intelligence 11g. You can access the BISAMPLE schema and installation
instructions here.
If you are interested in downloading and installing the latest version of the entire Sample
Application, you can access it here on the Oracle Technical Network (OTN). Please note,
however, that only the BISAMPLE schema is required to complete this tutorial.
Paste in C:\mw_home\Oracle_BI1\network\admin
Go to
C:\mw_home\instances\instance1\bifoundation\OracleBIApplication\coreapplication\setu
p and edit user.cmd
o
Page 5
Import Metadata
Verify Connection
Create Aliases
1. Select Start > Programs > Oracle Business Intelligence > BI Administration to open the
Administration Tool.
Page 6
3. Enter a name for the repository. In this tutorial the repository name is BISAMPLE.
Page 7
4. Leave the default location as is. It points to the default repository directory.
6. Enter and retype a password for the repository. In this tutorial BISAMPLE is the repository
password.
Page 8
7 . Click Next.
Import Metadata
1 . Change the Connection Type to OCI 10g/11g. The screen displays connection fields based on
the connection type you selected.
Page 9
2 . Enter a data source name. In this example the data source name is orcl. This name is the same as
the tnsnames.ora entry for this Oracle database instance.
Page 10
3 . Enter a user name and password for the data source. In this example the username and password
are bothBISAMPLE. Recall that BISAMPLE is the name of the user/schema you created in the
prerequisite section.
Page 11
4 . Click Next.
Page 12
Page 13
8 . Click the Import Selected button to add the tables to the Repository View.
Page 14
9 . The Connection Pool dialog box appears. Accept the defaults and click OK.
Page 15
Page 16
11 . When import is complete, expand BISAMPLE in the Repository View and verify that the five
tables are visible.
Page 17
Page 18
13 . Expand orcl > BISAMPLE and confirm that the five tables are imported into the Physical layer
of the repository.
Verify Connection
Page 19
2 . When update row counts completes, move the cursor over the tables and observe that row count
information is now visible, including when the row count was last updated.
Page 20
3 . Expand tables and observe that row count information is also visible for individual columns.
4 . Right-click a table and select View Data to view the data for the table.
Page 21
5 . Close the View Data dialog box when you are done. It is a good idea to update row counts or
view data after an import to verify connectivity. Viewing data or updating row count, if
successful, tells you that your connection is configured correctly.
Page 22
Create Aliases
1 . It is recommended that you use table aliases frequently in the Physical layer to eliminate
extraneous joins and to include best practice naming conventions for physical table names.
Right-click SAMP_TIME_DAY_D and selectNew Object > Alias to open the Physical Table
dialog box.
Page 23
3 . In the Description field, enter Time Dimension Alias at day grain. Stores one record for each
day.
Page 24
4 . Click the Columns tab. Note that alias tables inherit all column definitions from the source table.
Page 25
6 . Repeat the steps and create the following aliases for the remaining physical tables.
SAMP_ADDRESSES_D = D4 Address
SAMP_CUSTOMERS_D = D3 Customer
SAMP_PRODUCTS_D = D2 Product
SAMP_REVENUE_F = F1 Revenue
Page 26
2 . Right-click one of the highlighted alias tables and select Physical Diagram > Selected
Object(s) Only to open the Physical Diagram. Alternatively, you can click the Physical Diagram
button on the toolbar.
Page 27
3 . Rearrange the alias table objects so they are all visible. If desired, right-click in the white space
of the diagram and select Zoom to change the size of the objects in the Physical Diagram.
Page 28
5 . Click the D1 Time table, and then click the F1 Revenue table. The Physical Foreign Key dialog
box opens. It matters which table you click first. The join creates a one-to-many (1:N)
relationship that joins the key column in the first table to a foreign key column in the second
table.
Page 29
Page 30
7 . Click OK to close the Physical Foreign Key dialog box. The join is visible in the Physical
Diagram.
Page 31
8 . Repeat the steps to create joins for the remaining tables. Use the following expressions as a
guide:
"orcl".""."BISAMPLE"."D2 Product"."PROD_KEY" = "orcl".""."BISAMPLE"."F1
Revenue"."PROD_KEY"
"orcl".""."BISAMPLE"."D4 Customer"."CUST_KEY" = "orcl".""."BISAMPLE"."F1
Revenue"."CUST_KEY"
"orcl".""."BISAMPLE"."D5 Address"."ADDRESS_KEY" = "orcl".""."BISAMPLE"."D4
Customer"."ADDRESS_KEY"
Page 32
9 . Click the X in the upper right corner to close the Physical Diagram.
10 . Select File > Save or click the Save button on the toolbar to save the repository.
11 . Click No when prompted to check global consistency. Checking Global Consistency checks for
errors in the entire repository. Some of the more common checks are done in the Business Model
and Mapping layer and Presentation layer. Since these layers are not defined yet, bypass this
check until the other layers in the repository are built. You learn more about consistency check
later in this tutorial.
12 . Leave the Administration Tool and the repository open for the next topic.
Congratulations! You have successfully created a new repository, imported a table schema from
an external data source into the Physical layer, created aliases, and defined keys and joins.
Page 33
In the next topic you learn how to build the Business Model and Mapping layer of a repository.
Page 34
Page 35