Skip Headers
Oracle® Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer
11g Release 1 (11.1.1)

Part Number B40107-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

5 Configuring Discoverer Plus OLAP

This chapter describes how to configure the Discoverer Catalog and Discoverer Plus OLAP, and includes the following topics:

For information on Discoverer Plus OLAP, see the following documentation:

5.1 Overview of the Discoverer Catalog

Discoverer Plus OLAP is installed automatically when you install Discoverer Plus. Discoverer Plus OLAP depends on the Discoverer Catalog to store the objects that users need for analyzing data. The Discoverer Catalog is not installed automatically. Instead, you use Fusion Middleware Control to install and manage the Discoverer Catalog.

Note: You need the Discoverer Catalog, only if you intend to use Discoverer Plus OLAP.

Tip: When end users run Discoverer Plus Relational, they use the EUL, which is described elsewhere in this guide. When they run Discoverer Plus OLAP, they do not use the EUL; rather, they use the Discoverer Catalog.

5.1.1 What is the Discoverer Catalog?

The Discoverer Catalog is a repository for storing and retrieving definitions of objects for Discoverer Plus OLAP. There is one Discoverer Catalog per database. The Discoverer Catalog can also be used by applications that are built with Oracle Business Intelligence Beans (BI Beans). With Discoverer Plus OLAP, end users store in the Discoverer Catalog objects such as workbooks, calculations, and saved selections and share objects with others who have access to the Discoverer Catalog. In a BI Beans application, a user can create a graph and store it in the Discoverer Catalog. If another user has appropriate access, that user can retrieve the graph that was stored in the Discoverer Catalog and insert the graph into a new worksheet in Discoverer Plus OLAP. Oracle Business Intelligence creates a new user on the Oracle Business Intelligence middle tier installation called D4OSYS to hold the Discoverer Catalog.

The Discoverer Catalog provides security at the object level, by allowing users and system administrators to specify privileges for certain objects. The objects are saved in the Oracle database in XML format.

Note: Do not confuse the Discoverer Catalog, which contains object definitions, with the OLAP Catalog.

5.1.2 What is the OLAP Catalog?

The OLAP Catalog defines logical multidimensional objects that can be mapped either to columns in the tables of a star or snowflake schema or to multidimensional objects in an analytic workspace. Each database instance contains only one OLAP Catalog.

An analytic workspace stores multidimensional data objects and procedures that are written in the OLAP DML. The OLAP DML is a data manipulation language that is understood by the Oracle OLAP calculation engine. The OLAP DML extends the analytic capabilities of querying languages such as SQL and the OLAP API to include forecasting, modeling, and what-if scenarios.

For more information, see Oracle OLAP Reference.

5.1.3 What properties can objects in the Discoverer Catalog have?

The objects in the Discoverer Catalog contain numerous properties. The Name, Description, and Keywords properties can be modified by end users. The Created On, Created By, Modified On, Modified By, and Type properties cannot be modified by users. The values of these properties are assigned by Discoverer Plus OLAP.

5.1.4 What is the architecture of the Discoverer Catalog?

The Discoverer Catalog exists in the Oracle database, along with the OLAP Catalog and the EUL schema. The following list describes how Discoverer Plus Relational and Discoverer Plus OLAP access these pieces:

  • Discoverer Plus Relational accesses data and workbooks from the EUL. The database contains multiple EULs, business areas, and folders.

  • Discoverer Plus OLAP accesses data from the OLAP Catalog and accesses workbooks and related objects from the Discoverer Catalog. The OLAP Catalog contains the Measures folder and cubes of OLAP data. The D4OSYS schema holds the Discoverer Catalog and its objects (workbooks, calculations, saved selections, and so on).

Figure 5-1 provides a visual representation of this architecture.

Figure 5-1 Discoverer Catalog architecture

Description of Figure 5-1 follows
Description of "Figure 5-1 Discoverer Catalog architecture"

5.1.5 Differences between the Discoverer Catalog and the BI Beans Catalog

The objects in the Discoverer Catalog can be used by BI Beans applications. However, the Discoverer Catalog does differ from the BI Beans Catalog, as described in the following list:

  • The BI Beans Catalog stores many kinds of objects. The Discoverer Catalog stores only folders, workbooks, saved selections, calculations, shortcuts, user preferences, and formats.

  • You can have only one Discoverer Catalog per database instance, but you can have multiple BI Beans Catalogs per database instance. The Discoverer Catalog resides in its own schema called D4OSYS. The objects in the Discoverer Catalog refer only to OLAP metadata objects in the same database instance.

  • The BI Beans Catalog stores user and role information in itself. The Discoverer Catalog obtains user and role information from the database. The database users and roles must be authorized to use the Discoverer Catalog through the assignment of the D4OPUB role.

  • The BI Beans Catalog does not provide user management, so application developers must manage users themselves. The Discoverer Catalog provides powerful user management features.

  • BI Beans offers the use of a remote Catalog and a local, or file-based, Catalog. The Discoverer Catalog functions the same as a BI Beans remote Catalog. Searching of the Discoverer Catalog is not exposed in Discoverer Plus OLAP in the current release but is available in Discoverer Viewer.

See the BI Beans Help system for complete information on the BI Beans Catalog.

5.2 Maintaining the Discoverer Catalog

You can use Fusion Middleware Control or the Discoverer Plus OLAP command line utility to maintain the Discoverer Catalog.

You perform tasks such as installing, uninstalling, exporting, and importing the Discoverer Catalog and maintaining authorized users and roles. In Fusion Middleware Control or the Discoverer Plus OLAP command line utility, you do not create, delete, rename, copy, or move objects or folders for the Discoverer Catalog. Users perform these tasks in Discoverer Plus OLAP. Users also do not perform these tasks in Viewer; there, users simply save objects to the Discoverer Catalog.

5.2.1 Database privileges assigned to the D4OSYS user

When you install the Discoverer Catalog, you log in as a DBA user and you create the D4OSYS user, who has the following characteristics:

  • Is the administrator of the Discoverer Catalog.

  • Has the following roles: OLAP_DBA, RESOURCE, and CONNECT.

  • Authorizes Discoverer Catalog users and assigns roles to users.

  • Has Full Control privileges on all folders and objects in the Discoverer Catalog.

5.2.2 Installing a Discoverer Catalog

When you install a Discoverer Catalog, a D4OSYS user is created automatically; the D4OSYS schema is populated with the schema objects required for workbooks, worksheets, and other objects in Discoverer Plus OLAP.

Note:

If you are using Oracle OLAP 11g, you must certify Discoverer Plus OLAP with the 11g database instance as decribed in Section 5.2.2.2, "Certifying Discoverer Plus OLAP with Oracle Database 11g Release 2 (11.2)".

When you log in to install the Discoverer Catalog, you are prompted to create the password for the D4OSYS user. You are the only person who knows the password, so store it in a secure location.

To install the Discoverer Catalog:

  1. Use the database management tools in Fusion Middleware Control to create a tablespace into which you will install the Discoverer Catalog.

    Ensure that the tablespace has the appropriate block size, as described in Section 5.2.2.1, "Checking the block size when installing the Discoverer Catalog."

  2. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  3. From the Discoverer menu, select Catalog, and then select Install.

    The Install Catalog page is displayed.

  4. Enter the host name, port number, and SID of the database in which you want to install the Catalog.

    Note:

    You can specify the complete JDBC connect string in the Host field, in the following format:

    jdbc:oracle:thin:@HOST:PORT:SID
    

    If you specify the complete JDBC connect string in the Host field, then leave the Port and SID fields blank.

  5. Enter the DBA user name of "system" and the appropriate password.

    Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or higher).

  6. Click Continue.

    If a Discoverer Catalog already exists in the specified database, a warning message is displayed indicating that if you proceed with the installation process, the existing Catalog will be overwritten.

  7. Click Yes to proceed.

    The Install Catalog: D4OSYS Details page is displayed.

  8. Enter the password that you want to use for the D4OSYS user. In the Tablespace field, select the tablespace into which you want to install the Discoverer Catalog. You created this tablespace in step 1.

  9. Click Finish.

    A window is displayed prompting you to confirm whether you want to install the Discoverer Catalog.

  10. Click Yes to complete the installation process.

Note:

Alternatively, you can install the Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog."

5.2.2.1 Checking the block size when installing the Discoverer Catalog

An analytic workspace has a recommended 8-KB block size; so you might want to use that specification for the block size of the tablespace into which you install the Discoverer Catalog. Depending on requirements such as the character set in use, however, the block size may need to be changed.

When creating a custom tablespace with an 8-KB block size, specify 8192 as the block size value.

If the block size is not large enough, you might see an error message such as the following one when you try to install the Discoverer Catalog:

oracle.dss.d4o.administration.D4OInstallationException: D4O-1125 Post-install verification failed, not all Discoverer Catalog objects are installed. Expected xx, found yy.

xx represents the number of objects expected.

yy represents the number of objects found.

This error message indicates that, during the creation of the Discoverer Catalog, an attempt was made to create an index using a key size that is larger than the maximum allowed value. The index key size is limited by the value of the block size for the database or for the tablespace, because a key value cannot span multiple blocks.

Tip: Ask your database administrator for information about the block sizes of tablespaces and of the database.

5.2.2.2 Certifying Discoverer Plus OLAP with Oracle Database 11g Release 2 (11.2)

To certify a Discoverer Plus OLAP installation with Oracle Database 11.2, perform the following steps:

  1. After installing Oracle Database 11.2, download and install the latest Oracle OLAP patches from My Oracle Support.

    Note:

    To download patches, log in to My Oracle Support and select Patches & Updates.

  2. To connect an OLAP 10.2 analytic workspace to a Oracle Database 11.2 instance, set either of the following modes:

    • SupportMTM = FALSE, MetadataReaderMode = DEFAULT

      Run the following script:

      alter system set "_xsolapi_support_mtm" = FALSE scope=spfile;
      alter system set "_xsolapi_metadata_reader_mode"="DEFAULT"
      

      In this mode, you can either connect to OLAP 10g or OLAP 11g analytic workspaces, but you should apply the naming rules for the OLAP 11g objects to avoid naming conflicts. To connect to OLAP 10g analytic workspaces in this mode, you should run the INITIALIZE_CUBE_UPGRADE PL/SQL procedure for the schema. This procedure generates a table that maps old OLAP 10.2 objects to the corresponding OLAP 11.2 object names. The OLAP API uses this mapping to enable OLAP 10.2 analytic workspaces to work with the OLAP 11.2 metadata reader logic. For more information about executing the INITIALIZE_CUBE_UPGRADE PL/SQL procedure, see Oracle Database PL/SQL Packages and Types Reference.

    • SupportMTM = TRUE, MetadataReaderMode = 10_ONLY

      Run the following script:

      alter system set "_xsolapi_support_mtm" = TRUE scope=spfile;
      alter system set "_xsolapi_metadata_reader_mode"="10_ONLY"
      

      In this mode, you can connect only to OLAP 10g analytic workspaces. The 11g naming rules need not be applied here.

5.2.3 Uninstalling a Discoverer Catalog

When you uninstall a Discoverer Catalog, the D4OSYS user and the D4OPUB role are removed from the database. As a result, all workbooks, saved selections, and other objects that were created by Discoverer Plus OLAP are also removed. If you want to save these objects, then export the Discoverer Catalog before uninstalling it.

To uninstall the Discoverer Catalog:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  2. From the Discoverer menu, select Catalog, and then select Uninstall.

    The Uninstall Catalog page is displayed.

  3. Enter the host name, port number, and SID for the database, the DBA user name and password, and the D4OSYS password. Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or later).

  4. Click OK.

    A warning that the Discoverer Catalog will be uninstalled is displayed.

  5. Click OK to complete the uninstallation process.

Note:

Alternatively, you can uninstall a Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog.".

5.2.4 Exporting a Discoverer Catalog

You can export the entire contents of a Discoverer Catalog when you want to perform a backup or to migrate to a new version. The format of the exported file is PXIF (Persistence XML Interchange File). The exported XML file contains information about folder organization, object definitions, properties, and privileges.

To export a Discoverer Catalog:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  2. From the Discoverer menu, select Catalog, and then select Manage.

    The Manage: Discoverer Plus OLAP Login page is displayed.

  3. Enter the host name, port number, and SID for the database, and the D4OSYS password. Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or later).

  4. Click Login

    The Manage Catalog page is displayed.

  5. Click Export.

    The File Download dialog is displayed.

  6. Click Save.

    The Save As dialog is displayed.

  7. Specify a location and file name for the exported file, and then click Save.

Note:

Alternatively, you can export a Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog".

5.2.5 Importing a Discoverer Catalog

When you are migrating to a new version of the Discoverer Catalog or restoring from a backup, you can import a Catalog.

Notes

  • You can import only from a file that was created through the export of a Discoverer Catalog or BI Beans Catalog.

  • The import process adds new objects and overwrites existing objects with the same name.

  • Objects in the exported file and the imported Discoverer Catalog must have access to the same OLAP schemas and metadata.

  • You import the entire contents of an exported file, if the same users are authorized in the target Catalog as were authorized in the exported Catalog. You import object definitions, but you do not import user definitions. Therefore, if you import from a file that contains objects that are owned by a user who is not authorized to use the target Catalog, then that user's objects are not imported.

  • When you import catalog contents from one Discoverer Catalog to another, all path names of the exported objects (workbooks, calculations, and saved selections) are preserved in the catalog. Because most objects are stored in the Users/username folder or the Shared/username folder, it is important that these folders exist. Therefore, to facilitate a successful import, ensure that all users exist in the target environment before the import.

    For any users that do not exist in the target environment, you must create them with the database administration tools and authorize them using the Discoverer Administration tools.

To import a Discoverer Catalog:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  2. From the Discoverer menu, select Catalog, and then select Manage.

    The Manage: Discoverer Plus OLAP Login page is displayed.

  3. Enter the host name, port number, and SID for the database, and the D4OSYS password. Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or later).

  4. Click Login

    The Manage Catalog page is displayed.

  5. Click Import.

    The Import Catalog window is displayed.

  6. Specify the file name of the previously exported or backed up Catalog that you want to import.

  7. Click Import.

Note:

Alternatively, you can import a Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog".

5.3 Maintaining authorized users and roles for the Discoverer Catalog

When you authorize users and roles for the Discoverer Catalog, you do not create new users or roles. Instead, you authorize existing database users and roles to access the Discoverer Catalog. Authorized users log in to Discoverer Plus OLAP using their database user names. When you authorize users and roles for the Discoverer Catalog through Fusion Middleware Control, the users and roles are automatically assigned the D4OPUB role.

5.3.1 Characteristics of the folder structure of the Discoverer Catalog?

After users and roles are authorized, they can create folders within the existing folder structure of the Discoverer Catalog (using Discoverer Plus OLAP). The folder structure has the following characteristics:

  • The folder structure is created automatically when you install the Discoverer Catalog.

  • Folders for each user and role are created automatically within the structure when users and roles are authorized.

  • The folder structure was designed so that users can quickly store and find their own objects, but the structure also allows for sharing of objects.

5.3.2 Folders in the structure

The structure of the Discoverer Catalog consists of one root folder that contains the following main folders:

  • Users

    The Users folder contains a subfolder for each user or role that is authorized to use Discoverer Plus OLAP and is intended to store that user's or role's private objects. This subfolder is named with the user or role name, in all uppercase letters. Initially, each user's and role's subfolder contains no other subfolders, but users can create subfolders to suit their needs using Discoverer Plus OLAP. Each user or role has Full Control privileges on his or her subfolder. The D4OSYS user has Full Control privileges over the Users folder and all of its subfolders. No other users or roles have any privileges on the subfolders that belong to other users or roles.

  • Shared

    The subfolders in the Shared folder enable sharing of objects among users of Discoverer Plus OLAP. The Shared folder contains a subfolder for each user or role that is authorized to use Discoverer Plus OLAP. Initially, each user's and role's subfolder contains no other subfolders. Users can create subfolders to suit their needs using Discoverer Plus OLAP, because they have Full Control privileges for their own subfolders.

    Each user and role has Read privileges on all other subfolders under the Shared folder, because the D4OPUB role has Read privileges and all Discoverer Plus OLAP users have the D4OPUB role. A user can give other users and roles Write privileges on the subfolders in that user's or role's Shared subfolder. The D4OSYS user also has Full Control privileges over the Shared folder and all of its subfolders.

5.3.3 Types of privileges for objects and folders

The following list describes the privileges that are available for objects and folders in the Discoverer Catalog. Note that users can also have no privileges on certain objects and folders.

  • Add to Folder: Enables you to view the contents of a folder, to open a folder and the objects in it, and to create a folder or object (applies to folders only.

  • Full Control: Enables you to change privileges on a folder or object and to create or change the folder or object.

  • List: Enables you to view the contents of a folder (applies to folders only.

  • Read: Enables you to open a folder or object.

  • Write: Enables you to create, delete, or change a folder or object.

Privileges are cumulative. That is, the higher-level privileges inherit the controls of the privileges lower in the list. For example, the Write privilege inherits the controls of Read, List, and so on.

If a certain privilege is not applicable, then the next privilege down in the list is acquired. For example, suppose you have Write privileges on a folder on which the user that is named "Sam" has List privilege (which applies only to folders). You create an object in that folder. The user "Sam" acquires the privilege below the List privilege on that object, which is no privileges, so the user "Sam" cannot even see the object.

5.3.4 Managing privileges as the D4OSYS user

End users have Full Control privileges on all folders and objects in their Users/username folder and on the Shared/username folder, if they have been assigned that role. The D4OSYS user has Full Control privileges on the Shared folder and on the Users folder and on all their subfolders and objects.

While the D4OSYS user can change the default privileges that are assigned to all folders and objects when the Discoverer Catalog is installed, such practice is not recommended. Similarly, users could invoke their Full Control privileges to reduce the privileges of the D4OSYS user. Such practice is strongly discouraged, because it prevents the D4OSYS user from backing up users' objects.

5.3.5 Ensuring that users can use Discoverer Plus OLAP

In order for a user to run Discoverer Plus OLAP, that user must meet the following criteria:

  • Has an account on the database on which the Discoverer Catalog is installed.

  • Is assigned the D4OPUB role; that is, must be authorized to use Discoverer Plus OLAP on that database, as described in Section 5.3.6, "Authorizing user and role access to the Discoverer Catalog".

  • Is authorized to use the OLAP measures that the user needs, which requires that the user meet the following criteria:

    • Has been assigned the OLAP_USER role, which is inherited by the D4OPUB role.

    • Has access to the OLAP data, which is controlled by the Oracle OLAP database administrator.

Note: You cannot use Discoverer Plus OLAP with Oracle e-Business Suite security.

In addition, you must ensure that the Allow users to create their own connections in Discoverer Plus and Discoverer Viewer check box is not cleared in the Discoverer Administration page in Fusion Middleware Control. When this box is cleared, private connections are not available. Discoverer Plus OLAP requires private connections, as described in Section 5.3.8, "Using private versus public connections when accessing OLAP data".

For more information about assisting end users, see Section 5.5, "Information to be provided to end users"

5.3.6 Authorizing user and role access to the Discoverer Catalog

You authorize users and roles to log in to Discoverer Plus OLAP on a particular database. When you authorize a user or role directly, that user or role is immediately assigned the D4OPUB role and folders are created in the Users and Shared folders with the appropriate privileges. If you assign the D4OPUB role indirectly through another role, then the user and folders are added to the Discoverer Catalog when the user next connects.

To authorize a user or role to access the Discoverer Catalog:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  2. From the Discoverer menu, select Catalog, and then select Manage.

    The Manage: Discoverer Plus OLAP Login page is displayed.

  3. Enter the host name, port number, and SID for the database, and the D4OSYS password. Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or later).

  4. Click Login.

    The Manage Catalog page is displayed.

  5. Click Authorize Users.

    The Authorize Users window is displayed.

  6. In the Available Users and Roles list, select the users and roles that you want to authorize.

  7. Click Move.

    The selected users and roles move from the Available Users and Roles list to the Selected Users and Roles list.

  8. Click OK.

Note:

Alternatively, you can authorize user and role access to the Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog".

5.3.7 Revoking user or role access to the Discoverer Catalog

When you revoke access, the following steps are performed:

  • The D4OPUB role is removed from that user or role.

  • All privileges that have been assigned to that user or role are removed.

  • All user-related properties (such as Created On and Created By) are updated to refer to the D4OSYS user. None of the objects that the revoked user or role created are deleted.

The access rights of the D4OSYS user cannot be revoked. The D4OSYS user is removed only when the Discoverer Catalog is uninstalled.

To revoke user or role access:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages."

  2. From the Discoverer menu, select Catalog, and then select Manage.

    The Manage: Discoverer for OLAP Login page is displayed.

  3. Enter the host name, port number, and SID for the database, and the D4OSYS password. Note that passwords are case sensitive in Oracle databases (Enterprise Edition version 11.1 or later).

  4. Click Login.

    The Manage Catalog page is displayed.

  5. Click Authorize Users.

    The Authorize Users window is displayed.

  6. In the Selected Users and Roles list, select the users and roles for which you want to revoke access.

  7. Click Remove.

    The selected users and roles move from the Selected Users and Roles list to the Available Users and Roles list.

  8. Click OK.

Note:

Alternatively, you can revoke user or role access to the Discoverer Catalog by using the Discoverer Plus OLAP command line utility. For more information, see Section 5.9, "Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog".

5.3.8 Using private versus public connections when accessing OLAP data

When users connect to a Discoverer component, they use either a public or a private connection. End users can also login directly without using or creating a connection.The following list describes how users work with public and private connections when connecting to OLAP data:

  • Private connections: Users must use a private connection when connecting to Discoverer Plus OLAP. They can also use a private connection when connecting to Discoverer Viewer and Discoverer Portlet Provider for accessing OLAP data. With private connections, users can use Single Sign-On or not. Private connections that are not created with Single Sign-On active require users to re-enter their password.

  • Public connections: You can use Fusion Middleware Control to create public connections for users who want to access OLAP data through Discoverer Viewer and Discoverer Portlet Provider.

For more information on public and private connections, see Chapter 3, "Managing Oracle BI Discoverer Connections"

5.4 Customizing the look and feel of Discoverer Plus OLAP

You use Fusion Middleware Control to customize the look and feel of Discoverer Plus OLAP, using the same page on which you configure Discoverer Plus Relational.

You can configure the following items for Discoverer Plus OLAP:

To configure the look-and-feel for Discoverer Plus OLAP:

  1. Go to the Fusion Middleware Control Discoverer Home page.

    For more information, see Section 4.1.3, "How to display the Fusion Middleware Control Discoverer Home page and Discoverer component Home pages".

  2. Click the Discoverer Plus component.

  3. Click Configure.

    The Discoverer Plus Configuration page is displayed.

  4. Use the fields on this page to specify configuration settings.

  5. Click OK to apply the changes.

5.5 Information to be provided to end users

After you have configured the Discoverer Catalog and Discoverer Plus OLAP, you should ensure that users have the following information, which enables them to use Discoverer Plus OLAP:

5.6 Configuration diagnostic utility for Discoverer Plus OLAP

Discoverer Plus OLAP includes a utility that examines and reports on the configuration of the OLAP environment. Its purpose is to gather information about the configuration, to help you and Oracle Support diagnose problems that end users experience when running Discoverer Plus OLAP.

For more information about how users run the diagnostic utility, see the Discoverer Plus OLAP Help. Users simply click a button in an error dialog or choose a menu option. The dialog that is displayed provides basic output from the utility and allows end users to run another test that provides more detailed output. The Help topics instruct users to share the output with their database administrator if they need assistance.

5.6.1 Forms of output from the utility

The utility produces two forms of output, as described in the following list:

  • Output that is written directly to the dialog in which users run the utility -- For details, see Section 5.6.2, "Description of output from the utility".

  • An XML file -- Users name and store this file as they like, after running the utility and viewing the results in the dialog. The file contains the output that was displayed in the dialog, including version information for various components, the detailed stack trace of any errors, and a list of the folders, measures, and dimensions that were found in the database (that is, the metadata). You can send this file to Oracle Support Services as an e-mail attachment to get help in diagnosing problems.

5.6.2 Description of output from the utility

The following labels describe the items that the utility displays in the dialog and in the XML file. These labels are listed according to the sequence in which the utility performs the various checks. Many items relate to version numbers. See the installation guide that you used when installing Discoverer for information on the appropriate version numbers.

5.6.2.1 JDK version

The version number of the JDK that is being used, such as 1.5.0.

5.6.2.2 BI Beans internal version

The internal version number of BI Beans that is installed.

5.6.2.3 Discoverer Plus OLAP version

The internal version number of the Discoverer server that is installed.

5.6.2.4 Discoverer version

The internal version number of the Discoverer Plus component that is installed.

5.6.2.5 Connect to database

Whether the utility was able to establish a database connection. If a connection was established, then the result is "Successful." Otherwise, the result is "Unsuccessful." If the utility cannot connect to the database, then you can:

  • Examine the errors that are shown in the dialog for more information.

  • Verify that all the connection information (such as user name and password) is correct.

  • Verify that the database is running and accepting connections.

5.6.2.6 JDBC driver version

The version of the JDBC driver that is being used.

5.6.2.7 JDBC JAR file location

The full path name to the directory that contains the JDBC driver JAR file.

5.6.2.8 Database version

The version of the Oracle database to which Discoverer Plus OLAP is connected.

5.6.2.9 OLAP Catalog version, OLAP AW Engine version, OLAP API Server version

The versions for various OLAP components. The returned values might not exactly match the "Database version," due to database patch releases. Under certain circumstances, these versions are returned as "NA," which is not a problem that you must resolve.

5.6.2.10 BI Beans Catalog version

The internal version of the BI Beans Catalog that is installed. If the BI Beans Catalog is not installed, then this value is "NA; not installed in schema-name."

5.6.2.11 Discoverer Catalog version

The internal version of the Discoverer Catalog that is installed. If the Discoverer Catalog is not installed, then this value is "NA; not installed in schema-name." Discoverer Plus OLAP requires that the Discoverer Catalog be installed.

5.6.2.12 Authorized for Discoverer Plus OLAP

Whether the user who is running the utility is authorized to run Discoverer Plus OLAP.

5.6.2.13 OLAP API JAR file version

The version of the OLAP API client JAR file.

5.6.2.14 OLAP API JAR file location

The full path to the directory in the user's installation that contains the OLAP API client JAR files.

5.6.2.15 Load OLAP API metadata

Whether the utility was able to load the metadata from the database. If the metadata was loaded, then the result is "Successful." Otherwise, the result is "Unsuccessful."

The database administrator must define appropriate metadata in the Oracle database to support business intelligence applications. For information about defining OLAP metadata, see Oracle OLAP User's Guide.

If the metadata was not loaded, then verify that the metadata is correct. If you continue to have problems, then consult the OLAP forum on Oracle Technology Network or contact Oracle Support Services.

5.6.2.16 Number of metadata folders

The number of folders that were detected in the metadata from the database.

5.6.2.17 Number of metadata measures

The number of measures that were detected in the metadata from the database.

5.6.2.18 Number of metadata dimensions

The number of dimensions that were detected in the metadata from the database.

5.6.2.19 Metadata description

The full description of all the metadata from the database.

5.6.2.20 Error message description

If any errors occurred, then brief information about them is displayed at the appropriate location in the output in the dialog. For example, if the user entered an incorrect name or password, then information to this effect is noted immediately after the "Connect to database" label and no further output is included. The XML file of the output includes more detailed information than is provided in the dialog output.

5.7 URL parameters for the Discoverer Plus OLAP

Table 5-1, "Parameters for Discoverer Plus OLAP", describes the URL parameters that you can use to start Discoverer Plus OLAP.

Note: For an example of using URL parameters to start Discoverer Plus OLAP, see Section 12.5.6, "Example 6: Starting Discoverer Plus OLAP".

Table 5-1 Parameters for Discoverer Plus OLAP

Parameter and Values Description Example

autoconnect=yes|no

Specifies whether to automatically connect when all parameters are present. Yes is the default.

autoconnect=no

brandimage=logo_file_name

Specifies that you display a logo in the top right-hand corner of the Discoverer Plus OLAP screen.

You can reference this file in two ways:

  • Using a path that is relative to the location of the d4o.jar file on the server.

  • Using an absolute path.

brandimage=http://server.com:7777/discoverer/common/mylogo.gif

framedisplaystyle=
style

Specifies how to launch the Discoverer main window. The possible values for style are:

  • separate: Launch Discoverer's main window as a separate frame from the browser (that is, from the Discoverer Connections list). The browser window contains a Discoverer image and must remain open while Discoverer is being used.

  • embedded: Launch Discoverer's main window within the current browser window.

framedisplaystyle=separate

helpset=path/locale/helpset_file_name

Specifies a help set location that is different from the default Discoverer Plus OLAP help set, where:

path = Directory that contains the help set

locale = Two-character locale

helpset_file_name = Name of the help set file, such as myhelp.hs

Note: The help set must be in sub-directories that are named by the standard two-character locale.

helpset=mypath/en/myhelp.hs

lm=OLAP

Specifies that you are deploying Discoverer in a non-Single Sign-On environment.

lm=OLAP

locale=language[_country][_variant]

Specifies the language (and optionally the country and variant) that is used by Discoverer Plus OLAP. This parameter overrides the browser's language setting on the end user's client machine.

Tip: Use ISO codes to specify the language, country, and variant.

locale=es_ES

In this example, the language is Spanish and the country is Spain.

loglevel=type

Specifies the level of log messages to display for end users. The values for type are:


none = No messages (default)
error = Error messages
warning = Warning messages
informational = Informational messages
trace = Trace messages

loglevel=error

lookandfeelname=
type

Specifies a browser look and feel. The values for type are system, metal, windows, motif, oracle, and plastic.

You can also specify a custom LAF using the fully qualified Java class of the LAF (for example, javax.swing.plaf.metal.MetalLookAndFeel).

For more information about specifying a custom LAF on the Discoverer middle tier, see Section 8.1.3, "How to define a custom LAF for Discoverer Plus".

lookandfeelname=system

sheet=worksheetname

Specifies the name of the worksheet to open by default.

Note: If you use the sheet parameter multiple times in the URL, Discoverer Plus OLAP opens the last one.

sheet=Sales+Detail+Sheet

username=database_user_name

Specifies a database user name with which to connect to Discoverer Plus OLAP.

Note: If you do not specify a user name, password, host name, port number, and SID, then the Discoverer end user is prompted to enter the missing login information.

username=video_user

windowheight=number_of_pixels

Specifies the height in pixels of the Discoverer Plus OLAP application frame. If you do not use this parameter, then Discoverer Plus OLAP uses a default value.

windowheight=600

windowwidth=number_of_pixels

Specifies the width in pixels of the Discoverer Plus OLAP application frame. If you do not use this parameter, then Discoverer Plus OLAP uses a default value.

windowwidth=800

workbookname=
workbook_path_name

Specifies the folder location and the name of the workbook that you want users to display by default.

You must prefix folder names and workbook names with a slash (/) or the URL-encoded value for slash: %2F. For example, to specify Workbook A, which is stored in the Users/Jchan/ fikder in the Discoverer Catalog, enter:

&workbookname=Users/JChan/Workbook+A

workbookname=Users/JChan/Workbook+A


5.8 URL parameters for an OLAP worksheet in Discoverer Viewer

When you use URL parameters to access OLAP worksheets in Discoverer Viewer, usually, you can use the same URL parameters that you use with relational worksheets (for more information, see Section 12.7, "List of URL parameters common to Discoverer Plus and Viewer" and Section 12.9, "List of URL parameters specific to Discoverer Viewer"). However, the URL parameter for specifying an OLAP worksheet in Discoverer Viewer is different, as described in Table 5-2, "Parameters for an OLAP worksheet in Discoverer Viewer".

Table 5-2 Parameters for an OLAP worksheet in Discoverer Viewer

Parameter and Values Description Example

worksheetName=workbook_path/worksheet_name

Specifies the folder location, workbook name, and name of the worksheet to open.

You must prefix folder names, workbook names, and worksheet names with a slash (/) or the URL-encoded value for slash: %2F). For example, to specify a worksheet called Export 1 in Workbook A, which is stored in the Users/Jchan/ folder in the Discoverer Catalog, enter:

&worksheetName=Users/JChan/Workbook+A/Export+1

Note: Do not prefix the root folder name with a slash. For example, specify &worksheetName=Users, not &worksheetName=/Users.

worksheetName=Users/JChan/Workbook+A/Export+1

lm=OLAP

Specifies that you are deploying Discoverer in a non-Single Sign-On environment.

lm=OLAP


Note: For an example of using URL parameters to start Discoverer Viewer, see Section 12.5.9, "Example 9: Opening an OLAP worksheet in Discoverer Viewer".

5.9 Using the Discoverer Plus OLAP command line utility to manage the Discoverer Catalog

Discoverer Plus OLAP includes a command line utility for performing administrative functions. This utility is called d4o.jar and resides in the directory ORACLE_HOME/discoverer/lib.

To launch the utility, run the following command:

java -classpath d4o.jar oracle.dss.d4o.administration.D4OCommand subcommand -h host -po port -sid sid -su "sys as sysdba" -sp su_password -p d4o_password -t tablespace

You can obtain a list of all available commands by entering the following command:

java -classpath d4o.jar oracle.dss.d4o.administration.D4OCommand