02 Oracle BI Architect

7/27/2019 02 Oracle BI Architect

http://slidepdf.com/reader/full/02-oracle-bi-architect 1/85

Building Oracle BI EE

Metadata on the SalesHistory (“SH”) Schema



Sales History “SH” Schema

• SH is a sample database provided by Oracle• SH comes with Oracle 9i and 10g as an

installable option

• Has multiple purposes – not just a demo for Oracle BI EE



SH Schema Diagram

Tables omitted:

Sales_ext

Profits



Use Oracle BI to:

• Understand Sales and Profit By Time • Annual, quarterly, monthly, and weekly sales -- trends.

• Understand Sales and Profit By Distribution Channel• Which distribution channels are performing?

• Understand Sales and Profit by By Promotion• When the company runs special promotions on its products,

what is the impact on sales?

• Understand Sales and Profit By Geography• What countries, regions, states are doing well?

• Understand Sales and Profit by Product• What categories, sub-categories, and SKUs are selling or

not selling?



Steps to build metadata for SH

• Open Analytics Administration Tool

• Create a new repository from scratch

• Perform three steps:

1. Import schema information into Physical Layer

2. Build a Business Model and map model to sources

3. Build Presentation Catalog from Business Model



Stop Server and Web Server



Create a new repository

• Open the administration tool

• Create a new repository

(.RPD file)



Prerequisites

• Understand Answers – see tutorial on SH Web• Have installed SH database with user="sh" and

password = "sh"

• Create an Oracle TNSName that will allow you to

query SH. It is called "ORCL" in this tutorial.• Create a system ODBC DSN (data source name)

that uses the Oracle TNSName. See next slide.



Create ODBC System DSNSystem

tab

Add

Find

Oracle's

ODBCdriver

Test

connection

Accept all

defaults



Step 1: Import Schema

• File Import From Database

• Select ODBC System Data Source Name

(create the DSN first)



Import Schema (cont.)

.



Import Schema (final)



Update Row Counts, View Data

After importing schema information, it is often useful to see how

many rows tables contain, to see how many values each column

contains, and to actually view the data.



Specify Joins• Easiest way: use physical diagram

• Two types of joins: Key/FKey and Complex• Creating K/FK joins also defines keys and foreign keys

• Joins could be imported if Foreign Keys defined in db(but not recommended)



Step 2: Create Business Model• Move to middle layer (“Business Model and Mapping”)

• Create new business model• Create logical table to hold facts (aggregatable columns – sum,count, max, etc.)

• Add fact to logical table by dragging column from physical layer and setting aggregation rule



Add Attributes

• Need logical tables to hold attributes

• Attr ibutes = columns that aren’t aggregated

• Logical tables holding attributes are dimension tables

• Either of these methods is OK:

• Drag physical table onto business model. Logical tables are

created and are mapped directly to the physical tables. Tip: just drag the physical tables that are directly joined to fact

tables (unless they are “bridge” tables used to express N:N

relationship)

• Create logical table. Drag columns you want from physical

table.



• Use Business Model Diagram• Logical joins connect logical tables

• Use “New Complex Join” button

• Accept the defaults (almost always…)

• Join type (inner, outer, left outer, right outer) affects physical joins in SQL

• “Driving table” used in cross-database joins

• Cardinality differentiates logical fact table from logical

dimension tables.

Add Logical Joins

NOTE: After you create logical joins,

the dimension tables are white and

the fact table is yellow.



Prune Logical Columns

• Prune most codes – you can put them backlater if you are wrong

• Columns that hold duplicate information

• Columns that don’t seem analytically important

(view data to check)• Leave logical columns in dimension tables that

are primary keys of physical tables (notessential but helpful later on)



Logical Dimension Tables

• Have logical keys• Physical keys logical keys when dragged

• Have no columns with aggregation rules

• Attributes can have hierarchical relationships to each

other (many values of attribute A associated with asingle value of attribute B)

• Hierarchical relationships between attributes can be

expressed in hierarchies (later)



Rename tables and columns

• Develop meaningful names for logical columns andtables

• Recommended: decide names before savinganalyses and building dashboards

• Two ways to re-name objects in the business model:•

Manually – Select Object

Properties

<Change name>• Re-name wizard (demo shows this)



Dimension Hierarchies

• Hierarchies express 1:N relationships among attributes – and also a drill path

• Have at least two levels: Grand Total and Detail

• Recommend: start at detail and add parent – go up thehierarchy

• The rules are:• All levels have “level keys” except Grand Total

• When there are multiple attributes at a level, their values aredependent on the value of the level key attribute

• Level key of detail level is key of logical table

• Grand Total level usually has no attributes

• If there are multiple keys, pick one to “use for drill down”



Review of Hierarchies

• “Create Dimension” creates hierarchy with two levels,Detail and Grand Total

• Level keys needed for all levels except Grand Total

• Table key set as level key for Detail level

• “Drilling” in web goes down hierarchy via level keys

• When > 1 level key, specify which to “use for drill down”

• “Number of elements at this level”

• Used for aggregate table navigation

• Does not have to be precise

• Use “update row count” to see current value



A Note on Total Level

• Difference between Grand Total level and Total Attribute level• Grand Total – no attributes• Total Attribute level, optional, has an attribute value and a level key

• Other approaches are possible• Include Total attribute in grand total level (no level key)

• Include Total attribute as attribute in next level down

• Could model Total Attribute level using a constant in the logical table

source:



Create Channel Hierarchy



Create Promotion Hierarchy



Create Times Hierarchy

One difference --

create twohierarchies(calendar andfiscal) for thesame

dimension



Create Customer Hierarchy

• Need to add country

attributes in a

second physical

table

• Suggestion: keep

single dimension

table

• Note second

technique used to

set attribute level

• Note “new child

level”



Review Business Model Objects

Created from

menu or when

physical object

dragged intomiddle layer



Logical Table Source (LTS)

• Create from menu OR by draggingphysical table or column to businessmodel layer

• Contains logical to physical mappings



Create Presentation Catalog

• Business models themselves are not visible to users• Users see presentation catalogs whose columns are

defined in business models.

• Presentation catalogs appear as “subject areas” in the

web UI• Presentation catalogs are “databases” to client tools

using ODBC

• To create a presentation catalog, drag business model

to left panel. Then customize – re-order, re-folder, re-name.



Check Consistency

• After presentation catalog exists, check consistency• “Consistent” if:

>1 logical table

Logical tables joined

Logical dimension tables have keys

Logical columns mapped to sources

Hierarchies are consistent with sources

Business model has presentation catalog

No leading or trailing spaces in column names

Dimension sources join to fact sources



Create New Web Catalog

Delete all filesSH*.*

Where web

catalog

specified

Since sh directory does not exist any longer, the web server will create a

new one.

Go to this

folder



Preparing to test

• Loglevel 2 already set• NQSConfig.ini

<logical name> =

<filename>, default;

# comment

“NO” disables caching

Location of

NQSConfig.ini



Start (or re-start) servers

• Start Analytics Server -- re-start if already started• Start Analytics Web if not started

• Start Analytics Java Host if not started



Open RPD in Online Mode

OR

Via Menu Via Toolbar

Select the BI ODBC data sourcethat points to the rpd If blank, then the default rpd set

in NQSConfig.ini



Online Mode (cont.)

• Multi-user editing possible

• Objects must be checked out• Changes effective when objects are

checked in

• Automatic checkout using ToolsOptions

menu• Menu option FileUndo All Checkouts

available

• Change in presentation layer requiresReload Server Metadata on web server

Only web administrators

see this link



Add Costs Measure

• Costs table has productcosts for each combination

of period, promotion,

product, channel (not

customer)• Join Costs table to

customer via Sales table to

get costs of sales for each

customer



Add Costs Measure (cont.)

• Steps:• Add joins in physical layer

Control-Click on multiple columnscreates compound join andcompound key

•

Drag column to business model,creating logical column

Drag onto existing LTS in thiscase

Set aggregation rule

Re-name logical column• Add measure to presentation layer

• Check in changes

Note: Join

between Costs

and Sales

already defined

for you.

Blue indicates

new object



Why add Costs to existing LTS?

• If separate LTS, generates second query if “AmountSold” and “Unit Cost” are in the projection list

• Costs table will be included only if Unit Cost is in

projection list – otherwise the join is eliminated

• Join elimination determined by cardinality of join (Nside is Sales, 1 side is Costs)

Note that

COSTS does

not join directlyto dimension

tables



Query Cost Data

• Select Subject Area• Refresh Server

Metadata

• Click on columns

• Get results

• View Query Log



Create Formula in the Web

• Add a column from left panel• Use Fx button in column in Criteria tab to

enter formula

• When creating formula, click on column

names in the left panel



Save Query in Web Catalog

• Create new catalogfolder

• Save Query

• Examine catalog



Modify query

• Modify query (deletecolumn with web

formula)

• Re-save the query



Create Measure in Metadata

• Why create measures in metadata rather than web?

• Web formulas are only saved within the query

(modify query and then Save As a new query).

• Write formula once in metadata, “official” • If business rules change, modify formula in one

place, not in every analysis and report



Two Ways to Create Measures in Metadata

• Create logical column, define in terms of existing logical columns

• Create logical column, map to physical

columns in tables in the LTS.

Create logical column define in terms



Create logical column, define in terms

of existing logical columns

Create logical column map to



Create logical column, map to

physical columns in tables in the LTS

Create logical column map to physical



Create logical column, map to physical

columns in tables in the LTS (Cont)



Compare Methods

• Using Logical Columns• Aggregation of base

measures occurs first

Sum(Actual Amount)-

Sum(Unit Cost)

•

Inherit aggregatesources

• Mapped in LTS• Aggregation occurs after

computation

Sum(Actual Amount-Unit Cost)

• Have to be re-mapped if

there are aggregatesources



Create Measures Using Functions

• Display Functions:• Analytics server has several functions that

are non-standard SQL functions, like Rank(),nTile, mavg, msum, stddev,…

• Operate on the result set obtained from all

the other filters

• Create Rank Amount Sold measure (rankoverall)

• Create Rank Amount Sold withinCategory



Review

• New column =

Rank(existing column)

• Hierarchy level used to

create rank within Category

– an example of a “level-

based measure”

• New column = Existing

column to level

• You can filter on display

functions – e.g. top 5

products in each category Top 5 in Each Category



Add Filter View

• Add Filter view to showfilters to user

• Move Filter view under

Title view

• Save Analysis with new

name, which appears in

Title view

• Preview (allow popups)

Add filter view



New Measure: Category Sales

• Category Sales gives sales at category level• Method:

• duplicate existing “Amount Sold”

• re-name, set aggregation level

Create measure Test measure



Share of Category

• Share of Category = 100 * Amount Sold/Category

Sales

• Use level-based measure in denominator

• Calculation Wizard available



Time Series Comparisons

• Usage• User filters on time

• User can select measures that compare this time

with same data month ago, year ago, quarter ago, …

Sales Year Ago, Change vs. Yago, % Change vs. Yago• Can use “Time Series Wizard” when period

table that contains keys of the comparison

periods

• Otherwise, set up manually (case with SH)



Time Series Manual Setup• Different physical join from period table to fact table

•

Use fact table alias• Create new fact table source for time ago measures

• Include alias of period table in fact table source

• Use Calculation Wizard to create comparison measures

Aliases and

joines already

defined in

SH36.rpd



Review MAgo

• New joins required for existing tables• Solution: create aliases of existing fact andtime physical tables

• Set up joins so that time periods match with

correct fact table records• Create new fact table source

• Include time alias in fact table source (will onlybe used when MAgo fact is in query)

U M



Use Mago

M Q L



Mago Query Log

Join for Month Ago

Join for time period

2 LTSs,

2 Queries

P t ti L



Presentation Layer

• Business model layer is about content.Presentation layer is about looks.

• Simplify content of the business model and

present it in the best order and folder structure

• Rename columns for particular set of users (or tools)

• Security can be set here (or in the business

model)

P t ti C t l



Presentation Catalogs

• All columns in a presentation catalog come from same business model

• Multiple presentation catalogs can refer to the same business model

Catalog for

user group 1

Catalog for

user group 2

Both reference

same businessmodel

P t ti T bl d C l



Presentation Tables and Columns

• What users see in Answers• Folders, sub-folders, and columns in Answers

• Column ordering

Presentation

Table

Presentation

Column

Subject area

C t N P t ti C t l



• Drag and drop a business model from theBusiness Model layer to the Presentation

layer

• Duplicate to copy an existing catalog

Create a New Presentation Catalog

Dragging and dropping

creates the new catalog

Create a New Presentation



• Corresponding presentation layer objects areautomatically created for business model

layer objects

Create a New Presentation

Catalog Continued

Business model

becomes presentation

catalog

Logical tables become

presentation tables

Logical columns become

presentation columns

Hierarchies not seenexcept in default drill

behavior



R d T bl



Reorder Tables

Use the Presentation Tables

tab and the Up and Down

buttons to reorder tables

Double-click

R d C l



Reorder Columns

Use the Columns taband the Up and

Down buttons to

reorder columns

P t ti T bl G l t b



Presentation Table General tab

For

localization

Double-click

Rename

“Tool tip” in

Answers

Which users

will see this

table

Rename Tables



Rename Tables

• Admin tool creates an alias automatically when the

name of a presentation table changes

Use the Aliases tab

to view the previous

name

Rename Columns



Rename Columns

• Use the General tab to rename columns in the

Presentation Column properties box

Custom name

Uncheck to

specify a name

that is different

from the logical

column name

“Tool tip” in Answers

Which users

will see this

table

Click to edit logical

column in business

model

Column Alias



Column Alias

• Created automatically when presentationcolumn name changes

Trim Columns



Trim Columns• Remove keys

unless they havean intrinsic

meaning, such

as date.

• Remove

uninterestingcolumns (e.g. 1

value)

• Rule of thumb: 7

to 12 columns

per folder

Considerations



Considerations

• By default, Presentation columns (not tables)are renamed automatically when the

corresponding logical column name changes

• Presentation tables cannot have the same

name as the presentation catalogs (error isreceived)

• Presentation objects can be deleted without

affecting corresponding logical objects

Catalog General Tab



Catalog General Tab

Expose the

logical keys to

other ODBC

clients. Notrelevant for

Answers.

Set fact that will be

used to join

dimension tableswhen query consists

of >1 dimension and

no facts.

Leading Practices



Leading Practices

• Names can not containsingle quotes (') or double quotes

• Uniqueness removesambiguity in queryfilters (table names notshown)

• Rule of “7-12”

• Use nested folders

-> Characters in description

will cause folder to appear

nested in first folder above it

that is not nested

Demo: Presentation Layer



Demo: Presentation Layer

Add and re-order tables Move columns – use Query

to select and “mark” columns

Re-order columns (>7 mins)

Run times 3:12,

2:53, 7:21

Check Presentation Layer



Check Presentation Layer

View SH in Answers



View SH in Answers

• Check appearance of SH in Answers

• Because table.column associations have changed, re-

set default formats for numeric columns

Playing time1:13

Intro to Security



Intro to Security

• Usually, list of valid users and passwords are stored externally

• Analytics Server usually set up to authenticate users againstexternal sources (LDAP server or database table)

• List of user groups (roles) is stored in metadata

• User membership in groups is passed to server duringauthentication process

• Depending on group membership, queries are filtered to returninformation that is relevant to user’s role in the enterprise

Authentication Process



Authentication Process

BI

Server Web

Server

Metadata

initialization

block

LDAP

:USER

:PASSWORD

:USER

:PASSWORD

Authenticated,

Groups Authenticated,

Groups

Data

Queries on default

dashboard

Results

Results

Session

variables set Query (sql)

with session

filters

User logs on

using browser User seesdashboard

Demo security



Demo security

• Manage Security• Users named in RPD (normally external)• Groups listed in RPD

• Group membership in RPD (normally external)

• Group “CountryManagers” has filter on SH.Customerspresentation table

• Manage Variables• Initialization block sets session variables USER and

UserCountry

• Manage Sessions• Administrator can view sessions and values of

variables

• Different users see different results on samedashboard

Repository Variables



Repository Variables

• Same value for all users

• Two types

• Static

value set in RPD and does

not change

• Dynamic

updated by results of

initialization block

initialization block

executes per schedule

• Typical uses

• in formulas

• In content tab of LTS

• In saved filters in Web

Initialization Blocks



Initialization Blocks

Setting and Using Variables



Demo

Your final repository



Your final repository

• Create and add interesting measures…

See SH83.rpd

Date post:	02-Apr-2018
Category:	Documents
Upload:	anandh-kumar
View:	225 times
Download:	1 times

02 Oracle BI Architect

Documents