Oracle Discoverer Viewer and Web Cache Oracle Discoverer Configuration Considerations Oracle Discoverer Deployment Considerations

14-24 Oracle Fusion Middleware High Availability Guide Oracle Discoverer External Dependencies Discoverer requires an Oracle HTTP Server and Enterprise Manager Fusion Middleware Control. The database schema for Discoverer and the portlet schema must be loaded before installing Discoverer by using the Repository Creation Utility RCU. Discoverer interacts with customer databases that contain Discoverer workbooks and the Discoverer End User Layer and other data sources. For more information, see the About the Discoverer database tier section in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer. Oracle Web Cache can be used to configure load balancing for Discoverer. The Portlet Provider component of Discoverer can provide portlets to Oracle Portal and Oracle Web Center. The Web Services component of Discoverer can be used by external clients such as Oracle BI Publisher and Oracle BI Enterprise Edition to obtain Discoverer connections and workbooks. It is recommended but not mandatory to restrict access to Oracle Discoverer by using Oracle Single Sign-On SSO. Discoverer Process Flow See the How does Discoverer work? section in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer. Connection Protocols Client browsers send HTTP requests to the Discoverer Java EE application. The Discoverer Java EE application accesses the database schema by using WebLogic Server data sources. The Discoverer Session Server non-Java EE component uses the OCI layer to connect to data sources. The Discoverer Java EE application and the Discoverer Session Server processes communicate by using CORBA.

14.5.1.2 Oracle Discoverer Viewer and Web Cache

You can improve Discoverer Viewer performance and availability by using Oracle Web Cache. For information about when and how to use Web Cache, see the Using Discoverer Viewer with Oracle Web Cache chapter in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

14.5.1.3 Oracle Discoverer Configuration Considerations

The environment and behavior of Oracle Discoverer are controlled by Discoverer preferences and configuration parameters. ■ For information about the list of preferences and the procedure to change preference settings, see Managing Discoverer Preferences in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer ■ Configuration parameters are stored in the configuration.xml file. For information about configuration parameters and how you can define settings for those parameters, see Managing and Configuring Discoverer in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer. Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-25 For information about the location of the files in which preferences and configuration parameters are stored, see the Discoverer Configuration Files section in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

14.5.1.4 Oracle Discoverer Deployment Considerations

The Discoverer Java EE application deployment and contains basic deployment descriptors. ■ The discoverer.ear file consists of the following files: application.xml, jazn-data.xml, and weblogic-application.xml. These files are located in the DOMAIN_HOMEconfigfmwconfigserversWLS_ DISCOapplicationsdiscoverer_versionconfiguration directory, where DOMAIN_HOME is the name of the domain directory. ■ The discoverer.war file contains the following files: custom-laf.xml, plus_ versions.properties, uix-config.xml, portlet.xml, weblogic.xml, struts-config.xml, and web.xml. These files are located in the DOMAIN_HOMEconfigfmwconfigserversWLS_ DISCOapplicationsdiscoverer_versionconfiguration directory, where DOMAIN_HOME is the name of the domain directory.

14.5.1.5 Oracle Discoverer Log File Locations