Obiee rpd admin tools building physical layer oracle obiee

2Copyright © 2007, Oracle. All rights reserved.

Building the Physical Layer of a Repository

Copyright © 2007, Oracle. All rights reserved.2 - 2

Objectives

After completing this lesson, you should be able to:• Identify and describe the objects in the Physical layer

of a repository• Create the Physical layer of a repository


Physical Layer

• Contains objects representing the physical data sources to which Oracle BI Server submits queries

• May contain multiple data sources• Is typically the first layer built in the repository

Data sources


Physical Layer Objects

Are objects in the Physical layer, such as connection pools, folders, tables, columns, and keys• Expand a database object to display the objects it

contains.Database

Connection pool

Schema folder

Tables

Columns

Key


Database Object

• Is the highest-level object in the Physical layer• Defines the data source to which Oracle BI Server

submits queries

Database object


Database Object: General Properties

Use the General tab to view and set general properties for a database object.

Name

Type


Database Object: Features

Use the Features tab to view and set the SQL features that Oracle BI Server uses with this data source.

Default SQL features for this

data source

Enable or disable feature


Connection Pool

• Defines how Oracle BI Server connects to a data source• Specifies the ODBC or native data source name• Allows multiple users to share a pool of data source

connections

Data source name

Connection pooling enabledShared logon user

name and password

Maximum number of connections

Connection pool name


Schema Folder

Is an optional display folder that contains tables and columns for a physical schema• To create a schema folder, right-click a database object

and select New Object > Physical Schema.

Schema folder


Physical Table

• Is an object that corresponds to a table in a physical data source

• Is typically imported from a database or other data source

• Provides the metadata necessary for Oracle BI Server to access the tables with SQL requests

Physical table


Physical Table Properties

Double-click a physical table object to view its properties:

Name

Table type

Cacheable

Use tabs to create, view, or modify other properties.


Physical Table: Alias Table Type

Is a virtual physical table object that points to a physical table object• Right-click a physical table and select New Object >

Alias.• Provide a name for the alias table.• The alias table appears with an alias icon in the

Physical layer.

Alias name

Source table Alias synchronization is

automatic.


Physical Table: Select Table Type

Specifies that a physical table object is a SELECT statement

Table Type

SELECT statement

Database specific SQL


Physical Table: View Deployment

Creates a corresponding database view for metadata views

Select Deploy View.

View created in database


Physical Column

Is an object that corresponds to a column in a physical database

Columns


Key Column

Defines relationships between tables• Primary key:

– Uniquely identifies a single row of data– Consists of a column or set of columns– Is identified by a key icon

• Foreign key:– Refers to the primary key columns in another table – Is composed of a column or set of columns

Key


Joins

Represent the primary key–foreign key relationships between tables in the Physical layer

Double-click to view join properties.

Physical DiagramJoin properties

Join expression


ABC Scenario

Data for ABC resides in the SUPPLIER2 schema in an Oracle relational database, containing tables with:• Invoice data• Customer data• Product data• Period data

Import metadata using

Administration Tool

SUPPLIER2Source data

Physical layer


Implementation Steps

1. Define an ODBC System Data Source Name (DSN).2. Import the physical schema.3. Select tables and columns for import.4. Import keys and joins.5. Verify the import.6. Edit connection pool properties.7. Define physical keys and joins.


1. Define an ODBC System DSN

Use the ODBC Data Source Administrator to define a system DSN for each data source.

Data source name

TNS service name

User ID Test


2. Import the Physical Schema

Use the Oracle BI Administration Tool to import the physical schema.

Select ODBC source.

Select File > Import > from Database.


3. Select Tables and Columns for Import

Select the tables and columns needed to support the business model.

Select tables or columns for import.

Tables and keys selected by default

Filter tables for import.


4. Import Keys and Joins

Keys, foreign keys, and corresponding joins are imported automatically only if they are already defined in the data source.


5. Verify the Import

• Verify that the correct schema, tables, columns, and keys were imported.

• Use Update Row Count and View Data features to verify connection.

Schema

Tables

Columns

Key


6. Edit Connection Pool Properties

After import, verify or modify connection pool properties using the connection pool properties dialog box.

Data source name

Connection pooling enabled

Shared logon user name and

password

Maximum number of connections

Connection pool name

Call interface


7. Define Physical Keys and Joins

The Administration Tool allows you to define physical keys and joins that were not imported automatically.• Define keys using the Physical Table properties dialog

box.• Define joins and keys using the Physical Diagram.


Defining Keys Using the Table Properties Dialog

Open the table properties dialog box to view or define keys.Select the appropriate tab.

Check the appropriate check box to define the key.

Click New.


Using the Physical Diagram

Use the Physical Diagram to view or define keys and joins.

Double-click the link to open the Joins properties box.

Click the Physical Diagram icon ...

... or right-click the object to open the Physical Diagram.


Defining Foreign Key Joins

6. Join expression: first table selected maintains primary key; second table selected maintains foreign key to first table.

5. Select key columns.

1. Select New Foreign Key.

2. Select “one” table in relationship.

3. Select "many” table in relationship.

4. Physical Foreign Key

dialog opens.


Summary

In this lesson, you should have learned how to:• Identify and describe the objects in the Physical layer

of a repository• Create the Physical layer of a repository


Practice 2-1 Overview: ABC Business Scenario

This practice covers the ABC business scenario.


Practice 2-2 Overview: Gathering Information to Build an

Initial Business Model This practice covers the following topics:• Gathering and analyzing the business requirements of

the ABC company • Determining the structure of the initial business model


Practice 2-3 Overview: Creating a Repository and Importing

a Data SourceThis practice covers the following topics:• Creating a new repository• Import tables into the Physical layer of the repository


Practice 2-4 Overview: Defining Keys and Joins

This practice covers the following topic:• Defining the primary keys, foreign keys, and joins in the

Physical layer using the Administration Tool


Practice 2-5 Overview: Creating Alias and Select Tables

This practice covers the following topics:• Creating an alias table• Creating a select table• Deploying a view

Technology

Obiee rpd admin tools building physical layer oracle obiee