Practice Free 1z0-591 Oracle Business Intelligence Foundation Suite 11g Essentials Exam Questions Answers With Explanation

The value of a static repository value is initialized in the Variable dialog box. This value persists, and does not change until an Oracle BI Administrator decides to change it.

There are two types of session variables:

System — A session variable that the Oracle BI Server and Oracle BI Presentation Services use for specific purposes.

System session variables have reserved names that cannot be used for other kinds of variables (such as static or dynamic repository variables and non-system session variables).

Non-system — A system variable that the administrator creates and names. For example, the administrator might create a SalesRegion non-system variable that initializes the name of a user's sales region.

The administrator creates non-system session variables using the Oracle BI Administration Tool.

Note: Session Variables

A session variable is a variable that is initialized at login time for each user. When a user begins a session, the Oracle BI Server creates a new instance of a session variable and initializes it.

There are as many instances of a session variable as there are active sessions on the Oracle BI Server. Each instance of a session variable could be initialized to a different value.

An action link is a link to an action that you have embedded in an analysis, dashboard page, scorecard objective, scorecard initiative, or KPI that, when clicked, runs an associated action.

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

Steps for Creating Aggregate Tables in OBIEE

1. Create all Dimension Tables, Fact Tables & Hierarchies, which are required to be aggregated.

2. Go to ToolsàUtilities (from Administration tool menu bar), a dialog box will pop up with all available utilities.

3. Select Aggregate Persistence Wizard, and then click Execute Button.

4. Now Select appropriate path where you need to generate Aggregate Table SQL.

Note : Click Generate DDL file for first time generation of Aggregate Table

Click Next, to move to next page (Select Business Model & Measure Page)

In Select Business Model & Measure Page, Select Appropriate Business Model & then select associated Fact / Measure.

Etc.

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.

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.

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.

BI EE uses the ADM driver to extract the data from HFM.

Note: HFM (Hyperion Financial Management)

Example:

I EE connects to HFM through JavaHost. So, the setup for configuring the connectivity is to basically make the EPM environment variables available for access to BI EE. Before making the changes, there are a couple of things to be aware of

1. Ensure that DCOM is enabled on the BI Server machine. This is needed for HFM client to work/connect properly with HFM Server.

2. Ensure that HFM Client is installed.

The above assumes EPM 11.1.2.x version. If you are on Hyperion 9.3.3, then you need to have the ADM drivers installed manually. All of this is documented clearly. So, rather than re-iterating that i will just point to the link here. Ensure that you follow all the steps mentioned in the docs else you will have issues in the connectivity. Once all the pre-requisite steps are done, we start off with the metadata import process.

Dynamic Repository Variables:

You initialize dynamic repository variables in the same way as static variables, but the values are refreshed by data returned from queries. When defining a dynamic repository variable, you will create an initialization block or use a pre-existing one that contains a SQL query. You will also set up a schedule that the Oracle BI Server will follow to execute the query and periodically refresh the value of the variable.

Note: The value of a static repository value is initialized in the Variable dialog box. This value persists, and does not change until an Oracle BI Administrator decides to change it.

A:

* Combining Relational and OLAP Data Sources: Oracle’s Common Enterprise Information Model allows users to combine data from a relational system and an OLAP source in a single calculation. For example, a user can compare sales forecasts from an Oracle CRM System with budget data from an Oracle Essbase planning application. To clients of the Common Enterprise Information Model, the forecast and budget data appear to be from the same logical source.

* The Essbase server provides advanced multi-user read and write capabilities, including data update and multi-user recalculation. Business users with front-end tools can write data back to a server and recalculate the data on a server using calculation scripts—key functionality to support sophisticated modeling and planning applications.

* Using aggregate storage, Essbase serves a wide range of analytic needs—financial analysis, planning, budgeting, sales analysis, marketing analysis, supply-chain analysis, and profitability analytics—all from a single analytic infrastructure.

Note 2: Data model for business intelligence

The most important component of business intelligence is the concept of 'data model'. data model determinde what kind of analysis that end user could do with the data. It is also an independant concept that could span across different vendor 's product.

Unlike data model of the transaction system, the typical analytic data model is often denormalized and store extra data for analytic query and better query performance while transaction data model use is often normalized and optimized for a few data read and write, which is implemented by jointing many tables.

The most common used analytic data model in business intelligence is call the 'Star schema' data model.

With the Oracle business intelligence system, We could define star schema and dimension data model in the 'logical layer' in the admin tools. The data model in OBIEE could span different data source in physical layer, which means OBIEE have the capability of building one logical data model which is actually connect to different database in the backend

Enterprise Install: This installation type assumes some familiarity with Oracle Business

Intelligence. All software components are downloaded onto one

computer. You can accept the default configuration settings or use

your own. You use this installation type when you have an

established Oracle WebLogic domain, and you want to extend it to

the Oracle Business Intelligence application. This install option is

typically used for more advanced deployments with multiple users,

such as to scale out a deployment on additional computers.

MapViewer is shipped as part of Oracle Fusion Middleware. Its main deliverable is a J2EE application that can be deployed to a J2EE container, such as that for Oracle Fusion Middleware. MapViewer includes the following main components:

* A core rendering engine (Java library) named SDOVIS that performs cartographic rendering. A servlet is provided to expose the rendering functions to Web applications.

* A suite of application programming interfaces (APIs) that allow programmable access to MapViewer features. These APIs include XML, Java, PL/SQL, and an AJAX-based JavaScript API.

* A graphical Map builder tool that enables you to create map symbols, define spatial data rendering rules, and create and edit MapViewer objects.

* Oracle Map, which includes map cache and FOI (feature of interest) servers that facilitate the development of interactive geospatial Web applications.

Oracle Maps can be configured now in the map viewer as a built in layer.

CurrentMonth can be calculated by a sql statement.

Note:

REPOSITORY VARIABLE(DYNAMIC)

· Initialized when BI server is started

· Assigned value dynamically based on the result of a query

· Value is dependent of the sql provided in Initialization Block

Create a dynamic variable and provide a Name and Default Initializer.Create a new initialization block by clicking on the New button in the above screen.

Provide Intialization Block variable Name

Click on “Edit Data Source” button and provide the sql to be used for the variable, e.g.

select lower(sys_context('USERENV','SESSION_USER'))||

'@'||

lower(sys_context('USERENV','DB_NAME'))

from dual;

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";

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.

Security Realms are an Oracle Platform Security Services concept and bring together sets of users, groups, providers and so on for a WebLogic domain.

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

Steps to Create a Dimension Hierarchy - >Create a dimension object.Add a parent-level object.Add child-level objects.Determine number of elements.Specify level columns.Create level keys.Create a level-based measure.Create additional level-based measures.Create share measures.Create rank measures.Add measures to Presentation layer.Test share and rank measures.

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

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.

Web Catalog does contain object permissions: folder, reports, etc. The repository has objects permissions to Subject Areas, etc.

It is asking for Which task (NOT Which Tasks).

Using Administration (not Administrator) link in OBIEE you can go to 'Manage Map Data' and manage map components.

--------

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--------------

You do not use ODBC DSN to compare repositories.

Note: When an ODBC based application connects to a database, it connects to a logical name, the Data Source Name (DSN), which identifies the datasource to which it wants to connect.

Some external repository of configuration information holds the various DSN values that are available, together with the necessary configuration and control information needed by the ODBC driver to establish a connection and manage usage of the data source.

The DSN (data source name) is a data structure that contains the information about a specific data source (database, …), typically used by an ODBC driver to be able to connect to it.

The DSN contains information about the data source such as:

the name,

the directory,

and the driver.

On Windows, the DSN also specifies the ODBC driver to be used to access the database.