Oracle Reports State Information Oracle Reports External Dependencies Oracle Reports Specific Configuration Files Oracle Reports Connection Retry

Configuring High Availability for Oracle Portal, Forms, Reports, and Discoverer 14-11 pluggable-output destinations. The Reports Server also spawns runtime engines for generating requested reports, fetches completed reports from the Reports Server cache, and notifies the client that the job is ready. The reports server can be run stand-alone or in-process. Oracle Reports Engine The Reports Engine includes components for running SQL-based and pluggable data source-based reports, fetches requested data from the data source, formats the report, sends the output to cache, and notifies the Reports Server that the job is complete. Oracle Reports Cache The Reports Cache is used to store the output of reports, which have been successfully run. By using the reports cache it is not necessary to generate the same report repeatedly. Oracle Reports Queue The Reports Queue contains a list of the report requests. When processing capacity becomes available, the next report in the queue is executed. Oracle Reports Customer Databases Typically, reports are compiled using information stored in a variety of databases. These are referred to as customer databases. Oracle Single Sign On Although advisable it is not a mandatory requirement to restrict access to Oracle Reports using Oracle Single Sign-On SSO.

14.3.1.1 Oracle Reports State Information

Oracle Reports only state information is job metadata. For example, which reports are to be run, and the parameters with which they are run. This is often referred to as the reports queue. This information is stored in operating system files servername.dat, or alternatively in a database.

14.3.1.2 Oracle Reports External Dependencies

Oracle Reports requires Oracle HTTP Server to service requests. Optionally these requests may be cached by Oracle Web Cache, in which case it also acts in the capacity of a load balancer.

14.3.1.3 Oracle Reports Specific Configuration Files

The following table lists and locates configuration files used by Oracle Reports: File APPHOST1 Location APPPHOST2 Location rwserver.conf DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ REPORTSapplicationsreports_ 11.1.1.2.0configuration DOMAIN_ HOMEconfigfmwconfigserve rsWLS_ REPORTS1applicationsreports _11.1.1.2.0configuration reports_ohs.conf ORACLE_ INSTANCEconfigOHSohs1 moduleconf ORACLE_ INSTANCEconfigOHSohs1 moduleconf 14-12 Oracle Fusion Middleware High Availability Guide

14.3.1.4 Oracle Reports Connection Retry

This section describes the following connection retries: ■ Oracle Portal Database Connection Retry: If the connection from the Reports Server to the Oracle Portal database schema is dropped, the Reports Server tries to reestablish the connection before generating an error. If reconnection is successful, there is no need to restart the Reports Server. ■ Oracle Internet Directory Connection Retry: If the Oracle Internet Directory connection becomes stale, the Reports servlet and the Reports Server try to reestablish the connection before generating errors. If reconnection is successful, there is no need to restart the Reports Server. ■ Oracle Metadata Repository and Oracle Identity Management Outage: The outage of the Oracle Metadata Repository which stores security metadata does not bring down the Reports Server. If the Oracle Metadata Repository is unavailable, the Reports Server rejects new requests as a result of the component being unavailable. When the Oracle Metadata Repository is brought back on-line, the Reports Server recovers itself and begins to receive and process new requests. If Oracle Identity Management components become unavailable, the Reports Server also reject new requests, much like the outage of the Oracle Metadata Repository. ■ Reports Server Timeout: The Reports Server has a configurable timeout for waiting for requests to be returned from the database. This timeout must be set to a high enough value to allow valid reports to run but not so high as to cause excessively long waits.

14.3.1.5 Oracle Reports Process Flow