A1-Administration-Tool培训资料.doc

A1-Administration Tool

精品文档
Creating a Repository Using the Oracle Business Intelligence Administration Tool
Purpose
This tutorial covers using the Oracle Business Intelligence (BI) Administration Tool to build, modify, enhance, and manage an Oracle BI repository.
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.
Building the Physical Layer of a Repository
Create a New Repository

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

2.
Select File > New Repository.

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

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 BISAMPLE is the repository password.

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.

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.

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.

4 .
Click Next.

5 .
Accept the default metadata types and click Next.

6 .
In the Data source view, expand the BISAMPLE schema.

7 .
Use Ctrl+Click to select the following tables:
SAMP_ADDRESSES_D
SAMP_CUSTOMERS_D 
SAMP_PRODUCTS_D
SAMP_REVENUE_F
SAMP_TIME_DAY_D

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

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

10 .
The Importing message appears.

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

12 .
Click Finish to open the repository.

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

Verify Connection

1 .
Select Tools > 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 select View Data to 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.

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.

2 .
Enter D1 Time in the Name field.

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

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

5 .
Click OK to close the Physical Table dialog box.

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

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) Only to 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. 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.

4 .
Click the New Foreign Key button on the toolbar.

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.

6 .
Select the D1 Time. CALENDAR_DATE column, and then select F1 Revenue.BILL_DAY_DT to 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 Revenue"."BILL_DAY_DT"

7 .
Click OK to close the Physical Foreign Key dialog box. The join is visible in the Physical Diagram.

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"

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.
In the next topic you learn how to build the Business Model and Mapping layer of a repository.

Building the Business Model and Mapping Layer of a Repository
Create a Business Model

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

2.
Enter Sample Sales in the Name field. Leave Disabled checked.

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

4.
In the Physical layer, select the following four alias tables:
D1 Time
D2 Product
D3 Customer
F1 Revenue

Do not select D4 Address at this time.

5 .
Drag the four alias table from the Physical layer to the Sample Sales business model in the Business Model and Mapping layer. The tables are added to the Sample Sales business model. Notice that the three dimension tables have the same icon, whereas the F1 Revenue table has an icon with a # sign, indicating it is a fact table.

Examine Logical Joins

1.
Right-click the Sample Sales business model and select Business Model Diagram > Whole Diagram to 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 and Mapping 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.

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 OK to close the Logical Join dialog box.

5 .
Click the X to close the Business Model Diagram.

Examine Logical Columns

1 .
Expand the D1 Time logical table. Notice that logical columns were created automatically for each table when you dragged the alias tables from the Physical layer to the BMM layer.

Examine Logical Table Sources

1 .
Expand the Sources folder for the D1 Time logical 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.

2 .
Double-click the D1 Time logical table source (not the logical table) to open the Logical Table Source dialog box.

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.

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.

5 .
You learn more about the Content and Parent-Child Settings tabs later in this tutorial when you build logical dimension hierarchies. Click OK to close the Logical Table Source dialog box. If desired, explore logical table sources for the remaining logical tables.

Rename Logical Objects Manually
1.
Expand the D1 Time logical table.

2.
Click on the first logical column, BEG_OF_MONTH_WID, to highlight it.

3.
Click on BEG_OF_MONTH_WID again to make it editable.

4 .
Rename BEG_OF_MONTH_WID to Beg of Mth Wid. This is the manual method for renaming objects. You can also right-click an object and select Rename to manually rename an object.

Delete Unnecessary Logical Objects
1 .
In the BMM layer, expand Sample Sales > F1 Revenue.

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

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.

4 .
Click Yes to confirm the delete.

5 .
Confirm that F1 Revenue contains only the Revenue and Units columns.

Create Simple Measures
1 .
Double-click the Revenue logical column to open the Logical Column dialog box.

2 .
Click the Aggregation tab.

3 .
Change the default aggregation rule to Sum.

4 .
Click OK to close the Logical Column dialog box. Notice that the icon has changed for the Revenue logical column indicating that an aggregation rule has been applied.

5 .
Repeat the steps to define the SUM aggregation rule for the Units logical column.

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.

Creating Calculation Measures
Create a Calculation Measure Derived from Existing Columns
1 .
In the BMM layer, expand Sample Sales > F1 Revenue.

2 .
Right-click F1 Revenue and select New Object > Logical Column to open the Logical Column dialog box.

3 .
On the General tab, enter Actual Unit Price in the Name field.

4 .
Click the Column Source tab.

5 .
Select Derived from existing columns using an expression.

6 .
Click the Edit Expression button to open Expression Builder.

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

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

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

10 .
In the left pane select Logical Tables > F1 Revenue and then double-click Units to add it to the expression.

11 .
Click OK to close Expression Builder. Notice that the formula is added to the Logical Column dialog box.

12 .
Click OK to close the Logical Column dialog box. The Actual Unit Price calculated measure is added to the business model.

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

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

Create a Calculation Measure Using a Function
1 .
In the BMM layer, right-click F1 Revenue and select New Object > Logical Column to open the Logical Column dialog box.

2 .
On the General tab, enter Revenue Rank in the Name field.

3 .
Click the Column Source tab.

4 .
Select Derived from existing columns using an expression.

5 .
Click the Edit Expression button to open Expression Builder.

6 .
In the left pane select Functions > Display functions > Rank .

7 .
Click the Insert selected item button to move the Rank function to the right pane.

8 .
Click <<numExpr>> in the expression.

9 .
In the left pane select Logical Tables > F1 Revenue and then double-click Revenue to add it to the expression.

10 .
Click OK to close Expression Builder. Notice that the formula is added to the Logical Column dialog box.

11 .
Click OK to close the Logical Column dialog box. The Revenue Rank calculated measure is added to the