1z0-591 Questions and Answers

B: Before you can run Oracle Business Intelligence 11g Installer, you must first create

required Oracle Business Intelligence schemas in an unhardened database. You use

a tool called the Repository Creation Utility (RCU) to create these schemas with

the appropriate permissions and data.

E: The database 11gR2 is required if you want to run the Oracle Business Intelligence Enterprise Edition Plus Samples

One Oracle Database Preinstalled and not hardened to host the schemas.

A single query can be performed accessing data from both tables through a join on the columns in the foreign key relation.

After creating your base metrics, try using the Calculation Wizard to automate the process of creating time-series metrics or comparison metrics such as: Change, Percent Change, Index, and Percent. The Wizard may save you many hours of time and frustration, especially if you have to create more than a handful of these metrics. In addition, the Wizard allows you to include customized logic to handle nulls in the base metrics. You may refer to the Oracle documentation for further detail.

The rank measure is numbered from 1. The highest sales amount will be ranked 1.

All others are names for level-based measure but Sales is a base measure.

Modeling Time Series Function in OBIEE

Modeling Time Series Data

Time series functions provide the ability to compare business performance with previous time periods, allowing you to analyze data that spans multiple time periods. For example, time series functions enable comparisons between current sales and sales a year ago, a month ago, and so on.

Because SQL does not provide a direct way to make time comparisons, you must model time series data in the Oracle BI repository. First, set up time dimensions based on the period table in your data warehouse. Then, you can define measures that take advantage of this time dimension to use the AGO, TODATE, and PERIODROLLING functions.

Oracle Essbase developers creating planning and budgeting applications have been keenly aware of the advantages and disadvantages of the two different storage types available to them:

* Block storage option (BSO) databases support a wide range of calculations, including forecasts, allocations, and aggregations through procedural calculation scripts. The results of these calculations can be written back to the database, but applications that use BSO storage are limited to about 10 dimensions and member counts in the low hundreds of thousands.

* Aggregate storage option (ASO) databases can support about 20 dimensions and member counts in the millions. ASO databases use multidimensional functions rather than procedural scripts to perform calculations, but the results of queries cannot be stored back in the database, making ASO unsuitable for most financial management applications.

B: Example:

1. Configure the new source table to have the 'logical level' under the content set to 'Countries' (the summarized level)

b

2. Do the similiar setting for dimension table

Now when user query the data at 'Counties' level, the query will be redirected to these summary table instead of the more detail fact table

Note: Aggregate tables are Physical tables that store Aggregates of measures across multiple levels of a Hierarchy.

Note: A level-based measure is a column whose values are always calculated to a specific level of aggregation.

The calculation of this measure is independent of the query grain and used always the aggregation grain of the logical column.

Level-based measures allow :

* to return data at multiple levels of aggregation (the query grain and the level-based column grain) with one single query

* to create share measures (percentage), that are calculated by taking some measure and dividing it by a level-based measure. For example, you can divide salesperson revenue by regional revenue to calculate the share of the regional revenue each salesperson generates.

Decrease query response time which will improve performance for Dashboards and Analysis.

With the advent of 11G, MapViewer is installed as part of Oracle BI Enterprise Edition and deployed in the same domain as Oracle BI EE on the Web application server.

Before content designers can create map views, in the Manage map Data Administration page, the metadata must be configured:

* layers (theme) and map (zoom level)

* the mapping between Oracle BI EE data and spatial data

You can control the way that the interface for Oracle BI EE is displayed to users by creating skins and styles.

While skins and styles are typically used to customize the look and feel of analyses and dashboards by providing logos, color schemes, fonts, table borders, and other elements, they can also be used to control the position and justification of various elements by including specialized style tags in the relevant style sheet (.css) file.

You can check the directory skin location with a right click on a OBIEE dashboard page, select show source code and search “custom.css”.

All metadata for cubes and dimensions is stored in the Oracle database and revealed in the data dictionary views, so that you can query the entire business model in SQL.

Note 1: OBIEE offers two calculation types for measure in the repository:

logical

physical

You can define calculations in either of the following ways:

* Before the aggregation, in the logical table source.

* After the aggregation, in a logical column derived from two other logical columns. For example: sum(col A) * sum(col B)

Note 2: A measure column is a column unlike the baseline column that has a default aggregation rule defined in the Aggregation tab of the Logical Column dialog in the repository.

Measure columns always calculate the aggregation with which they are defined.

Measures need to be defined in a logical fact. Any column with an aggregation rule is a measure.

In a Star Schema the dimensional tables does not need to be normalized.

A Snowflake Schema is a modified Star Schema that has normalized the dimensional tables.

The Oracle BI repository development process adheres to the classic Software Configuration Management (SCM)process, which utilizes a three-way merge to manage concurrent development.

The merge process involves three repositories:

The (Original|Received|Master|Parent) repository. The repository that you received before changed. You must keep it preciously unchanged.

The Modified repository. The repository that contains the customizations you made to the original repository.

The Current repository. Generally, the repository that is in production and where some customisations could have been performed by other people.

In a multiuser environment (MUDE), Developers check out the file and make changes locally. Then, these changes are automatically reconciled and merged into the master repository.

Query Limits. You can limit queries by the number of rows received, by maximum run time, and by restricting to particular time periods. You can also allow or disallow direct database requests or the Populate privilege.

See figure below.

BIEE 11g Install High level Steps :

Software Required

1. Database (Oracle, IBM DB2 or MS-SQL)

2. Repository Creation Utility (RCU)

3. OBIEE 11g (11.1.1.3 is latest OBIEE as of 30 April 2011)

4. WebLogic 10.3.3 (Optional – Only required for 64 bit machine or IBM AIX)

5. JDK 1.6 64 bit (Optional – Only required for 64 bit machine)

The Oracle BI Presentation Services Administration page provides the Manage Map Data link. This link displays the Manage Map Data page, where you can manage the logical and display versions of the data from various physical data sources. This defines the layers that content designers use when creating map views. The data that is available for managing maps and data is stored in Oracle Database as part of MapViewer.

Using this page, you provide:

* (A) Logical names to prevent any existing BI column mappings and map analyses from breaking because of changes to the physical data or to the data source.

* Display names so that the geographic data is meaningful to end users.

Note: Administering Maps Using Administration Pages

For (C) –layers, see 3-7 below.

For (D) –import images, see 11-12 below.

To administer maps using Administration pages:

Sign in to Oracle Business Intelligence.

In the global header, click Administration.

Click the Manage Map Data link to display the Manage Map Data page.

Click the Layers tab.

Click the Import Layers button to display the Import Layers dialog.

In the dialog, select the connection and the layers that are needed for zooming and drilling. (This tab is not prepopulated by other selections on the Administration pages. You can use any layers or images with any map.)

Click OK when you have finished selecting layers that are appropriate for the subject area with which you are working.

Back on the Layers tab, select a layer, then click the Edit Layer button to display the Edit Layer dialog in which you associate layers with attribute columns so that you can display BI data in the map view.

Click OK when you have finished editing the layer.

You use this tab to associate layers with BI data. If you use the City column in multiple subject areas, then you must associate it with a layer for each subject area.

Click the Background Maps tab, then click the Import Background Maps button to display the Import Background Maps dialog.

In the dialog, select the connection and the main maps to use.

The connection that you select for the main map can be different from the connection for the layers or images.

Click OK when you have finished selecting main maps.

Back on the Background Maps tab, select a map, then click the Edit Background Map button to display the Edit Background Map dialog in which you name the map and specify the order of layers and their zoom levels.

Click OK when you have finished editing the map.

Optionally, click the Images tab, then click the Import Images button to display the Import Images dialog. You can import images if you plan to use them as a format on maps.

In the dialog, select the connection and the images to use.

Click OK when you have finished selecting images.

Click Back when you have finished working with the Administration page. Your changes are saved automatically.

The Oracle Business Intelligence (BI) Administration Tool can be used to build, modify, enhance, and manage an Oracle BI repository.

C: To add a new user to a repository

1 Open a repository in the Administration Tool.

2 Display the security manager by selecting Manage > Security.

3 Select Action > New > User to open the User dialog box.

4 Type a name and password for the user.

5 If you want to log queries for this user in the query log, change the query logging level to 1 or 2.

6 Click OK.

This creates a new user with default rights granted to it.

Note: What is Oracle BI Admin Tool/Oracle Business Intelligence Administration Tool?

Oracle Business Intelligence Administration Tool is Used to manage OBIEE server

Available only for Windows operating systems.

A Windows application that allows the BI Server administrator to create & edit repositories.

Can edit repositories in either online or offline mode.

Having a session manager and a cache manager in online mode.

It is a best practice to create aliases for all tables. Aliases are created in the Physical Layer of the repository. Some of the benefits of using aliases are given below:

(A) * An alias is used to avoid circular joins and to configure self joins.

* You can create a join relationship which is different than the actual foreign key relationship in the database. This helps in defining relationships to meet business model criteria.

* Aliases can function in numerous ways to define business model e.g. a table can act both as a dimension and a fact using aliases.

(B) * You can rename aliases to make physical and business model easier to understand.

In online mode, you connect to a catalog on a running web server. In this mode your permissions are applied, you can select a locale, and you can see the effects of any localization on the catalog. You can see only those objects for which you have the appropriate permissions. Both Presentation Services and the web server must be running for you to open catalogs in online mode.

Use online mode when you want to make minor incremental changes or additions to the catalog, such as changes to permissions, updates to a single object, or migration of new objects to a production environment.

Note:

* You can open a catalog in one of two modes — online or offline. Both modes can operate against an actual production catalog, with no need for any downtime.

* Repository changes can be done in either online

or offline mode. Online mode is when BI Server

is actively reading the repository file (when a

user is logged in). Offline is when BI Server is

idle. Best practice is to develop in Offline mode.

Minor changes can be made when in online

mode.

Oracle BI Cluster Server Components

* Oracle Business Intelligence Cluster Controller: The Cluster Controller determines which BI Server works in the cluster. It monitors the operation of servers in the cluster. The Cluster Controller is deployed in active-passive mode.

* Clustered BI Servers: The BI Cluster Server feature supports up to 16 BI Servers in a network domain to act as a single server. BI Servers in the cluster share requests from multiple Oracle BI clients.

* Master BI Server: A clustered Oracle Business Intelligence Server is designated as the Master BI Server. The Oracle Business Intelligence Administration Tool connects to the master BI Server for online repository changes.

* Cluster Manager: The Cluster Manager is available in the Administration Tool when a repository is opened in online mode. The Cluster Manager enables Oracle BI Server clustered instances.

Priority group

You can set priority group numbers to determine which logical table source should be used for queries for which there is more than one logical table source that can satisfy the requested set of columns.

For example, you might have user queries that can be fulfilled by both a data warehouse and an OLTP source. Often, access to an operational system is “expensive,” while access to a data warehouse is “cheap.” In this situation, you can assign a higher priority to the data warehouse to ensure that all queries are fulfilled by the data warehouse if possible.

Note that the priority group of a given logical table source does not always ensure that a particular query will be fulfilled by that source.

Priority Group Designation

0 the highest-priority source (the default)

1 a lowest-priority source

The relationship is defined at the model and mapping layer.

Note:

At the highest level, an OBIEE Metadata Repository includes three layers of information:

1.

First, a Physical layer is defined. The metadata layer identifies the source data.

2.Second, a Business Model and Mapping layer is defined. This metadata layer organizes the physical layer into logical categories and records the appropriate metadata for access to the source data.

3.Finally, the Presentation layer is defined. This metadata layer exposes the business model entities for end-user access.