Propagation of Configuration Changes Across the Cluster Cluster-Wide Application Deployment Online Application Deployment Oracle Discoverer Process Failures

Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-27

14.5.2.3 Performance Recommendation

The Discoverer Java EE Servlet spawns a Session Server process for each HTTP request that it receives. If multiple Discoverer instances managed server and the associated oracle instance exist in a single machine, the load on the CPU might become very high because all Discoverer instances might spawn C++ processes simultaneously. Adding Discoverer instances on different machines yields better performance than adding them on the same machine.

14.5.2.4 Propagation of Configuration Changes Across the Cluster

Any configuration change must be implemented individually in each managed server in the cluster. You can achieve this by copying the configuration.xml file to all the managed servers. For information about the location of the configuration files, see the Discoverer Configuration Files section in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

14.5.2.5 Cluster-Wide Application Deployment

Each Discoverer Java EE application instance managed server should be associated with an Oracle instance that contains Discoverer components. These components are created during the configuration phase of the installation process. So adding managed servers to a cluster and deploying the Discoverer Java EE application from the WebLogic Server administration console are not supported. All the managed servers defined in the cluster are targets for deployment of the Discoverer Java EE application.

14.5.2.6 Online Application Deployment

Most of the Discoverer Java EE application-dependent jar files are available through shared libraries. Patching these shared libraries does not require the Discoverer Java EE application to be restarted. Changes to the following jar files, which are available through the system classpath, require the Discoverer Java EE application to be restarted. WL_HOME serverlibweblogic.jar ORACLE_HOME modulesoracle.jrf_11.1.1jrf.jar ORACLE_HOME opmnlibnonj2eembeans.jar ORACLE_HOME serverlibojdbc6.jar ORACLE_HOME opmnliboptic.jar ORACLE_HOME opmnlibiasprovision.jar ORACLE_HOME opmnlibons.jar ORACLE_HOME modulesoracle.adf.share_11.1.1oracle-el.jar ORACLE_HOME jlibshare.jar ORACLE_HOME jlibjewt4.jar

14.5.2.7 Oracle Discoverer Process Failures

For the Discoverer Java EE application to access databases, an entry for each database must be created in the ORACLE_INSTANCEconfigtnsnames.ora file. For more information, see the About configuring the tnsnames.ora file section in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer. 14-28 Oracle Fusion Middleware High Availability Guide

14.5.2.8 Oracle Discoverer Node Failures