1z0-591 Oracle Business Intelligence Foundation Suite 11g Essentials Questions and Answers

You can nest presentation folders in two ways.

1) You can enter a hyphen and a greater than sign in the description field of the table to achieve the result.

2) Or, prefix the name of the presentation folder to be nested with a hyphen and a space and place it after the folder in which it nests to achieve the same result as shown below.

Result

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

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.

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.

Denormalization is the process of intentionally backing away from normalization to improve performance by suppressing join and permitting the use of star transformation technique.

Denormalization should not be the first choice for improving performance and should only be used for fine tuning of a database for a particular application.

A: Much of the configuration of OBI that used to be done in the NQSConfig.ini files can now be done using this front end console, which in turns updates the NQSConfig.ini file. Things in the NQSConfig.ini file that are set by EM are noted in the file with '# This Configuration setting is managed by Oracle Business Intelligence Enterprise Manager'. Some things that needs to be setup manually in the NQSConfig.ini file are:

1. Usage Tracking

2. Dynamic Libraries

3. Query Optimization Flags

4. MDX Member Name Cache Section (SAP BW)

5. More specific General Settings where EM doesn't contain the level of detail required

D: Cache Management Techniques include

• Inspecting the cache reports

• Configuring the cache parameters

• Setting caching and cache persistence for tables

• Using the Cache Manager

• Inspecting SQL for cache entries

• Modifying the Cache Manager column display

• Purging the cache entries manually using the Cache Manager

• Purging the cache entries automatically

• Using event polling tables

• Seeding the cache

Security Manager – is used to setup users, groups, synchronize LDAP users and Groups, set access rights for Objects (tables, columns) and to control over when and what data a user can access.

Note: When you open the administration tool, you can reach the security manager by the Menu :

Manage > Security

NQSConfig.ini is the main configuration file of Bi Server and contains a lot of parameters.

The parameters in the Query Result Cache Section provide configuration information for Oracle BI Server caching. The query cache is enabled by default. After deciding on a strategy for flushing outdated entries, you should configure the cache storage parameters in Fusion Middleware Control and in the NQSConfig.INI file.

Initialization blocks are used to initialize dynamic repository variables, system session variables, and nonsystem session variables.

Download and installation of the client

The client install executable is available for download from the More Products menu in Oracle BI Interactive Dashboards and Oracle BI Answers.

See picture below.

OBIEE - Grain (Level of summarization)

Grain definition in the context of OBIEE.

The following list describes the different grains in navigating a query:

* Aggregation grain. The grain of the aggregate source of from a level based metrics

* Query grain. The grain of the request.

* Time Series grain. The grain at which the time series function aggregation is requested.

* Storage grain. The query in the example can be computed from daily sales or from monthly sales, or from quarterly sales.

Note:

The aggregation grain is defined in the content tab of the logical table source.

When the query grain match the aggregation grain of a logical table source, this one is used to create the physical query.

Identity Store: It is directory server to perform the authentication. It contains user name , password and groups membership information .When a user name and password combination is entered at log in, the authentication provider searches the identity store to verify the credentials provided.

See figure below.

If you want to create a dynamic time-series reference such as the value of a measure as at this time last year, or over the past three months, or year-to-date, you can use one of the OBIEE time-series functions (AGO, PERIODROLLING, TODATE) to provide an offset value for a measure.

Figure:

Note: OBIEE 11g offered a bunch of improvements that were particularly aimed at Essbase, and other OLAP server, customers; the new hierarchical columns feature brought proper OLAP analysis to OBIEE, and coupled with OLAP-oriented features such as hierarchical prompts and selection steps, made OBIEE 11g a much more conducive environment for Essbase users.

There’s much better support for Essbase-native features such as value-based hierarchies, alternate hierarchies, multiple alias tables, UDAs and other Essbase artifacts, and the value-based hierarchy feature in particular is very welcome as it can avoid the need to completely re-import your Essbase database if your outline gains additional hierarchy levels.

So coupled with the new and improved visualization capabilities in OBIEE 11g, including maps, scorecards, improved dashboard controls, the whole new UI, improved BI Publisher and so on, there’s a lot to recommend OBIEE 11g to users of the “legacy” Hyperion tools looking for a bit of a refresh of their BI environment.

B: Click Refresh All from the Oracle BI menu in PowerPoint to refresh all the refreshable objects in the presentation.

C: Right-click Table and select Insert as List from the shortcut menu. The Edit Prompts and Levels dialog box appears. Accept the default options and click Insert.

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.

Consistency check is one of the process to check whether a repository is yielding proper results in Answer reports. It checks whether;* All logical columns are mapped correctly to physical columns (B).* All logical dimension tables have a logical key.* There are at least two logical tables in the business model; one is a logical fact table, the other is logical dimension table with join condition.* There are no circular logical join relationships.* A presentation catalog exists for the business model.

Query environment can be managed by setting query limits (governors) in the Repository (RPD) for particular Application Roles. You should always set query limits for particular application roles rather than for individual users.

Steps:

1. Login to Repository using OBIEE Admin Tool

2. Navigate to Manage > Identity

3. Go to Application Role tab, choose the role and double click on it to open.

4. Click on Permissions tab

5. Set the 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.

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.

Note: The Administration tool is used to manage OBIEE server and have some capabilities to automate some repetitive tasks and principally his embedded tools.

Oracle Business Intelligence Administration Tool is available only for Windows operating systems.

The Administration Tool is a Windows application that allows the BI Server administrator to create and edit repositories.

Repositories can be edited with the administration tool in either online or offline mode.

The Administration Tool also includes a session manager and a cache manager which are available in online mode. The Cache Manager displays what queries have been cached and how frequently they have been accessed. You can also select and delete items

Horizonal Scaleout of System Components

* Used for adding additional managed servers (Java components) and

system components to an existing cluster

* Used for scalability and failover

* Set up via the Universal Installer > Scale Out BI System option

--------

In an Ibor or Agent, in the 'Destinations' tab you can set the 'Specific Devices' However, it is a Device or Delivery Profile the one used for alerts, see this OBIEE guide:

---------------x--------------

User's Guide

http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10544/toc.htm

http://download.oracle.com/docs/cd/E21764_01/bi.1111/e10544.pdf

page 218

What Are Devices and Delivery Profiles?

Devices and delivery profiles control how you will be reached when an alert is

generated by an agent and which devices receive the content:

¦ Device — A device is the medium used to deliver content to you. The content of

an agent can be delivered to a range of devices as an e-mail or SMS message.

¦ Delivery profile — A delivery profile specifies which devices to use to deliver

content to you, based on the priority of the content. You can define several

delivery profiles to meet your needs, and switch

---------------x--------------

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.

Ragged Hierarchies are hierarchies where some routes down the hierarchy are longer than others; for example, you may have an organizational hierarchy for salespeople where the overall boss has two assistant managers, one of them works on their own and another has three sales managers under them; some of those sales manager may have sales staff under them, and some sales staff may have trainees under them.

Example (see step 4 and 5 below): Getting Top-N Sales Reps for Year and Year-1

1. Under the “Business Model and Mapping” Layer, right click the “F1 Revenue” and select “New Object” -> “Logical Column…”

2. In the “Logical Column” Window give for Name: Year Ago Revenue as seen below:

3. Goto the “Column Source” Tab and select “Derived from existing columns using an expression” radio button then click on the “Edit Expression” icon.

4. Enter the following expression in the “Expression Builder” Window by selecting “Functions” in the “Category:” list, “Time Series Functions” in the “Functions:” list then “Ago” “Time Series Functions:” section.

5. Select the “<>” in the “Ago( )” function, then select “Logical Tables” in the “Category:” list, “F1 Revenue” in the “Logical Tables:” list, then double click the “Revenue” in the “Columns:” list.

Etc.

Users in Oracle BI Answers can create queries that span multiple subject areas, as long as the subject areas correspond to the same business model.

The Software Only Install type installs the Oracle Business Intelligence software binary

files in an Oracle home for later configuration as part of a Fusion Middleware

deployment.

The Essbase cube looks just like any other relational star schema in my Presentation Layer, however when it is queried Oracle BI Server will issue MDX queries against a multi-dimensional data source, rather than an SQL query against a relational star schema.

B: The Aggregate Persistence Wizard automates the creation and initial population of aggregates, persists them in a back-end database and configures the BI Server metadata layer so that they’re used when appropriate.

C: The wizard then shows me a preview of the script it’s going to generate, and asks me if I want to create any more summaries. Here’s how the preview script looks – note that it’s not SQL, it’s a script language that the BI Server understands and uses as the specification for an aggregation job, which it then turns into separate CREATE TABLE, INSERT … SELECT and so on SQL statements, “optimized” for the particular back-end database platform.

Script example:

"ag_Items"

for "Seminar - Complete"."Items"("Quantity")

at levels ("Seminar - Complete"."Customerdim"."State", "Seminar - Complete"."Productdim"."Category", "Seminar - Complete"."Timedim"."Year")

using connection pool "custdw"."CUSTDW_Pool"

in "custdw".."CUSTDW";

If security attributes conflict, a user or group is granted the least restrictive security attribute.