White Paper On Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL
A Comprehensive Study of Discoverer BI Administration Introduction and End User Layer (EUL)
Jayashree Satapathy (jsatapathy@deloitte.com) Krishna Mohan (krmohan@deloitte.com)
Deloitte Consulting India Pvt. Ltd.
CONTENTS:
1. INTRODUCTION..1 1.0. Business Intelligence.. .1 1.1. Business Intelligence Tools 1 1.2. Integrated Approach to Business Intelligence.1 1.3. Oracle Business Intelligence Discoverer...3 1.4. Oracle Business Intelligence Discoverer Components...4 1.5. Oracle Business Intelligence Discoverer Architecture....7 1.6. Metadata Administration Using Oracle Discoverer9 2. ORACLE BI DISCOVERER ADMINISTRATION..10 2.1 The new or enhanced features of BI Discoverer Administration...10 2.2 Prerequisites for using Oracle BI Discoverer Administrator...12 2.3 Discoverer BI Administration Components...12 2.4 How does Discoverer Administration Works....13 3. DISCOVERER BI ADMINISTRATOR..19 4. END USER LAYER (EUL)21 4.1 What is an End User Layer .................................................................................................... 21 4.2 Why is the End User Layer useful ....................................................................................... 21 4.3 What does the EUL contain.................................................................................................... 21 4.4 EUL Gateway 22 4.5 Privileges to create an End User Layer in an Oracle database ...22 4.6 Creation of an End User Layer ...23 4.7 Default End User Layer ...25 4.8 EUL Tables .26 4.9 Exports/Imports EUL objects .29
5. CONCLUSION .... 32 6. REFERENCE . 32
Deloitte Consulting India Pvt. Ltd. A Comprehensive Study of Discoverer BI Administration Introduction and End User Layer
ii
1. INTRODUCTION
1.0. Business Intelligence Business intelligence (BI) is a broad category of application programs and technologies for gathering, storing, analyzing, and providing access to data to help enterprise users make better business decisions. BI applications include the activities of decision support, query and reporting, online analytical processing (OLAP), statistical analysis, forecasting, and data mining. 1.1. Business Intelligence Tools Business Intelligence Tools help to gather, store, access and analyze corporate data to aid in decision-making. Generally these systems will illustrate business intelligence in the areas of customer profiling, customer support, market research, market segmentation, product profitability, statistical analysis, and inventory and distribution analysis. Benefits: Extract, transform and load data (ETL tools). Build data repositories geared to query/reporting/analysis (E.g. inquiry-only databases, stars, OLAP cubes). Document data with metadata (data about data) and user views. Query data repositories. Analyze the data in repositories. Format reports. Make reports available (portals, etc.)
1.2. Integrated Approach to Business Intelligence
Every organization has a spectrum of Business Intelligence requirements Ranging from complex MIS written operational reports, to end user based ad-hoc queries to advanced analytical tasks like forecasting and what if analysis. However, in general the insight gained from corporate data may be simplified down to three basic questions; What is the state of my business? What influenced this and what factors were involved? Based on certain trends where will my business go?
The job functions of those tasked with answering these questions has often resulted in the use of quite different reporting methods. That is, traditional structured reports for (1), Drill and pivot ad-hoc query tools for (2) and advanced analytical engines for question (3).
Oracle BI Discoverer Administration-EUL To date the use of disparate tools, often from separate vendors, has resulted in Pockets of knowledge without the ability for others to easily access the findings or to drill further into the results. A successful solution to Business Intelligence gathering should therefore allow end users to take advantage of the findings of others and to feed their own findings into an integrated solution.
Figure 1.0: Integrated business Intelligence across the enterprise
In order to make the most of the information gained from analytical tools it needs to be accessible to as wide an audience as possible. Oracle Reports facilitates the publishing of analytical data to the enterprise in two ways; By allowing for the creation of reports directly from data views created in Oracle Discoverer, Oracles award winning ad-hoc query and analysis tool for Relational databases.
Figure 1.1: Generate Operational Reports directly from Ad-Hoc Queries
The creation of Express queries directly against the Oracle Express Server, an advanced calculation engine and multi-dimensional cache for on-line analytical processing (OLAP). By the use of the Express Wizard within the Oracle Reports Developer query definition screen, users may choose from lists the dimensions and measures which have been defined within the multi-dimensional cache.
1.3. Oracle Business Intelligence Discoverer Oracle BI Discoverer is a business intelligence tool for analyzing data. It provides an integrated business intelligence solution that includes intuitive ad-hoc query, reporting, analysis, and Web-publishing functionality. Oracle BI Discoverer allows non-technical users to gain immediate access to information from multidimensional OLAP data sources, data marts, data warehouses, or online transaction processing systems. Usage: Analyze data from both relational and multidimensional data sources across the Web. Analyze data in existing worksheets and save personalized Customizations of those worksheets.
Display Discoverer worksheets as gauges, tables, crosstabs, or graphs in a dashboard-style portal. With Oracle BI Discoverer, business users at all levels of the organization have secure and immediate access to data from a variety of data sources, all through a standard Web browser.
Business Impact: Allows business knowledge experts to manage the metadata content. Handles data maintenance tasks and changes seamlessly. Provides data warehouse users with a single version of the truth.
1.4. Oracle Business Intelligence Discoverer Components Oracle Business Intelligence Discoverer includes the following components: Oracle Business Intelligence Discoverer Administration(10g) Oracle Business Intelligence Discoverer Desktop(10g) Oracle Business Intelligence Discoverer Viewer(10g)
Figure1.2: Oracle Business Intelligence Discoverer Architecture
Oracle Business Intelligence Discoverer Plus OLAP Oracle Business Intelligence Discoverer Plus Relational Oracle Business Intelligence Discoverer Portlet Provider
Description of Oracle BI Discoverer Components Below is the detailed description of BI Discoverer Components: Oracle Business Intelligence Discoverer Administration (10g) This Oracle Business Intelligence Discoverer component is a Windows- only application used by the Discoverer manager to create and maintain a business oriented view of relational data. Discoverer Administrator provides wizards and dialogs to: control access to data manage summary data administer batch scheduling
Oracle Business Intelligence Discoverer Desktop (10g) This Oracle Business Intelligence Discoverer component is a Windows-only application that enables end users to build new worksheets to analyze relational data. The worksheets that end users create in Discoverer Desktop can be used in Discoverer Plus, Discoverer Viewer, and Discoverer portals.
Oracle Business Intelligence Discoverer Plus OLAP This allows non-technical users to create reports that leverage the powerful OLAP analysis capabilities of the Oracle database. The OLAP query model works with users' own common business terms and definitions. This allows users to build complex queries in a series of steps. The flexibility of the OLAP model allows users to add new analytic calculations to their reporting environment that look, feel, and operate like stored measures and execute directly in the database. After creating a report, Oracle Business Intelligence Discoverer plus OLAP saves report definitions and calculations independent of the report, saving time in creating future reports.
Oracle Business Intelligence Discoverer Plus Relational This is a Web-based report authoring tool designed for non-technical users. It provides efficient, interactive report layout and formatting capabilities, as well as data analysis tools and built-in calculation wizards.
Discoverer plus Relational works against any relational data source, from data warehouses and data marts to online transaction processing systems. After creating reports, you can share them directly or export them as Excel, PDF, or HTML files. Oracle Business Intelligence Discoverer Viewer This allows business users to access reports and analyzes their data from a standard Web browser using a pure HTML interface, without needing to install or download additional software. With Discoverer Viewer reports can be opened .After analyzing the data; User/Developer can save the changes for future viewing, or can export the report to a variety of file formats, such as Microsoft Excel, HTML, or PDF. This can also send exported files as e-mail attachments directly from Discoverer Viewer. Oracle Business Intelligence Discoverer Portlet Provider Integration between Oracle Business Intelligence Discoverer and Oracle Application Server Portal allows creating secure and convenient dashboards to track performance measures critical to the business. The Oracle BI Discoverer Portlet Provider publishes existing Discoverer reports to an Oracle AS Portal page through a wizard-based interface, without having to write any code. Report data can be presented as a gauge, graph, table, or crosstab, depending on the report. Then these are allowed other users to view and access their data through these reports, taking advantage of Oracle Identity Management in Oracle Application Server and the fine-grained Access Control in the Oracle Database.
Users can click the analyze link to access the reports in Discoverer Viewer. The Discoverer Viewer interactive analysis environment lets users make personalized customizations to the report, tailoring information to their own needs.
1.5. Oracle Business Intelligence Discoverer Architecture The below figure shows the relationship among the components of Oracle Business Intelligence. Figure1.3: Oracle Business Intelligence Discoverer Architecture
Description of "Figure 1.2: Oracle Business Intelligence Discoverer Architecture"
Oracle Business Intelligence Discoverer has a multi-tier architecture, which takes advantage of the distributed nature of the Web environment. Oracle BI Discoverer components are installed across the following tiers:
The Discoverer client tier is the Web browser accessing Discoverer Plus (OLAP or Relational), Discoverer Viewer, or Discoverer Portlets included on an Oracle AS Portal page.
For Discoverer Plus, the only requirement for the client machine is that it runs a Java-enabled Web browser. The first time a machine is used to connect to Discoverer, the Discoverer Plus applet is downloaded from the Discoverer services tier and cached on the client machine. The applet provides the user interface and functionality for creating workbooks and analyzing data. For Discoverer Viewer and Discoverer portlets on a portal page, the only requirement for the client machine is that it runs a JavaScript-enabled Web browser.
The Discoverer services tier (also called the Discoverer middle tier) consists of Discoverer J2EE and CORBA components. The Discoverer middle tier manager controls these components using Oracle Enterprise Manager 10g Application Server Control. The services tier also stores the Discoverer Plus applet.
The Discoverer database tier contains both data and metadata that includes:
o o o o
The Discoverer workbooks used to store reports and charts. The Discoverer End User Layer (EUL) that provides an easy-to-understand view of the relational data sources. The Discoverer Catalog for access to multidimensional data sources. The data users want to analyze, such as an OLAP analytical workspace, data warehouse, or online transaction processing system.
The database tier may include more than one database.
1.6. Metadata Administration Using Oracle Discoverer
Meta Layer setup and maintenance are generally recognized as time consuming and tedious chores. Much of the tedious work associated with Meta layer setup and maintenance is performed automatically with the Oracle Discoverer Administration edition, greatly easing the burden of warehouse administration. Administration and maintenance of metadata in an Oracle Discoverer environment is performed in the End User Layer using the Administration Edition of the Discoverer tool. The End User Layer is a set of metadata control tables which are created and centrally resident in the Oracle relational database server.
This paper highlights on Introduction to Discoverer BI Administration and End User Layer (EUL) that offers a strategy for proactive use of these new features by a data administrator.
Oracle has invested a great deal of effort in developing the End User Layer into a standard for metadata management which will soon integrate the Oracle RDBMS, Oracle Financials, Manufacturing, Human Resources, and the Oracle Express OLAP product. Oracle Discoverer is also fully integrated with the Oracle application development tool suite of Oracle Developer and Designer. In particular, the Oracle Designer Case tool and Oracle Warehouse Builder ETL tool can be used to populate the End User Layer directly via the Administration Edition, greatly simplifying on-going meta-layer maintenance and consolidating the administration process.
Oracle Designer can be used to map and model the data relationships between the OLTP source system and the data warehouse. Changes in database design or definition can be performed using Designer and then quickly updated in the End User Layer through the use of Discoverers automatic synchronization feature. The administration function within Oracle Discoverer is vastly improved over previous releases of the product.
2. ORACLE BI DISCOVERER ADMINISTRATION

The current release of Oracle BI Discoverer Administration Edition has new features for better scalability and performance, apart from the UI enhancements. Exciting (and most wanted) features such as complex folder reach through and indexed items (for better query performance) have been added in the current version of Discoverer Administrator. We can also see UI enhancements to handle large number of users (better scalability) Figure 2.1: Discoverer Administration Edition
2.1.
The new or enhanced features of BI Discoverer Administration
Working with Indexed Items Defining indexed items is also very useful when you have a large facts table (such as Sales with millions of rows) and a small dimension table (such as Products containing a few rows). For example, end users may define a query to see the sales revenues for a product, where a parameter is defined on product name. Note that Sales table contains only Product_Id column, but not Product_Name column.
10
Therefore, to find rows for a specific product, Discoverer must first look in the Products table to match the product name with its product ID, and then use the product ID to return matching rows from the Sales table. This operation might be slow when the fact table that you are querying contains hundreds of thousands, or millions of rows. So defining Product Id as the indexed item for Product Name ensures that Discoverer now uses Product Id for queries based on the parameter for Product Name.
Enabling Reach Through for the Base Folders of a Complex Folder
Complex Folder Reach Through is a new feature that enables Discoverer Plus (and Discoverer Desktop) users to include items from the base folders of a complex folder, in addition to the items provided in a complex folder. (In other words, this feature helps end users extend their analysis by including additional items in the worksheets from the base folders.)
Using Discoverer Administrator, developer can enable the reach through for base folders from the Item Properties dialog box of a complex folder. When an end user selects any item from a complex folder, other items in the base folders for which reach through are enabled become available for selection.
Note that same result can be achieved by creating joins between the complex folder and its base folders.
However, this approach is undesirable because it may result in poor query performance, and we will have additional joins to maintain as a Discoverer manager. Complex folder reach through is particularly useful when using Discoverer with Oracle Applications flexfields (that is, user defined items) to query a base folder after a complex folder has been created.
If the base folder is defined as reach through enabled, then new flexfield items can be added to the base folder without having to modify the complex folder definition. UI Enhancements to Handle Large Number of Users
Discoverer Administrator has UI enhancements, and improved ability to search, select, and display selected users without having to browse through the entire list of database users. We can mention a search criterion for the list of users that we want to see using the improved Select User/Role dialog box.
11
2.2 Prerequisites for using Oracle BI Discoverer Administrator Below are the prerequisites for using Oracle BI Discoverer System prerequisites Before using Discoverer Administrator: A suitable database must be installed and available. An Oracle Enterprise Edition database will support the use of materialized views to improve the performance of summary folders.
Discoverer Administrator must have been installed on a PC, typically as part of a full Oracle Developer Suite installation. Before end users can use Discoverer, either one or both of the following must have been installed: o Discoverer Plus and/or Discoverer Viewer must have been installed on an application server machine and configured correctly as part of an Oracle Business Intelligence installation
Data access prerequisites To create and maintain a Discoverer system using Discoverer Administrator, you will require certain Discoverer privileges and database privileges: To create a EUL we must have the privileges: Discoverer Administration privilege on the EUL Allow Administration privilege on business areas we want to modify SELECT database privilege on any tables we want to add to a business area.
2.3 Discoverer BI Administration Components The fundamental components of Discoverer Administration are as below: End User Layer Business areas Folders Items Item Classes Alternative Sorts Hierarchies and drills Summary folders
12
2.4
How does Discoverer Administration Works
An administrator will initially set up Business Areas which are logical combinations of tables or views according to business function such as Personnel or Sales. Business Areas, represented in a file cabinet metaphor in Discoverer, can be populated directly from tables defined within the Oracle Designer dictionary or by loading tables from the online dictionary using the Oracle Discoverer Administration Edition.
After a Business Area is set up, the warehouse administrator will grant access to all users through the Security function and begin simplifying the process of data access for end users by clicking on the Business Area Data tab
Using the Administration Edition, tables and views which make up a Business Area, are represented using the Windows Folder metaphor. Folders can be included in more than one Business Area as they apply. Columns in a table or derived calculations are denoted as Items and may have Conditions applied to them as in any SQL query in order to restrict the rows seen by system users. Domains define categories of Items and can be used to set up list of values, alternative sort keys, and data drills.
Double clicking on an appropriate folder will bring up the Item Properties work area. Folders and there Items can be renamed in concise business terms by editing their properties. It some cases, it may be smart to hide Items so that users will not select columns that have no query value (such as a random number key) into their ad hoc reports.
List of values are created by default and are extremely helpful for a Data Administrator in evaluating the type and quality of the data resident in the warehouse. In the User Edition of the package, clicking on the + icon for an Item will give a distinct list of values which can be selected to narrow query parameters. It may be necessary, as part of the administration function, to restrict the list of values, particularly for number or date columns that typically contain too many distinct values to be useful when building queries.
Joins are created by default within a Business Area for all tables that have matching primary and foreign keys. The table schema definition must have been created using primary/foreign key constraints or matching column names in order for Discoverer to automatically recognize join criteria. Joins can be represented in composite folders by joining items from multiple folders into a single new folder.
13
Administrative creation of joins is the only method available to provide users access to more than one folder at a time. Users are prevented from joining tables on the fly in the query tool.
The hierarchy tab allows the administrator to set up item hierarchies so that users can make logical drill down queries. Date drill hierarchies are created by default but drill down relationships such as region-state must be created by the administrator using an easy drag and drop function. The Create Item Classes icon enables drill to detail to other folders besides the default folder supplied using a wizard approach. Using check boxes, drill functions can be created to drill down from summary to detail items and even perform a "hyper drill" to linked Lotus Screen Cam files, Word Documents, or Excel Spreadsheets.
It is a good idea when setting up a business area to create complex folders. Complex folders are logical groupings of columns or items from other folders that simplify the users ability to access the data.
If, for instance, a sales analysis folder contains two types of information, one related to the sale of a product and one related to distribution of the product, it might be smart to break the table into two complex folders. One folder could contain information directly related to sales revenue, profit, and sales trends while the other could contain information concerning product distribution, demographics of a sale, and buying trends within a region as it pertains to distribution points for delivery. If the complex folder is made up of two or more folders, table join conditions between all base tables must be specified. If a complex folder contains too many join conditions, it will likely be advisable to create one or more summary tables.
14
Discoverer BI Administration Implementation with a relational data source There are essentially six steps to the implementation of a Discoverer system with a relational data source, as shown in the flowchart below:
Figure 2.2: Discoverer BI Administration Implementation flowcharts (with a relational data source)
15
These six steps are described in more detail below.
2.4.1
Identifying users' requirements
For a Discoverer implementation to be successful, it must meet users' requirements. We need to find out what those requirements are and how the same can be clarified. This can be quickly seen how using Discoverer will give users both access to the information they currently use and the ability to analyze that information in new and powerful ways. In General, users' requirements typically change over time. Often the biggest changes are requested by users when a system has been rolled out. When users see what Discoverer can do for them, they soon have suggestions for other areas where it could be useful.
2.4.2
Creation of a EUL (mandatory if one does not exist already).
A EUL must exist before the creation of a business area. If a EUL does not already exist, it must be created one.
16
2.4.3
Creation of a business area and load data into it (mandatory).
Having identified users' requirements, we will have a good idea of the information that users need to access. For example, one group of users might want to access sales information, another group might want to access manufacturing information, and so on.
In Discoverer, information can be grouped with a common business purpose into a business area. Having created a business area, It must be specified which database tables and views hold that information. This can be done by 'loading' the tables and views into the business area.
2.4.4
Refining the structure of the business area so that users can view data in the most flexible and understandable way.
The default settings and contents of a business area are sufficient to enable users to access and analyze data. However, Discoverer Administrator provides a number of features to enhance the default analysis capabilities.
Specifically, the below tasks can be performed: o o o o o o o o

o
Creation of optional and mandatory conditions to restrict the number of rows returned in a folder. Creation of calculated items to provide users with ready-made computations. Creation of joins to combine folders that were not automatically joined when tables were loaded from the database Combining the folders into complex folders to completely hide joins and relational structures from users. Creation of custom folders, to represent a result set (returned by a SQL statement that is entered) as a folder with items. Editing the item names, descriptions, and other formatting information to make data easier to understand. Creation of item classes to support lists of values, alternative sorts, and drill to detail. Creation of hierarchies to simplify drilling operations. Creation of summary tables let Discoverer automate summary management, or register existing summary tables to maximize query performance.
17
2.4.5
Grant permission to be given to the business area access to users or roles (mandatory).
Having identified users' requirements, will have a good idea of which users (and groups of users) need access to which information. In some cases, different users will want access to the same information. For example, information about an employee might be required by the employee's manager, payroll staff, and users in the Human Resources department. In other cases, it is appropriate for only one group of users to have access to the information. For example, information about an engineering project is invaluable for a project manager but of no interest to payroll staff. 2.4.6 Deploying Discoverer.
Users' requirements will determine which of the Discoverer components and which version of Discoverer Administration is to be made available for the company .Also what are the Discoverer Client Versions to be available for the end users.
18
3. DISCOVERER BI ADMINISTRATOR Connectivity Details To start Discoverer Administrator: 3.1 From the Windows Start menu, we need to choose Programs | Oracle Business Intelligence Tools - <BI_TOOLS_HOME_NAME> | Discoverer Administrator to display the Connect to Oracle Business Intelligence Discoverer Administrator dialog. Figure 3.1: Discoverer BI Administrator
3.2
Before connecting to Oracle Discoverer as an Oracle Applications user, we must configure the Connect dialog to default to Oracle Applications users. Select Tools > Options to display the "Options dialog: Connection tab": Figure 3.2: Discoverer BI Administration Connection to EUL
19
3.3
To connect to Oracle BI Discoverer Administrator connection as an Oracle Applications user, we need to Select File > Connect to database to display the Connection window Figure 3.2: Discoverer BI Administrator Connectivity as an Oracle application user
3.4
After connecting to Oracle Discoverer as an Oracle Applications user, we must find a check box as shown in the fig. Figure 3.3: Username/Password for Discoverer BI Administrator Connectivity
20
4. END USER LAYER (EUL) Introduction The End User Layer (EUL) insulates Discoverer end users from the complexity and physical structure of the database. The EUL provides an intuitive, businessfocused view of the database that you can tailor to suit each Discoverer end user or user group. The EUL enables Discoverer end users to focus on business issues instead of data access issues. It helps Discoverer end users produce queries by generating SQL and provides a rich set of default settings to aid report building. The Meta layer structure of the EUL preserves the data integrity of the database. Whatever the Discoverer manager or the Discoverer end user does with Discoverer, it affects only the metadata in the EUL and not the database. The EUL is a collection of approximately 50 tables in the database. These are the only tables that can be modified through Discoverer Administrator. Business areas are defined in Discoverer Administrator using the EUL database tables. Discoverer provides read-only access to the application database. 4.1 What is an End User Layer? The End User Layer (EUL) is the metadata (i.e. data about the actual data in a database) that is simple and easy for Discoverer end users to understand. We use Discoverer Administrator to create, customize, and maintain this view for the users so they can easily access data in Discoverer. One must have access to at least one EUL in order to use Discoverer. Access is granted using the Privileges dialog. 4.2 Why is the End User Layer useful? The EUL insulates Discoverer end users from the complexity usually associated with databases. It provides an intuitive, business-focused view of the database using terms that Discoverer end users are familiar with and can easily understand. This enables Discoverer end users to focus on business issues instead of data access issues. 4.3 What does the EUL contain? The EUL contains the metadata that defines one or more business areas. A business area is a conceptual grouping of tables and/or views that apply to a user's specific data requirements. Business areas can be set up to reflect the needs of the user or group of users accessing the EUL.
21
For example, an accounting department might have an accounting business area that represents data about budgets and finance, while project leaders in an engineering department might have a business area specifically for projects requiring budget information. Although some of the columns may be the same, the exact combination of tables and views for each department may be different.
4.4 EUL Gateway The EUL Gateway provides a way for Discoverer to populate a EUL with metadata from another source, such as Oracle Designer. The EUL Gateway allows metadata defined in another tool or application to be loaded directly into the EUL.
4.5 Privileges to create an End User Layer in an Oracle database
To create an End User Layer in an Oracle database, the database user that the EUL is being created in must have the following database privileges:
CREATE CREATE CREATE CREATE CREATE
SESSION TABLE VIEW SEQUENCE PROCEDURE
The database user must also have a default tablespace. (This must not be a temporary tablespace)
4.6 Creation of an End User Layer (for an existing database user) To create a EUL for an existing database user followings steps are to be followed:
22
4.6.1 Tools | EUL Manager is to be chosen to display the EUL Manager window. Figure 4.1 EUL Manager Dialog
4.6.2 To Create a new EUL we need to click on the radio button as shown in the below figure. Figure 4.2 Create EUL Wizard Step 1 dialog
23
4.6.3 The Select an existing user radio button is to be selected.
4.6.4 The Grant access to PUBLIC check box is to be Selected or cleared as required:
This check box is to be selected to enable all users in the current database to access the new EUL This check box is to be cleared to enable only the EUL owner to view data through the new EUL.
4.6.5 The New EUL is for use by Oracle Applications users ONLY check box is to be selected or cleared as required:
This check box is to be selected to restrict the new EUL to Oracle Applications users only. This check box is to be cleared to create a standard EUL A standard EUL cannot be changed into an Oracle Applications EUL (and vice versa). 4.6.6 The Select button is to be clicked to display the where we search for, and the database user is selected to own the new EUL.
4.6.7 If it is specified a database user other than the current user to be the EUL owner, then it is needed to specify the database user's password.
4.6.8 Finish button is to be clicked.
Discoverer Administrator displays the Creating EUL progress bar and creates a new EUL for the specified database user.
When the new EUL has been created, Discoverer gives the option to install the Discoverer sample data in the new EUL.
24
4.7 Default End User Layer It can be viewed or changed which EUL is the default. Figure 4.3 Retrieving list of available EUL
EUL for the current database user (i.e. the EUL used when the current database user connects to Discoverer Administrator).
25
Figure 4.4 Default EUL (for example: EUL4_US)
4.8 EUL Tables
The EUL Manager dialog enables you to create or delete the set of tables that make up a EUL. When a Discoverer manager defines folders and items in a business area using Discoverer Administrator, Discoverer generates the appropriate SQL statements (that define the selections from a table, view, or column) and stores them in the EUL tables. When a Discoverer end user executes a query (in Discoverer Plus or Discoverer Viewer), Discoverer generates the corresponding SQL statement and sends it to the database, which in turn returns the results to display in Discoverer.
The Discoverer end user does not have to understand any SQL to access, analyze, and retrieve data. It is all handled by Discoverer.
26
A EUL's tables / views are found in the schema by the same name as the EUL. So, if EUL is called: EUL_US (like 94.85678% of them are!), then all the EUL meta-data tables / views are found in the EUL_US schema.
The views that are in the Apps schema are not EUL tables / views always, but Oracle Apps BIS views that can be imported the definition into EUL. So, for example, if an Apps EUL is not used but a standard EUL, there are no BIS views.
Finally, the EUL that is used as default is the one that's identified in the Tools section of plus / desktop / Admin / Viewer program.
(Table 4.1: Some of the EUL tables and its description) EUL TABLES EUL4_BAS EUL4_OBJS EUL4_KEY_CONS DESCRIPTION Table gives list of Business Areas Table gives all folders in the EUL Table gives all Folder Joins details. Key_Obj_ID points to parent folder, FK_Obj_ID_Remote points to child folder Table gives all Items that are in the EUL where IT_Obj_ID is not null AND join to a row in EUL4_Objs you have a Folder Item. They are listed as Exp_Type of 'CO' or 'CI'. COs are database object items. CIs are created items (like date hierarchy items, complex folder items, etc). Table gives details about the types of objects Obj_Type tells you Standard (SOBJ) from Complex (COBJ) folders. Table gives user details. Table to use to get the list of Disco users that was granted access to the User Edition. Basically, when a user has been granted privileges one row per privilege is inserted into this table. The column called AP_EU_ID contains the ID of the user. The column GP_APP_ID is the one that tells you what privilege a user has.
EUL4_EXPRESSIONS
EUL4_OBJS EUL_USERS
EUL4_ACCESS_PRIVS
27
Discoverer versions and EUL versions The different upgrade paths are shown in the flowchart below: Figure 4.5 Discoverer upgrade flowchart
Specific versions of Discoverer are compatible with particular EUL versions.Discoverer end users will be unable to connect to a EUL that is not compatible with the version of the Discoverer product that they are using. (Table 4.2: Discoverer and EUL Version Numbers) Discoverer Release/Version Number Release 3.1.x/3.3.x Release 4.1.x Version 9.0.2.52 and earlier Version 9.0.2.53 and later Version 9.0.4.x Version 10.1.2.x EUL Version Number Release 3.1.x Release 4.1.x Version 5.0.0.x Version 5.0.2.x Version 5.0.2.x Version 5.1.x.x
Discoverer version numbers and EUL version numbers are not totally synchronized, as shown above.
The two systems (i.e. 4i and 10g) do not share a common EUL prefixing system. Discoverer 4i uses EUL4x while Discoverer 10g uses EUL5x. Therefore, while upgrading from 4i to 10g using the same schema you will still be able to use your 4i installation after the upgrade. It is required to consider installing 10g into a separate schema, using Discoverer's export import mechanism to affect the EUL upgrade.
28
4.9 Exports/Imports EUL objects EUL objects can be exported (e.g. business areas, workbooks, folders, items) from one database and imported into another database. For example, we might want to move EUL objects when transitioning from a development environment to a production environment.
Copying EULs and EUL objects by exporting and importing Typically, the following tasks are carried out:
backup or archive EULs distribute EULs to other locations copy business areas between EULs copy EUL objects (e.g. business areas, folders, hierarchies, calculations) from one EUL to another apply patches to a production environment
There are a number of different ways to copy EULs and EUL objects, depending on the requirement:
copy specified EUL objects into another EUL copy an entire EUL and recreate it as a new EUL copy the database user that is the EUL owner
We can import and export EULs and EUL objects in the following ways: Using the Discoverer Export Wizard and Import Wizard Using the Discoverer command line interface
Using the standard database export/import commands, this option is used to export an entire EUL to a file when one needs to copy objects from the EUL into a new EUL or to create a backup.
29
Oracle BI Discoverer Administration-EUL To export the entire EUL using the Discoverer Export Wizard: 4.9.1 Choose File | Export to display the "Export Wizard Step 1 dialog". Figure 4.5 Export Wizard: Step 1 dialog
4.9.2 Select the entire End User Layer radio button and click Next to display the next wizard. Figure 4.6 Export Wizards: Step 2 dialog
30
The above dialog is used to specify a name and location for the export file. 4.9.3 Click Browse to display the Save As dialog. This enables us to browse for a location to save the EUL export file. 4.9.4 Enter a suitable name for the exported EUL. 4.9.5 Select the Generate XML for exported workbooks check box to save any workbook definitions in XML format. (optional) This enables us to view workbook definitions in an XML browser. The export file (*.eex) is always in XML format but workbooks by default are saved inside it as a binary to save space and time. The check box is selected to save the workbook definitions additionally as XML inside the export file.
4.9.6 Select the Save export commands to a text file (*.txt) check box to save the export commands that created this export to a text file. (Optional). This creates an additional file containing the commands used to create this export and applies the file extension .txt. 4.9.7 Click Finish to create the export file (and any additional files selected) in the specified location and display the Export Log. Figure 4.7 Export Log dialog
31
The Export Log displays information about what has been exported. 4.9.8 Click Save to specify a name and location to save the Log file. (Optional) 4.9.9 Click Close to finish. If Discoverer Administrator is used to export EULs or EUL objects, a Discoverer EUL export file is created (with an .EEX suffix). Having created an .EEX file, Discoverer Administrator (another instance) can be used to import the .EEX file.
5. Conclusion
Always Discoverer Administrator is started in the default EUL. Default EUL is the one specified on the "Options dialog: Connection tab". If we want to change the EUL we are working in, we must change our default EUL and then reconnect to Discoverer Administrator When we use Discoverer Administrator, we should make sure that no more than one current connection exists against a particular EUL. When there is a single connection against a EUL, to avoid the risk of unknowingly making conflicting changes to EUL objects. To improve performance, Discoverer stores statistics about end user queries in the EUL. For this reason, Discoverer requires that the database containing the EUL is writeable. Specifically, Discoverer does not support the creation of EULs in Logical Standby (or read-only) databases. To prevent Discoverer end users having write access to: Business data store the data in a read-only database and use database links to access the data from the writeable database that contains the EUL. The EUL itself, do not grant the Create/Edit Workbook privilege to any users, and only grant the Administration privilege to the EUL owner
6. References http://www.otn.oracle.com http://www.oracle.com/ http://download-west.oracle.com/docs/html/B13916_04 http://www-db.stanford.edu/~hgupta/ps/dawn.ps http://www-db.stanford.edu/warehousing/index.html
32

White Paper On Oracle BI Discoverer Administration-EUL

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

White Paper On Oracle BI Discoverer Administration-EUL

Încărcat de

Drepturi de autor:

Formate disponibile

Oracle BI Discoverer Administration-EUL

Jayashree Satapathy (jsatapathy@deloitte.com) Krishna Mohan (krmohan@deloitte.com)

Deloitte Consulting India Pvt. Ltd.

Oracle BI Discoverer Administration-EUL

5. CONCLUSION .... 32 6. REFERENCE . 32

Oracle BI Discoverer Administration-EUL

1.2. Integrated Approach to Business Intelligence

Figure 1.0: Integrated business Intelligence across the enterprise

Oracle BI Discoverer Administration-EUL

Figure 1.1: Generate Operational Reports directly from Ad-Hoc Queries

Oracle BI Discoverer Administration-EUL

Figure1.2: Oracle Business Intelligence Discoverer Architecture

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Description of "Figure 1.2: Oracle Business Intelligence Discoverer Architecture"

The database tier may include more than one database.

Oracle BI Discoverer Administration-EUL

1.6. Metadata Administration Using Oracle Discoverer

Oracle BI Discoverer Administration-EUL

2. ORACLE BI DISCOVERER ADMINISTRATION

The new or enhanced features of BI Discoverer Administration

Oracle BI Discoverer Administration-EUL

Enabling Reach Through for the Base Folders of a Complex Folder

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

How does Discoverer Administration Works

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

These six steps are described in more detail below.

Identifying users' requirements

Creation of a EUL (mandatory if one does not exist already).

Oracle BI Discoverer Administration-EUL

Creation of a business area and load data into it (mandatory).

Specifically, the below tasks can be performed: o o o o o o o o

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

4.5 Privileges to create an End User Layer in an Oracle database

CREATE CREATE CREATE CREATE CREATE

SESSION TABLE VIEW SEQUENCE PROCEDURE

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

4.6.3 The Select an existing user radio button is to be selected.

4.6.8 Finish button is to be clicked.

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Figure 4.4 Default EUL (for example: EUL4_US)

4.8 EUL Tables

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

Oracle BI Discoverer Administration-EUL

6. References http://www.otn.oracle.com http://www.oracle.com/ http://download-west.oracle.com/docs/html/B13916_04 http://www-db.stanford.edu/~hgupta/ps/dawn.ps http://www-db.stanford.edu/warehousing/index.html

S-ar putea să vă placă și