creating a repository using obi administration tool

8/9/2019 Creating a Repository Using OBI Administration Tool

1/354

Creating a Repository Using the Oracle Business Intelligence

Administration Tool

This tutorial contains the following sections:

Purpose

Time to Complete

Overview

Prerequisites

Building the Physical Layer of a Repository

Building the Business Model and Mapping Layer of a

Repository

Building the Presentation Layer of a Repository

Testing and Validating a Repository

Managing Logical Table SourcesCreating Calculation Measures

Creating Logical Dimensions with Level-Based

Hierarchies

Creating Level-Based Measures

Creating Logical Dimensions with Parent-Child

Hierarchies

Creating Logical Dimensions with Ragged and

Skipped-Level Hierarchies

Using Aggregates

Using Initialization Blocks and Variables

Creating Time Series Measures

Summary

Resources

Purpose

This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool to build, modify, enhance, and

manage an Oracle BI repository. This tutorial is built using OBI EE 11.1.1.3. There will be some differences if you are

testing with 11.1.1.5, such as in Create Keys and Joins, Check Consistency, and Set Up Query Logging. There is a new

tutorial based on OBI EE 11.1.1.5, please check here.

Time to Complete

Approximately 6 hours.

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.

Prerequisites

Creating a Repository Using the Oracle BI Admini... http://www.oracle.com/webfolder/technetwork/t

of 355 01/21/2015 01:53


2/354

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 hereon the Oracle Technical Network (OTN). Please note, however, that only the BISAMPLE schema is required to

complete this tutorial.

Building the Physical Layer of a Repository

In this topic you use the Oracle BI Administration Tool to build the Physical layer of a repository.

The Physical layer defines the data sources to which Oracle BI Server submits queries and the relationships between

physical databases and other data sources that are used to process multiple data source queries. The recommended

way to populate the Physical layer is by importing metadata from databases and other data sources. The data sources

can be of the same or different varieties. You can import schemas or portions of schemas from existing data sources.

Additionally, you can create objects in the Physical layer manually.

When you import metadata, many of the properties of the data sources are configured automatically based on the

information gathered during the import process. After import, you can also define other attributes of the physical data

sources, such as join relationships, that might not exist in the data source metadata. There can be one or more data

sources in the Physical layer, including databases, flat files, XML documents, and so forth. In this example, you import

and configure tables from the BISAMPLE schema included with the Oracle BI 11g Sample Application.

To build the Physical layer of a repository, you perform the following steps:

Create a New Repository

Import Metadata

Verify Connection

Create Aliases

Create Physical Keys and Joins


Import Metadata

Verify Connection

Create Aliases

Create Keys and Joins


1. Select Start > Programs > Oracle Business Intelligence > BI Administrationto open the Administration Tool.


2 of 355 01/21/2015 01:53


3/354

2. Select File > New Repository.

3. Enter a name for the repository. In this tutorial the repository name is BISAMPLE.


3 of 355 01/21/2015 01:53


4/354

4. Leave the default location as is. It points to the default repository directory.

5. Leave Import Metadata set to Yes.

6. Enter and retype a password for the repository. In this tutorial BISAMPLEis the repository password.


4 of 355 01/21/2015 01:53


5/354

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.


5 of 355 01/21/2015 01:53


6/354

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.


6 of 355 01/21/2015 01:53


7/354

3 . Enter a user name and password for the data source. In this example the username and password are both

BISAMPLE. Recall that BISAMPLE is the name of the user/schema you created in the prerequisite section.


7 of 355 01/21/2015 01:53


8/354

4 . Click Next.

5 . Accept the default metadata types and click Next.


8 of 355 01/21/2015 01:53


9/354

6 . In the Data source view, expand the BISAMPLEschema.

7 . Use Ctrl+Clickto select the following tables:

SAMP_ADDRESSES_D

SAMP_CUSTOMERS_D

SAMP_PRODUCTS_D

SAMP_REVENUE_F

SAMP_TIME_DAY_D


9 of 355 01/21/2015 01:53


10/354

8 . Click the Import Selected buttonto add the tables to the Repository View.


0 of 355 01/21/2015 01:53


11/354

9 . The Connection Pool dialog box appears. Accept the defaults and click OK.


1 of 355 01/21/2015 01:53


12/354

10 . The Importing message appears.


2 of 355 01/21/2015 01:53


13/354

11 . When import is complete, expand BISAMPLEin the Repository View and verify that the five tables are visible.


3 of 355 01/21/2015 01:53


14/354

12 . Click Finishto open the repository.


4 of 355 01/21/2015 01:53


15/354

13 . Expand orcl > BISAMPLEand confirm that the five tables are imported into the Physical layer of the repository.

Verify Connection

1 . Select Tools > Update All Row Counts.


5 of 355 01/21/2015 01:53


16/354

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.


6 of 355 01/21/2015 01:53


17/354

3 . Expand tables and observe that row count information is also visible for individual columns.

4 . Right-click a table and selectView Datato view the data for the table.


7 of 355 01/21/2015 01:53


18/354

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 isconfigured correctly.


8 of 355 01/21/2015 01:53


19/354

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_Dand select New

Object > Aliasto open the Physical Table dialog box.

2 . EnterD1 Timein the Name field.


9 of 355 01/21/2015 01:53


20/354

3 . In the Description field, enter Time Dimension Alias at day grain. Stores one record for each day.


20 of 355 01/21/2015 01:53


21/354

4 . Click the Columnstab. Note that alias tables inherit all column definitions from the source table.


21 of 355 01/21/2015 01:53


22/354


23/354

Create Keys and Joins

1 . Select the five alias tables in the Physical layer.

2 . Right-click one of the highlighted alias tables and select Physical Diagram > Selected Object(s) Onlyto open the

Physical Diagram. Alternatively, you can click the Physical Diagram button on the toolbar.


23 of 355 01/21/2015 01:53


24/354

3 . Rearrange the alias table objects so they are all visible. If desired, right-click in the white space of the diagram andselect Zoom to change the size of the objects in the Physical Diagram.


24 of 355 01/21/2015 01:53


25/354

Building the Business Model and Mapping Layer of a Repository

In this topic you use the Oracle BI Administration Tool to build the Business Model and Mapping layer of a repository.

The Business Model and Mapping layer of the Administration Tool defines the business, or logical, model of the data

and specifies the mappings between the business model and the Physical layer schemas. This layer is where the

physical schemas are simplified to form the basis for the users view of the data. The Business Model and Mapping

layer of the Administration Tool can contain one or more business model objects. A business model object contains the

business model definitions and the mappings from logical to physical tables for the business model.

The main purpose of the business model is to capture how users think about their business using their own vocabulary.

The business model simplifies the physical schema and maps the users business vocabulary to physical sources. Most

of the vocabulary translates into logical columns in the business model. Collections of logical columns form logical

tables. Each logical column (and hence each logical table) can have one or more physical objects as sources.

There are two main categories of logical tables: fact and dimension. Logical fact tables contain the measures by which

an organization gauges its business operations and performance. Logical dimension tables contain the data used to

qualify the facts.

To build the Business Model and Mapping layer of a repository, you perform the following steps:

Create a Business Model

Examine Logical JoinsExamine Logical Columns

Examine Logical Table Sources

Rename Logical Objects Manually

Rename Logical Objects Using the Rename Wizard

Delete Unnecessary Logical Objects

Create Simple Measures


Examine Logical Joins

Examine Logical Columns



Rename Objects Using the Rename Wizard




1. Right-click the white space in the Business Model and Mapping layer and select New Business Modelto open the

Business Model dialog box.


25 of 355 01/21/2015 01:53


26/354

2. Enter Sample Salesin the Name field. Leave Disabledchecked.


26 of 355 01/21/2015 01:53


27/354

3. Click OK. The Sample Sales business model is added to the Business Model and Mapping layer.


27 of 355 01/21/2015 01:53


28/354


29/354

Examine Logical Joins

1. Right-click the Sample Salesbusiness model and select Business Model Diagram > Whole Diagramto open the

Business Model Diagram.

2 . If necessary, rearrange the objects so that the join relationships are visible.

Because you dragged all tables simultaneously from the Physical layer onto the business model, the logical keys and

joins are created automatically in the business model. This is because the keys and join relationships were already

created in the Physical layer. However, you typically do not drag all physical tables simultaneously, except in very

simple models. Later in this tutorial, you learn how to manually build logical keys and joins in the Business Model andMapping layer. The process is very similar to building joins in the Physical layer.

3. Double-click any one of the joins in the diagram to open the Logical Join dialog box. In this example the join between

D1 Time and F1 Revenue is selected.


29 of 355 01/21/2015 01:53


30/354

Notice that there is no join expression. Joins in the BMM layer are logical joins. Logical joins express the cardinality

relationships between logical tables and are a requirement for a valid business model. Specifying the logical table

joins is required so that Oracle BI Server has necessary metadata to translate logical requests against the business

model into SQL queries against the physical data sources. Logical joins help Oracle BI Server understand the

relationships between the various pieces of the business model. When a query is sent to Oracle BI Server, the server

determines how to construct physical queries by examining how the logical model is structured. Examining logical

joins is an integral part of this process. The Administration Tool considers a table to be a logical fact table if it is at the

many end of all logical joins that connect it to other logical tables.

4 .Click OKto close the Logical Join dialog box.

5 . Click the Xto close the Business Model Diagram.

Examine Logical Columns

1 . Expand the D1 Timelogical table. Notice that logical columns were created automatically for each table when you


30 of 355 01/21/2015 01:53


31/354

dragged the alias tables from the Physical layer to the BMM layer.


1 . Expand the Sourcesfolder for the D1 Timelogical table. Notice there is a logical table source, D1 Time. This logical

table source maps to the D1 Time alias table in the Physical layer.


31 of 355 01/21/2015 01:53


32/354


33/354

3 . On the General tab, rename the D1 Time logical table source to LTS1 Time. Notice that the logical table to physical

table mapping is defined in the "Map to these tables" section.


33 of 355 01/21/2015 01:53


34/354

4 . On the Column Mapping tab, notice that logical column to physical column mappings are defined. If mappings are

not visible, select Show mapped columns.


34 of 355 01/21/2015 01:53


35/354


36/354


1. Expand the D1 Timelogical table.


36 of 355 01/21/2015 01:53


37/354

Rename Objects Using the Rename Wizard

1 . Select Tools > Utilities > Rename Wizard > Executeto open the Rename Wizard.

2 . In the Select Objects screen, click Business Model and Mappingin the middle pane.

3 . Expand the Sample Salesbusiness model.


37 of 355 01/21/2015 01:53


38/354

4 . Expand the D1 Timelogical table.


38 of 355 01/21/2015 01:53


39/354

5 . UseShift+click to select all of the logical columns except for the column you already renamed, Beg of Mth Wid.

6 . Click Addto add the columns to the right pane.


39 of 355 01/21/2015 01:53


40/354

7 . Repeat the steps for the three remaining logical tables so that all logical columns from the Sample Sales business

model are added to the right pane. Only the columns from F1 Revenue are shown in the screenshot.


40 of 355 01/21/2015 01:53


41/354

8 . Click Nextto move to the Select Types screen.


41 of 355 01/21/2015 01:53


42/354

Notice that Logical Columnis selected. If you had selected other object types, such as logical tables, the type would

have appeared here.

9 . Click Nextto open the Select Rules screen.


42 of 355 01/21/2015 01:53


43/354

10 . In the Select Rules screen, select All text lowercaseand click Addto add the rule to the lower pane.


43 of 355 01/21/2015 01:53


44/354

11 . Add the rule Change each occurrence of '_' into a space.


44 of 355 01/21/2015 01:53


45/354

12 . Add the rule First letter of each word capital.

13 . Click Nextto open the Finish screen. Verify that all logical columns will be named according to the rename rules you

selected.


45 of 355 01/21/2015 01:53


46/354

14 . Click Finish.

15 . In the Business Model and Mapping layer, expand the logical tables and confirm that all logical columns have beenrenamed as expected. The screenshot shows only the columns in D1 Time.

16 . In the Physical layer, expand the alias tables and confirm that all physical columns have notbeen renamed. The

point here is you can change object names in the BMM layer without impacting object names in the Physical layer.

When logical objects are renamed, the relationships between logical objects and physical objects are maintained by

the logical column to physical column mappings.


46 of 355 01/21/2015 01:53


47/354


1 . In the BMM layer, expand Sample Sales > F1 Revenue.


47 of 355 01/21/2015 01:53


48/354

2 . Use Ctrl+Click to select all F1 Revenue logical columns except for Revenueand Units.


48 of 355 01/21/2015 01:53


49/354

3 . Right-click any one of the highlighted logical columns and select Delete. Alternatively you can select Edit > Delete or

press the Delete key on your keyboard.


49 of 355 01/21/2015 01:53


50/354

4 . Click Yesto confirm the delete.

5 . Confirm that F1 Revenue contains only the Revenueand Unitscolumns.


50 of 355 01/21/2015 01:53


51/354


1 . Double-click the Revenuelogical column to open the Logical Column dialog box.

2 . Click the Aggregationtab.


51 of 355 01/21/2015 01:53


52/354

3 . Change the default aggregation rule to Sum.


52 of 355 01/21/2015 01:53


53/354


54/354

Measures are typically data that is additive, such as total dollars or total quantities. The F1 Revenue logical fact table

contains the measures in your business model. You aggregated two logical columns by summing the column data.

6 . Save the repository without checking global consistency.

Congratulations! You have successfully built a business model in the Business Model and Mapping layer of a

repository and created business measures.

Building the Presentation Layer of a Repository

You have created the initial Sample Sales business model in the repository. You now create the Presentation layer of

the repository. The Presentation layer exposes the business model objects in Oracle BI user interfaces so that users

can build analyses and dashboards to analyze their data.

To build the Presentation layer you perform the following steps:

Create a Subject Area

Create Presentation Tables

Create Presentation Columns

Rename Presentation Columns

Reorder Presentation Columns





Reorder Presentation Columns


1 . Right-click thewhite spacein the Presentation layer and select New Subject Areato open the Subject Area dialog

box.


54 of 355 01/21/2015 01:53


55/354

2 . On the General tab, enter Sample Salesas the name of the subject area.


55 of 355 01/21/2015 01:53


56/354

3 . Click OKto close the Subject Area dialog box. The Sample Sales subject area is added to the Presentation layer.


1. Right-click the Sample Salessubject area and select New Presentation Tableto open the Presentation Table

dialog box.

2. On the General tab, enter Timeas the name of the presentation table.


56 of 355 01/21/2015 01:53


57/354

3 . Click OKto close the Presentation Table dialog box. The Time presentation table is added to the Sample Sales

subject area.

4 . Repeat the process and add three more presentation tables: Products, Customers, and Base Facts.

Please note that you are using the manual method for creating Presentation layer objects. For simple models it is

also possible to drag objects from the BMM layer to the Presentation layer to create the Presentation layer objects.

When you create presentation objects by dragging from the BMM layer, the business model becomes a subject area,

the logical tables become presentation tables, and the logical columns become presentation columns. Note that all

objects within a subject area must derive from a single business model.


57 of 355 01/21/2015 01:53


58/354


1. In the BMM layer, expand theD1 Timelogical table.

2. Use Ctrl+ Clickto select the following logical columns:

Calendar Date

Per Name Half

Per Name Month

Per Name Qtr

Per Name Week

Per Name Year.


58 of 355 01/21/2015 01:53


59/354

3 . Drag the selected logical columns to the Timepresentation table in the Presentation layer.


59 of 355 01/21/2015 01:53


60/354

4 . Repeat the process and add the following logical columns to the remaining presentation tables:

Products: Drag Brand, Lob, Prod Dsc, Typefrom D2 Product.

Customers: Drag Cust Key, Namefrom D3 Customer.

Base Facts: Drag Revenue, Unitsfrom F1 Revenue.


1. In the Presentation layer, expand the Productspresentation table.


60 of 355 01/21/2015 01:53


61/354

2. Double-click the Lobpresentation column to open the Presentation Column dialog box. On the General tab notice

that "Use Logical Column Name" is selected. When you drag a logical column to a presentation table, the resulting

presentation column inherits the logical column name by default. In this example the Lob presentation column

inherits the name of the logical column "Sample Sales"."D2 Product"."Lob".

3 . Deselect Use Logical Column Name. The Name field is now editable.


61 of 355 01/21/2015 01:53


62/354

4 . Enter Line of Businessin the Name field.


62 of 355 01/21/2015 01:53


63/354

5 . Click OKto close the Presentation Column dialog box. Notice that the presentation column name is now changed to

Line of Business in the Presentation layer.

6 . In the BMM layer, expand D2 Product. Notice that the Loblogical column name is not changed. The point here isyou can change object names in the Presentation layer without impacting object names in the BMM or Physical

layers.

7 . In the BMM layer, rename the Prod Dsclogical column to Product. Notice that the name change is inherited by thecorresponding presentation column.


63 of 355 01/21/2015 01:53


64/354

8 . Make the following name changes to logical objects in the BMM layer so that the names of the corresponding

presentation columns are also changed:

For the D3 Customer logical table:

Change Cust Keyto Customer Number.

Change Nameto Customer Name.


64 of 355 01/21/2015 01:53


65/354


66/354

2. Click the Columnstab.


66 of 355 01/21/2015 01:53


67/354

3 . Select columns and use the up and down arrows, or drag the columns. to rearrange the presentation columns into

the following order from top to bottom:

Per Name Year

Per Name Half

Per Name QtrPer Name Month

Per Name Week

Calendar Date

4 . Click OKto close the Presentation Table dialog box and confirm that the presentation column order is changed in the

Presentation layer.


67 of 355 01/21/2015 01:53


68/354

5 . Repeat the steps to reorder the columns in the Productspresentation table:

Brand

Line of Business

Type

Product

6 . Save the repository without checking global consistency.

Congratulations! You have successfully built the Presentation layer of a repository.

Testing and Validating a Repository

You have finished building an initial business model and now need to test and validate the repository before continuing.

You begin by checking the repository for errors using the consistency checking option. Next you load the repository into

Oracle BI Server memory. You then test the repository by running an Oracle BI analysis and verifying the results.

Finally, you examine the query log file to observe the SQL generated by Oracle BI Server.

To test and validate a repository you perform the following steps:

Check Consistency

Disable Caching

Load the Repository

Set Up Query Logging

Create and Run and Analysis

Check the Query Log

Check Consistency

Disable Caching

Load the Repository


Create and Run an Analysis

Check the Query Log

Check Consistency

1. Select File > Check Global Consistency.


68 of 355 01/21/2015 01:53


69/354

2. You should receive the message Business model "Sample Sales" is consistent. Do you want to mark it asavailable for queries?

3 . Click Yes. You should receive the message: Consistency check didn't find any errors, warnings or best practice

violations.


69 of 355 01/21/2015 01:53


70/354

If you do not receive this message, you must fix any consistency check errors or warnings before proceeding.

4 . Click OK. Notice that the Sample Sales business model icon in the BMM layer is now green, indicating it is available

for queries.

5 . Save the repository without checking global consistency again.

6 . Select File > Close to close the repository. Leave the Administration Tool open.

Disable Caching


70 of 355 01/21/2015 01:53


71/354

1. Open a browser and enter the following URL to navigate to Fusion Middleware Control Enterprise Manager:

http://:7001/em

In this tutorial the URL is http://localhost:7001/em

2. Log in as an administrative user. Typically you use the administrative user name and password provided during the

Oracle BI installation. In this example the user name isweblogic.

3 . In the left navigation pane, expand Business Intelligenceand click coreapplication.

4 . Click the Capacity Management tab.


71 of 355 01/21/2015 01:53


72/354

5 . Click the Performancesub tab.

6 . Locate the Enable BI Server Cachesection. Cache is enabled by default.

7 . ClickLock and Edit Configuration.

8 . Click Closewhen you receive the confirmation message "Lock and Edit Configuration - Completed Successfully."


72 of 355 01/21/2015 01:53


73/354

9 . Deselect Cache enabled. Caching is typically not used during development. Disabling cache improves query

performance.

10 . Click Apply.


73 of 355 01/21/2015 01:53


74/354

11 . Click Activate Changes.

12 . Click Closewhen you receive the confirmation message Activate Changes - Completed Successfully.

13 . Do not click Restart to apply recent changesyet. You do that after uploading the repository in the next set of steps.


74 of 355 01/21/2015 01:53


75/354

Load the Repository

1. Click the Deploymenttab.

2 . Click the Repositorysub tab.


4 . Click Closewhen you receive the confirmation message "Lock and Edit Configuration - Completed Successfully."


75 of 355 01/21/2015 01:53


76/354

5 . In the "Upload BI Server Repository" section, click Browseto open the Choose file dialog box.

6 . By default, the Choose file dialog box should open to the repositorydirectory. If not, navigate to the repository

directory with the BISAMPLE repository.


76 of 355 01/21/2015 01:53


77/354

7 . Select the BISAMPLE.rpdfile and click Open.


77 of 355 01/21/2015 01:53


78/354

8 . Enter BISAMPLEas the repository password and confirm the password.

9 . Click Apply.


78 of 355 01/21/2015 01:53


79/354

10 . In the BI Server Repository section, confirm that the Default RPD is now BISAMPLE with an extension. In this

example the file name is BISAMPLE_BI0025.


79 of 355 01/21/2015 01:53


80/354



80 of 355 01/21/2015 01:53


81/354

12 . Click Closewhen you receive the confirmation message Activate Changes - Completed Successfully.

13 . Click Restart to apply recent changesto navigate to the Overviewpage (this may take a moment).


81 of 355 01/21/2015 01:53


82/354

14 . On the Overview page, click Restart.


82 of 355 01/21/2015 01:53


83/354

15 . ClickYeswhen you receive the messageAre you sure you want to restart all BI components?

16 . Allow the Restart All processing to complete. This may take a few moments.

17 . Click Closewhen you receive the confirmation message Restart All - Completed Successfully.

18 . Confirm that System Componentsare 100%and that five components are up. Leave Enterprise Manager open.


83 of 355 01/21/2015 01:53


84/354


1 . Return to the Administration Tool, which should still be open.

2 . Select File > Open > Onlineto open the repository in online mode. You use online mode to view and modify a

repository while it is loaded into the Oracle BI Server. The Oracle BI Server must be running to open a repository in

online mode.

3 . Enter BISAMPLEas the repository password and enter your user name and password.


84 of 355 01/21/2015 01:53


85/354

4 . Click Opento open the repository in online mode.

5 . Select Manage > Identityto open Security Manager.


85 of 355 01/21/2015 01:53


86/354

6 . In the left pane, select BI Repository.

7 . In the right pane, double-click your administrative user to open the User dialog box. In this example the

administrative user isweblogic.


86 of 355 01/21/2015 01:53


87/354

8 . In the User dialog box, on the User tab, set Logging level to 2.


87 of 355 01/21/2015 01:53


88/354

9 . Click OKto open the Check Out Objects dialog box.


88 of 355 01/21/2015 01:53


89/354

10 . In the Check Out Objects dialog box, click Check Out. When you are working in a repository open in online mode,

you are prompted to check out objects when you attempt to perform various operations.


89 of 355 01/21/2015 01:53


90/354

11 . Select Action > Closeto close Security Manager.


90 of 355 01/21/2015 01:53


91/354

12 . Select File > Check In Changes. Alternatively, you can click the Check In Changes icon on the toolbar.


91 of 355 01/21/2015 01:53


92/354

13 . Save the repository. There is no need to check consistency.

14 . Select File > Closeto close the repository.


92 of 355 01/21/2015 01:53


93/354

15 . Click OKwhen you receive the following message:

"In order for your online changes to take effect, you will have to manually restart each non-master Oracle BI Server

instance in the cluster."

16 . Leave the Administration Tool open.


1. Open a browser or a new browser tab and enter the following URL to navigate to Oracle Business Intelligence:


93 of 355 01/21/2015 01:53


94/354

http:///:9704/analytics

In this tutorial the URL is http://localhost:9704/analytics

2. Sign in as an administrative user. Typically you use the administrative user name and password provided during the

Oracle BI installation. In this example the user name isweblogic. If you need help identifying a user name andpassword, contact your company's Oracle BI Administrator.

3 . In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.


94 of 355 01/21/2015 01:53


95/354

4 . Select the Sample Salessubject area.

5 . In the left navigation pane, expand the folders in the Sample Sales subject area and confirm that the user interface

matches the presentation layer of the repository.


95 of 355 01/21/2015 01:53


96/354

6 . Double-click the following column names in the Subject Areas pane to add them to the analysis:

Time.Per Name Year

Products.Type

Base Facts.Revenue


96 of 355 01/21/2015 01:53


97/354

7 . Click Results.

8 . The analysis results are displayed in a compound layout, which includes a Title view and a Table view.

9 . Use the buttons at the bottom of the compound layout to view additional rows.


97 of 355 01/21/2015 01:53


98/354

Check the Query Log

1 . Return to Fusion Middleware Control Enterprise Manager, which should still be open.

2 . Click the Diagnosticstab.


98 of 355 01/21/2015 01:53


99/354

3 . Click the Log Messages sub tab.

4 . Scroll to the bottom of the window to the View / Search Log Filessection.


99 of 355 01/21/2015 01:53


100/354

5 . Click Server Logto navigate to the Log Messages screen.

6 . In the Log Messages screen, leave the data range set to Most Recent, 1 Days. Deselect all message types except

for Trace.


00 of 355 01/21/2015 01:53


101/354

7 . In the Message field, enter sending query to database.

8 . Click Search.

9 . There should be only one message at this point, but if there are more than one, select the last message in the list.

This is the most recent query sent to the database.


01 of 355 01/21/2015 01:53


102/354

10 . In the bottom pane, click the Collapse Pane button(arrow on the right side) to view the log message. Your results

should look similar to the screenshot.

11 . Click the Restore Pane button. Throughout this tutorial, you return to this view to check the query log.

12 . Leave Enterprise Manageropen.

Managing Logical Table Sources


02 of 355 01/21/2015 01:53


103/354

In this set of steps you create multiple logical table sources for the D3 Customer logical table. To create multiple logical

table sources you perform the following steps:

Open the Repository in Offline Mode

Add a New Logical Table Source

Create Presentation Layer Objects

Load the Repository


Check the Query Log




Load the Repository


Check the Query Log


1 . Return to the Administration Tool, which should still be open. If not, select Start > Programs > Oracle Business

Intelligence > BI Administration.

2 . Select File > Open > Offline.

3 . Select the BISAMPLE repository with the highest number extension. In this example it is BISAMPLE_BI0025.rpd.

Yours may be BISAMPLE_BI0001, or something similar.


03 of 355 01/21/2015 01:53


104/354


105/354

6 . Enter BISAMPLEas the repository password.

7 . Click OKto open the repository in Read Only mode.

8 . Select File > Save Asto open the Save As dialog box.


05 of 355 01/21/2015 01:53


106/354

9 . Select BISAMPLE.rpdto enter it in the File name field.


06 of 355 01/21/2015 01:53


107/354

10 . Click Save.

11 . You should receive the message: BISAMPLE.rpd already exists. Do you want to replace it?

12 . Click Yesto open the BISAMPLE repository in offline mode. This action replaces the existing BISAMPLE repository

with the BISAMPLE repository that contains the security information.


07 of 355 01/21/2015 01:53


108/354

13 . Select Manage > Identity to open Security Manager.

14 . Select BI Repository in the left pane.


08 of 355 01/21/2015 01:53


109/354

15 . Confirm that your administrative user is visible in the right pane. In this example the administrative user isweblogic.


09 of 355 01/21/2015 01:53


110/354

16 . Double-click the administrative user to open the User dialog box. On the Usertab, confirm that logging level is set to

2.


10 of 355 01/21/2015 01:53


111/354

17 . Click Cancel to close the User dialog box.

18 . Select Action > Closeto close Security Manager. The offline BISAMPLE repository now has a user with a logging

level set to 2. This will allow you to check the query log as you complete the remaining exercises in this tutorial. You

will not have to repeat the steps of saving an online repository.


1 . In the BMM layer, expand Sample Sales > D3 Customer > Sources. Notice that the D3 Customer logical table has

one logical table source named D3 Customer.


11 of 355 01/21/2015 01:53


112/354

2 . Rename the D3 Customer logical table source (not the logical table) to LTS1 Customer.


12 of 355 01/21/2015 01:53


113/354

3 . Double-click LTS1 Customer to open the Logical Table Source dialog box.

4 . Click the Column Mapping tab and notice that all logical columns map to physical columns in the same physical

table: D3 Customer. It may be necessary to scroll to the right to see the Physical Table column. Make sure "Show

mapped columns" is selected.


13 of 355 01/21/2015 01:53


114/354

5 . Click OK to close the Logical Table Source dialog box.

6 . In the Physical layer, expand orcl > BISAMPLE.


14 of 355 01/21/2015 01:53


115/354

7 . Drag D4 Addressfrom the Physical layer to the D3 Customerlogical table in the BMM layer. Notice this creates a

new logical table source named D4 Address for the D3 Customer logical table. It also creates new logical columns

that map to the D4 Address physical table.


15 of 355 01/21/2015 01:53


116/354

8 . In the BMM layer, double-click the new D4 Address logical table source to open the Logical Table Source dialog box.


16 of 355 01/21/2015 01:53


117/354

9 . On the General tab, enter LTS2 Customer Addressin the Name field.


17 of 355 01/21/2015 01:53


118/354

10 . Click the Column Mappingtab and notice that all logical columns map to physical columns in the same physical

table: D4 Address. If necessary, select Show mapped columns and deselect Show unmapped columns.


18 of 355 01/21/2015 01:53


119/354

11 . Click the red Xnext toADDRESS_KEYto delete the column. This is a duplicate column and is not needed.


19 of 355 01/21/2015 01:53


120/354


121/354

13 . Confirm that the D3 Customer logical table now has two logical table sources: LTS1 Customer and LTS2 Customer

Address. A single logical table now maps to two physical sources.


21 of 355 01/21/2015 01:53


122/354


123/354

Your results should look similar to the screenshot.


1 . In the Presentation layer, right-click the Sample Salessubject area and select New Presentation Tableto open the

Presentation Table dialog box.


23 of 355 01/21/2015 01:53


124/354


125/354

3 . Click OK to close the Presentation Table dialog box. Confirm that the Customer Regions presentation table is added

to the Sample Sales subject area in the Presentation layer.

4 . In the BMM layer, expand Sample Sales > D3 Customer.


25 of 355 01/21/2015 01:53


126/354

5 . Drag the following logical columns fromD3 Customer to Customer Regionsin the Presentation layer:

Address 1

Address 2

Area

City

Country Name

Estab Name

Postal Code

Region

State Province

State Province Abbrv


26 of 355 01/21/2015 01:53


127/354

Your column names may be slightly different depending on how you renamed them.

6 . Reorder the Customer Regions presentation columns in the following order, from top to bottom:

Region

Area

Country Name

State Province

State Province Abbrv

City

Postal Code

Address 1

Address 2


27 of 355 01/21/2015 01:53


128/354

Estab Name

7 . Double-click the Sample Sales subject area in the Presentation layer to open the Subject Area dialog box.

8 . Click the Presentation Tablestab.


28 of 355 01/21/2015 01:53


129/354


130/354

10 . Click OK to close the Subject Area dialog box. Confirm that the presentation tables appear in the expected order.

You now have two presentation tables, Customers and Customer Regions, mapped to the same logical table, D3

Customer. The D3 Customer logical table is mapped to two physical sources: D3 Customer and D4 Address.

11 . Save the repository and check global consistency when prompted. You should receive a message that there are no

errors, warnings, or best practice violations to report.

If you do receive any consistency check errors or warnings, fix them before proceeding.

12 . Click OK to close the consistency check message.

13 . Close the repository. Leave the Administration Tool open.

Load the Repository

1. Return to Fusion Middleware Control Enterprise Manager, which should still be open. If not, open a browser and

enter the following URL to navigate to Fusion Middleware Control Enterprise Manager:

http:///:7001/em



30 of 355 01/21/2015 01:53


131/354

2. If your session has timed out, you will need to log in again. Log in as an administrative user. Typically you use the

administrative user name and password provided during the Oracle BI installation. In this example the user name is

weblogic.

3 . In the left navigation pane, expand Business Intelligenceand click coreapplication.

4 . Click the Deploymenttab.



31 of 355 01/21/2015 01:53


132/354


7 . Click Closewhen you receive the confirmation message Lock and Edit Configuration - Completed Successfully.

8 . Click Browseand navigate to the directory with the BISAMPLErepository.


32 of 355 01/21/2015 01:53


133/354



11 . Click Apply.


33 of 355 01/21/2015 01:53


134/354


135/354



35 of 355 01/21/2015 01:53


136/354


137/354



37 of 355 01/21/2015 01:53


138/354


18 . Allow the processing to complete.

19 . Click Closewhen you receive the message Restart All - Completed Successfully.


1. Return to Oracle BI, which should still be open. If not, open a browser or browser tab and enter the following URL to

navigate to Oracle Business Intelligence:


In this tutorial the URL is http://localhost:9704/analytics.

2. If your previous session has timed out, sign in as an administrative user. Typically you use the administrative user

name and password provided during the Oracle BI installation. In this example the user name isweblogic.


38 of 355 01/21/2015 01:53


139/354

3 . In the left navigation pane, under Create... Analysis and Interactive Reporting, select Analysis.

4 . Select the Sample Salessubject area.


39 of 355 01/21/2015 01:53


140/354

5 . In the left navigation pane, expand the folders and confirm that the Customer Regions folder and corresponding

columns appear.

6 . Create the following analysis by double-clicking column names in the Subject Areas pane:

Customer Regions.Region

Customers.Customer Name

Products.Type

Base Facts.Revenue

7 . Click Resultsto view the analysis results. Use the buttons at the bottom of the results screen to see more rows.


40 of 355 01/21/2015 01:53


141/354

Check the Query Log

1 . Return to Fusion Middleware Control Enterprise Manager, which should still be open.

2 . Click the Diagnosticstab.


41 of 355 01/21/2015 01:53


142/354

3 . Click the Log Messages sub tab.

4 . Scroll to the bottom of the window to the View / Search Log Filessection.


42 of 355 01/21/2015 01:53


143/354

5 . Click Server Logto navigate to the Log Messages screen.

6 . In the Log Messages screen, leave the data range set to Most Recent, 1 Days. Deselect all message types except

for Trace.

7 . In the Message field, enter sending query to database.

8 . Click Search.


43 of 355 01/21/2015 01:53


144/354


145/354


Creating Calculation Measures

In this set of steps you use existing measures to created a derived calculation measure. To create a derived calculation

measure you perform the following steps:


Create a Calculation Measure Derived from Existing Columns

Create a Calculation Measure Using a Function

Load the Repository


Check the Query Log




Load the Repository


Check the Query Log


1 . Return to the Administration Tool, which should still be open. If not, select Start > Programs > Oracle Business

Intelligence > BI Administration.


3 . Select BISAMPLE.rpdand click Open. Do not select any BISAMPLE repository with an extension, for example,

BISAMPLE_BI0025.rpd. Recall that these are the repositories that have been loaded into Oracle BI Server memory.


45 of 355 01/21/2015 01:53


146/354

4 . Enter BISAMPLEas the repository password and click OKto open the repository.


1 . In the BMM layer, expand Sample Sales > F1 Revenue.


46 of 355 01/21/2015 01:53


147/354


148/354

4 . Click the Column Sourcetab.


48 of 355 01/21/2015 01:53


149/354


150/354

6 . Click the Edit Expressionbutton to open Expression Builder.


50 of 355 01/21/2015 01:53


151/354

7 . In the left pane select Logical Tables > F1 Revenue > Revenue.


51 of 355 01/21/2015 01:53


152/354

8 . Click the Insert selected itembutton to move the Revenue column to the right pane.


52 of 355 01/21/2015 01:53


153/354

9 . Click the division operatorto add it to the expression.


53 of 355 01/21/2015 01:53


154/354

10 . In the left pane select Logical Tables > F1 Revenueand then double-click Unitsto add it to the expression.


54 of 355 01/21/2015 01:53


155/354


156/354

12 . Click OKto close the Logical Column dialog box. The Actual Unit Pricecalculated measure is added to the

business model.

13 . Drag Actual Unit Pricefrom the BMM layer to the Base Facts presentation table in the Presentation layer.


56 of 355 01/21/2015 01:53


157/354

14 . Save the repository and check consistency. Fix any errors or warnings before proceeding.


1 . In the BMM layer, right-click F1 Revenue and select New Object > Logical Columnto open the Logical Column

dialog box.


57 of 355 01/21/2015 01:53


158/354

Load the Repository

1. Return to Fusion Middleware Control Enterprise Manager, which should still be open. If not, open a browser and

enter the following URL to navigate to Fusion Middleware Control Enterprise Manager:

http:///:7001/em


2. If necessary, log in as an administrative user. Typically you use the administrative user name and password provided

during the Oracle BI installation. In this example the user name is weblogic.

3 . In the left navigation pane, expand Business Intelligenceand click on coreapplication.

4 . Click the Deploymenttab.


58 of 355 01/21/2015 01:53


159/354



7 . Click Closewhen you receive the confirmation message Lock and Edit Configuration - Completed Successfully.

8 . Click Browseand navigate to the directory with the BISAMPLErepository.


59 of 355 01/21/2015 01:53


160/354




60 of 355 01/21/2015 01:53


161/354

11 . Click Apply.

12 . Confirm that the default RPD is now BISAMPLE with an extension. In this example the file name is

BISAMPLE_BI0025.


61 of 355 01/21/2015 01:53


162/354



62 of 355 01/21/2015 01:53


163/354


164/354



64 of 355 01/21/2015 01:53


165/354


18 . Allow the processing to complete.

19 . Click Closewhen you receive the message Restart All - Completed Successfully.


1. Return to Oracle BI, which should still be open. If not, open a browser or browser tab and enter the following URL to

navigate to Oracle Business Intelligence:


In this tutorial the URL is http://localhost:9704/analytics.

2. If necessary, log in as an administrative user. Typically you use the administrative user name and password provided

during the Oracle BI installation. In this example the user name is weblogic.


65 of 355 01/21/2015 01:53


166/354


167/354

8 . Click Resultsto view the analysis results.

Please note that the Actual Unit Price calculation is correct, although it does not make sense from a business

perspective. For example, the unit price for an LCD HD Television would not be 9 dollars. This is a result of the

underlying sample data.

Check the Query Log

1 . Return to Fusion Middleware Control Enterprise Manager, which should still be open, and check the query log. Ifyou need help, click hereto review steps from earlier in this tutorial.

2 . Your log entry should look similar to the screenshot.


67 of 355 01/21/2015 01:53


168/354

Note that the division of Revenue by Units is calculated in the outer query block (D1.c2 / nullif ( D1.c1, 0) as c3 in this

example). Because you defined the Actual Unit Price calculation using logical columns, the SUM aggregation rule is

applied to the Revenue and Units columns first and then the division is calculated.


Creating Logical Dimensions with Level-Based Hierarchies

In this set of steps you add logical dimension hierarchies to the business model. A logical dimension represents a

hierarchical organization of logical columns belonging to a single logical dimension table. Logical dimensions can exist

in the Business Model and Mapping layer and in the Presentation Layer. Adding logical dimensions to the Presentation

layer exposes them to users, which enables users to create hierarchy-based queries. You implement four logical

dimensions for ABC: Time, Product, Office, and Customer. Creating logical dimensions with hierarchies allows you to

build level-based measures, define aggregation rules that vary by dimension, provide drill down on charts and tables in

analyses and dashboards, and define the content of aggregate sources.To create logical dimensions with level-based

hierarchies, you perform the following steps:


Create a Logical Dimension for Product

Create Logical Levels

Associate Logical Columns with Logical Levels

Set Logical Level Keys

Create a Logical Dimension for Time

Associate Time Logical Columns with Logical Levels

Create a Logical Dimension for Customer

Set Aggregation Content for Logical Table Sources

Test Your Work


Create a Logical Dimension for Product





Associate Time Logical Columns with Logical Levels

Create a Logical Dimension for Customer

Set Aggregation Content for Logical Table Sources

Test Your Work


1 . Return to the Administration Tool, which should still be open. If not, select Start > Programs > Oracle BusinessIntelligence > BI Administration.



68 of 355 01/21/2015 01:53


169/354


170/354

3 . Click OK. The logical dimension is added to the Sample Sales business model.


1 . Right-click H2 Product and select New Object > Logical Level.

2 . Name the logical level Product Total .


70 of 355 01/21/2015 01:53


171/354

3 . Because this level represents the grand total for products, select the Grand total levelcheck box. Note that when

you do this, the Supports rollup to higher level of aggregationfield is grayed out and protected.


71 of 355 01/21/2015 01:53


172/354

4 . Click OKto close the Logical Level dialog box. The Product Totallevel is added to the H2 Product logical

dimension.

5 . Right-click Product Totaland select New Object > Child Levelto open the Logical Level dialog box.


72 of 355 01/21/2015 01:53


173/354

6 . Name the logical level Product Brand.


73 of 355 01/21/2015 01:53


174/354

7 . Click OKto close the Logical Level dialog box. The Product Brandlevel is added to the logical dimension.

8 . Repeat the steps to add the following child levels:

Product LOBas a child of Product Brand

Product Typeas a child of Product LOB


74 of 355 01/21/2015 01:53


175/354

Product Detailas a child of Product Type

Use the screenshot as a guide:


1 . Expand the D2 Product logical table.

2 . Drag the Brandcolumn from D2 Product to the Product Brand level in H2 Product.


75 of 355 01/21/2015 01:53


176/354

3 . Continue dragging logical columns from the D2 Productlogical table to their corresponding levels in the H2 Product

logical dimension:

Logical Column Logical LevelLob Product LOB

Type Product Type

Product Product Detail

Prod Key Product Detail

Your results should look similar to the screenshot:


76 of 355 01/21/2015 01:53


177/354


1 . Double-click the Product Brand logical level to open the Logical Level dialog box. On the General tab, notice that

the Product LOB child level is displayed.


77 of 355 01/21/2015 01:53


178/354

2 . Click the Keystab.


78 of 355 01/21/2015 01:53


179/354


180/354

4 . In the Columns field, use the drop down list to select D2 Product.Brand.


80 of 355 01/21/2015 01:53


181/354


182/354

6 . Set Brandas the Primary key.


82 of 355 01/21/2015 01:53


183/354

7 . Click OKto close the Logical Level dialog box. The icon changes for Brand to show that it is the key for the Product

Brand level.


83 of 355 01/21/2015 01:53


184/354


185/354

10 . The icon changes for Lob to show that it is the key for the Product LOB level.

11 . Use either method to set the remaining keys for the H2 Product logical dimension:

Logical Level Logical Level Key Use for Display

Product Type Type Yes

Product Detail Product Yes

Product Detail Prod Key No

Your results should look similar to the screenshot:


85 of 355 01/21/2015 01:53


186/354

Please note that the Detail level (lowest level of the hierarchy) must have the column that is the logical key of the

dimension table associated with it and it must be the key for that level: Prod Key in this example.

12 . Set Prod Keyas the primary key for the Product Detail level. Hint: Double-click the level and select the Keystab.


86 of 355 01/21/2015 01:53


187/354


1 . Use a different technique to create a logical dimension for Time. Right-click the D1 Tim

creating a repository using obi administration tool

Documents