Skip Headers

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
Copyright © 2006, Oracle. All rights reserved.

Installing the Discoverer Samples

These instructions guide you through the installation of the sample workbooks for OracleBI Discoverer. When you have completed the installation process, you can use OracleBI Discoverer to analyze data from both relational and multidimensional (OLAP) data sources.

Contents

Overview

Top

The installation program installs sample workbooks and metadata used to access both OLAP and relational data.
The procedure performs the following tasks:

For relational access:

  1. Executes the Discoverer EUL Command Line for Java interface to create the user 'BI_USER' and an End User Layer (EUL). BI_USER is the user used when logging into the samples and tutorial.
  2. Grants the necessary common schema ('SH') object privileges to BI_USER allowing access to the common schema data set.
  3. Imports the bi_user.eex Discoverer EUL export file into BI_USER. The .eex file contains both the metadata and the sample relational workbooks.
  4. Refreshes summary tables used by the Discoverer tutorials.

For OLAP data access:

  1. Installs the Discoverer Catalog, if it has not already been installed.
  2. Authorizes database user SCOTT and BI_USER to access the Discoverer Catalog and the sample data set.
  3. Updates the Discoverer Catalog with sample content, including workbooks, calculations, and saved selections.

Downloading the samples

  1. Create a new directory (referred to as <SAMPLE_HOME>) on the computer where Oracle Business Intelligence middle tier is installed.
  2. Download from the Oracle Technology Network (OTN) the latest version of the samples and unzip to <SAMPLE_HOME>
  3. Change to the <SAMPLE_HOME>\samples\discoverer directory.

Installing the samples

Top

Pre-installation tasks

If you plan to user Discoverer only against relational datasources, verify that the following requirements have been met:

If you plan to user Discoverer against an OLAP datasource, verify that the following additional requirements have been met:

Performing the installation

You can install the relational and OLAP Discoverer samples separately, if you so want. This installation must be performed on the computer where the Oracle Business Intelligence middle tier is installed.

  1. Set your ORACLE_HOME environment variable to the Oracle Business Intelligence Home. For example:

    set ORACLE_HOME=c:\oracleBI
  2. Change to the <SAMPLE_HOME>\samples\discoverer directory.

Installing the relational Discoverer workbooks

  1. Run the install_rel.bat (on Unix you need to run install_rel.sh) file using the following parameters:
    1. TNSNAMES entry
    2. Password for the SYSTEM user.
    3. Default tablespace for BI_USER
    4. Temporary tablespace for BI_USER
    5. Directory where the installation script is found

      Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.

    The following line provides a sample command for running the file:
    c:\samples\discoverer> install_rel orcl system_pwd USERS TEMP c:\samples\discoverer

Installing the OLAP Discoverer workbooks

  1. You must first install the relational Discoverer samples as described above in the 'Installing the relational Discoverer workbooks' section.
  2. Run the install_olap.bat (on Unix you need to run install_olap.sh) file using the following parameters:
    1. Database machine name (e.g. bi.oracle.com)
    2. Database Port (e.g. 1521)
    3. Database SID (e.g. orcl)
    4. TNSNAMES entry
    5. Password for the SYSTEM user.
    6. Password for the D4OSYS user. This user is the owner of the Discoverer Catalog. If the Discoverer Catalog has not been installed, then the D4OSYS user will be created with the password that you entered.
    7. Directory where the installation script is found

    Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.

    The following line provides a sample command for running the file:
    c:\samples\discoverer> install_olap bi.oracle.com 1521 orcl myhost_tns system_pwd d4osys_pwd c:\samples\discoverer

Installing both relational and OLAP Discoverer workbooks

  1. Run the install_all.bat (on Unix you need to run install_all.sh) file using the following parameters:
    1. Database machine name (e.g. bi.oracle.com)
    2. Database Port (e.g. 1521)
    3. Database SID (e.g. orcl)
    4. TNSNAMES entry
    5. Password for the SYSTEM user.
    6. Password for the D4OSYS user. This user is the owner of the Discoverer Catalog. If the Discoverer Catalog has not been installed, then the D4OSYS user will be created with the password that you entered.
    7. Default tablespace for BI_USER
    8. Temporary tablespace for BI_USER
    9. Directory where the installation script is found

      Note: The host and Oracle database parameters are for the instance that will contain the Discoverer Catalog and EUL. This must be the same host machine and database that contains the common schema sample data.

    The following line provides a sample command for running the file:

    c:\samples\discoverer> install_all bi.oracle.com 1521 orcl myhost_tns system_pwd d4osys_pwd USERS TEMP c:\samples\discoverer

This page provides an overview of the sample workbooks.

Scoping Scott's view of the data

It is often a requirement to scope the set of data values that users are permitted to analyze. For this OLAP sample, Scott and BI_USER are not allowed to see the forecasted data for future time periods (such as 2002). In order to set up this type of security, the Discoverer manager must define an environment similar to the one that is described here.

The data used for the sample workbook is stored in an Oracle OLAP analytic workspace named shaw. In this workspace, a stored procedure named scope_data was defined that scopes the time periods based on the current database user ID. The scope_data stored procedure is defined as follows:

DEFINE SCOPE_DATA PROGRAM
PROGRAM
"Scopes data based on user id trap on error noprint aw attach SH_OLAP.SH_AW first
"***
"* shawt_time_isvisible specifies for each user the time periods that are visible.
"* The SCOTT user does not have access to 2002 forecast data
"***
limit shawusers to upcase(userid)

cns shawt_time
  permit read when shawt_time_isvisible

error:
  return
END

This stored procedure is called every time Discoverer Plus OLAP connects to Oracle OLAP. Discoverer Plus OLAP provides an application "hook" to allow Discoverer managers to run preprocessing tasks such as data scoping. This application hook is defined in the form of a PL/SQL procedure called d4o_autogo in the D4OSYS schema. This procedure is called by Discoverer Plus OLAP and accepts the user ID as a parameter. In this case, the d4o_autogo stored procedure attaches the sh_aw analytic workspace and calls the scope_data stored procedure. The d4o_autogo procedure is defined as follows:

CREATE OR REPLACE PROCEDURE D4OSYS.D4O_AUTOGO (user_id
  IN VARCHAR) is
  BEGIN
  dbms_aw.aw_attach('SH_OLAP', 'SH_AW');
  dbms_aw.execute('scope_data');
  END;

Uninstalling the sample

Top

To uninstall the relational sample:

  1. Connect to SQL*Plus and drop the BI_USER user by running the following command:

    SQL> DROP USER bi_user CASCADE;

To uninstall the OLAP sample:

  1. Connect to Discoverer Plus OLAP as the D4OSYS user
  2. Go to the Tools menu and select Manage Catalog
  3. Navigate to the Users directory and select the SCOTT folder. Click the Delete button.
  4. Navigate to the Shared directory and select the SCOTT folder. Click the Delete button.



Copyright © 2006 Oracle Corporation
All Rights Reserved