18 Using Discoverer with Components of Oracle Fusion Middleware

This chapter explains how to use Discoverer with components of Oracle Fusion Middleware, such as Oracle Web Cache and Oracle Portal, and contains the following topics:

18.1 Using Discoverer with Oracle Fusion Middleware Control

Oracle Fusion Middleware Control provides a common look and feel, behavior and security infrastructure to configure the middle tier web components of Oracle Fusion Middleware with a single tool. Using a single tool for all Oracle Fusion Middleware components reduces the time spent on administration and configuration. You can use Oracle Fusion Middleware Control to configure Discoverer's middle tier web components.

For more information, see:

18.2 Using Discoverer with Oracle Reports

Discoverer users can share workbooks, export them to Oracle Reports (V7.0 and later) enabling Reports users to open a Discoverer workbook. The workbook SQL, additional formatting and calculations are passed to Oracle Reports using an XML based workbook. The workbook is translated into an Oracle Reports-compatible format that can be modified using Oracle Reports.

In Oracle Reports the look and feel of the original Discoverer workbook is retained so that the Oracle Reports user can continue to work on the Report in a standalone fashion. To further emphasize this point: no further interaction with the Discoverer server is required for the Reports user to enhance the file

For more information, see the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Discoverer Plus.

18.3 Using Discoverer with Oracle Web Cache

Oracle Web Cache helps e-businesses improve Web site performance issues. Oracle Web Cache is a content-aware server accelerator that improves the performance, scalability and availability of Web sites that run on Oracle Fusion Middleware and Oracle databases (version or later). High accessibility is achieved at high speed by applying the latest caching techniques provided by Oracle Web Cache.

By storing frequently accessed URLs in memory, Oracle Web Cache eliminates the need to repeatedly process requests for those URLs on the application Web server. Unlike legacy proxy servers that handle only static documents, Oracle Web Cache caches both static and dynamically generated content from one or more application Web servers. Because Oracle Web Cache is able to cache more content than legacy proxy servers, it provides optimal performance by greatly reducing the load on application Web servers.

For more information, see the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Discoverer Plus and Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

18.4 Using Discoverer with Oracle Warehouse Builder

Oracle Warehouse Builder (OWB) can generate Discoverer metadata. You can use OWB and Discoverer Bridge to create a Discoverer EUL in OWB's metalayer, and then create a Discoverer export file (.EEX file). The .EEX file can be imported into a Discoverer EUL using Discoverer Administrator (for more information, see "How to import EUL objects from a file using the Import Wizard"). The Discoverer EUL retains the folder and item lineage from OWB. You can display the folder and item lineage from OWB by using a Discoverer Lineage workbook.

To install the lineage workbook for use with Oracle Warehouse builder:

  1. Login to Discoverer Administrator as the Discoverer EUL schema owner.

  2. Import the lineage.eex file.

  3. Login to SQL*Plus as the Discoverer EUL schema owner.

    For example:

    > SQLPLUS myeul/myeul@myconnection

  4. Run the lineage.sql file.

    For example:

    SQL> start d:\<ORACLE_HOME>\discoverer\lineage.sql

    This script will ask you to input and verify the following:

    • the OWB URL Machine Name.Domain Name:Port

      For example, http://myserver.us.mycompany.com:7777

    • the OWB Virtual path to mod_plsql (the default is pls)

      For example, pls

    • the OWB Database Access Descriptor DAD (the default is portal30)

      For example, portal30

    • the OWB Browser schema

      For example, myowbinstall

    • the OWB Host name (that is, the name of the machine that runs the OWB repository)

      For example, myserver

      Note that the name must be the same as used in the OWB browser registration.

    • the OWB SID (that is, the database instance name)

      For example, ASdB

    • the OWB Schema where the OWB repository resides

      For example, owbrep

  5. Login to Oracle BI Discoverer Plus, Oracle BI Discoverer Viewer, or Oracle BI Discoverer Desktop as the EUL schema owner and open the Lineage workbook.

If you export and re-import the EUL, you must run lineage.sql again.

If you have previously imported EUL5.eex, the Lineage workbook would already be saved in the database. If this is the case, all you need to do is run lineage.sql.

18.5 Using Discoverer with OracleAS Single Sign-On Server

The OracleAS Single Sign-On Server provides a framework which allows any web-based client, inside or outside of Oracle Portal, to use Oracle's Single Sign-On services. OracleAS Single Sign-On is intended for use with an LDAP server which provides the means for storing and managing all the user credentials.

18.6 Using Discoverer with Oracle Portal

You can publish Discoverer workbooks and worksheets to Oracle Portal quickly and easily. Oracle Portal's intuitive user interface guides you through the publishing process step by step, enabling you to create powerful business intelligence portals with ease.

For more information about publishing to Oracle Portal, see the Oracle Fusion Middleware Guide to Publishing Oracle Business Intelligence Discoverer Portlets.