Post on 02-Dec-2015
Embed Size (px)
Print PreviewCreating a Repository Using the Oracle BI 11gAdministration ToolThis tutorial contains the following sections:Purpose
Time to Complete
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 Sources
Creating 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 Initialization Blocks and Variables
Creating Time Series Measures
Viewing ScreenshotsClick icon to hide all screenshotsNote:Alternatively, you can click an individual icon (or image) associated with each step to view (or hide) the screenshot associated with that step.Creating a Repository Using the Oracle BI 11gAdministration ToolPurposeThis tutorial covers using the Oracle Business Intelligence (BI) Administration Tool to build, modify, enhance, and manage an Oracle BI repository.Time to CompleteApproximately 6 hours.OverviewThis tutorial shows you how to build an Oracle BI metadata repository using the Oracle BI Administration Tool. You learn how to import metadata from 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.PrerequisitesBefore starting this tutorial, you should:1.Have access to or have Installed Oracle Business Intelligence Enterprise Edition 11g.
Please note: This tutorial is built using Oracle Business Intelligence Enterprise Edition 22.214.171.124. Due to product enhancements in 126.96.36.199, if you use an earlier version of the product to complete this tutorial, you will notice some differences in functionality:New Diagramming Capability: The Physical and Business Model Diagrams have enhanced capabilities in the 188.8.131.52 release, including an improved look-and-feel, the ability to display columns in table objects in the diagram, and new diagram options like auto-layout, marquee zoom, and zoom to fit. Additionally, joins in the Physical and Business Model Diagrams are now represented by a line with an arrow at the "one" end of the join, rather than the line with crows feet at the "many" end of the join that was used in previous releases. When creating joins in the Physical and Business Model Diagrams, you now select the "many" end of the join first, and then select the "one" end of the join. In previous releases, joins in the diagrams were created by selecting the "one" end of the join first.Whensetting up query logging, you must select Action > Set Online User Filter in Identity Manager to view users in the repository.
2.To complete this tutorial you must have access to the BISAMPLE schema that is included with the Sample Application for Oracle Business Intelligence Suite Enterprise Edition Plus. There are three options for accessing the BISAMPLE schema:1. If you already have installed version 825 or V107 of the Sample Application, verify that you have access to the BISAMPLE schema and begin the tutorial.2. If you are interested in downloading and installing the complete Sample Application, you can access ithereon the Oracle Technical Network (OTN). Please note, however, that only the BISAMPLE schema is required to complete this tutorial. If you want to install only the BISAMPLE schema, proceed to option 3.3. Clickhereto access the ForOBE.7z file, which has the 825 version of the BISAMPLE schema and installation instructions. Save ForOBE.7z, unzip, and begin with README FIRST.txt.
Building the Physical Layer of a RepositoryIn 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 11gSample 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 JoinsCreate a New Repository
1.SelectStart > Programs > Oracle Business Intelligence > BI Administrationto open the Administration Tool.
2.SelectFile > New Repository.
3.Enter a name for the repository. In this tutorial the repository name isBISAMPLE.
4.Leave the default location as is. It points to the default repository directory.
5.Leave Import Metadata set toYes.
6.Enter and retype a password for the repository. In this tutorialBISAMPLE1is the repository password.
1 .Change the Connection Type toOCI 10g/11g. The screen displays connection fields based on the connection type you selected.
2 .Enter a data source name. In this example the data source name isorcl. This name is the same as the tnsnames.ora entry for this Oracle database instance.
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.
5 .Accept the default metadata types and clickNext.
6 .In the Data source view, expand theBISAMPLEschema.
7 .UseCtrl+Clickto select the following tables:SAMP_ADDRESSES_DSAMP_CUSTOMERS_DSAMP_PRODUCTS_DSAMP_REVENUE_FSAMP_TIME_DAY_D
8 .Click theImport Selected buttonto add the tables to the Repository View.
9 .The Connection Pool dialog box appears. Accept the defaults and clickOK.
10 .The Importing message appears.
11 .When import is complete, expandBISAMPLEin the Repository View and verify that the five tables are visible.
12 .ClickFinishto open the repository.
13 .Expandorcl > BISAMPLEand confirm that the five tables are imported into the Physical layer of the repository.
1 .SelectTools > Update All Row Counts.
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.
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.
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.
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-clickSAMP_TIME_DAY_Dand selectNew Object > Aliasto open the Physical Table dialog box.
2 .EnterD1 Timein the Name field.
3 .In the Description field, enterTime Dimension Alias at day grain. Stores one record for each day.
4 .Click theColumnstab. Note that alias tables inherit all column definitions from the source table.
5 .ClickOKto close the Physical Table dialog box.
6 .Repeat the steps and create the following aliases for the remaining physical tables.
SAMP_ADDRESSES_D =D4 AddressSAMP_CUSTOMERS_D =D3 CustomerSAMP_PRODUCTS_D =D2 ProductSAMP_REVENUE_F =F1 Revenue
Create Keys and Joins
1 .Select the five alias tables in the Physical layer.
2 .Right-click one of the highlighted alias tables and selectPhysical Diagram > Selected Object(s) Onlyto open the Physical Diagram. Alternatively, you can click the Physical Diagram button on the toolbar.
3 .Rearrange the alias table objects so they are all visible.
4 .You may want to adjust the objects in the Physical Diagram. If so, use the toolbar buttons to zoom in, zoom out, fit the diagram, collapse or expand objects, select objects, and so forth:
5 .Click theNew Joinbutton on the toolbar.
6 .Click theF1 Revenuetable and then theD1 Timetable. 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.
7 .Select theD1 Time. CALENDAR_DATEcolumn, and then selectF1 Revenue.BILL_DAY_DTto join the tables. Ensure that the Expression edit box (at the bottom) contains the following expression:
"orcl".""."BISAMPLE"."D1 Time"."CALENDAR_DATE" = "orcl".""."BISAMPLE"."F1