Oracle Hyperion Financial Reporting High Availability Architecture Protection from Failures and Expected Behaviors

Configuring High Availability for Oracle Business Intelligence and EPM 15-35 Control: com.hyperion.FinancialReporting and com.hyperion.Annotations.

15.1.9.1.5 Deployment Artifacts Financial Reporting has these Deployment Artifacts:

■ FREssClient.ear – Contains the Enterprise Scheduler Service server implementation for Financial Reporting jobs, deployed to the FinDomain Enterprise Scheduler Service. ■ HReports.ear – Primary Financial Reporting Web Application deployed to the BIDomain. Shared Libraries deployed to the BIDomain that the Financial Reporting Web Application requires include: epm-shared-libraries epm-fr-libraries epm-annotation-libraries epm-frweb-libraries epm-misc-libraries.

15.1.9.1.6 Log Files Financial Reporting logs are in domain

home servers{weblogic.Name}logsfinancialreporting. Note that {weblogic.Name}is the managed server name, for example bi_server1 or bi_ server2.

15.1.10 Oracle Hyperion Financial Reporting High Availability Concepts

Oracle Hyperion Financial Reporting supports high availability for the following functionality: ■ Report Execution and Viewing as HTML or PDF: – Prompt – POV changes – Page dimension drop-down HTML only – Annotation creation and viewing – Expansion – Drill-through Not available in PDF ■ Book execution and viewing as HTML or PDF ■ Export to Microsoft Office formats

15.1.10.1 Oracle Hyperion Financial Reporting High Availability Architecture

Figure 15–2 shows Essbase in a highly available Oracle BI EE deployment.

15.1.10.1.1 Shared Files and Directories There are no shared files or directories. All

common properties and documents are either in the relational database or stored in the Oracle BI Presentation Services repository.

15.1.10.1.2 Cluster-Wide Configuration Changes Except for PrintServer, configuration is

cached. Modifications affect only the server where they are made until the next restart of the other server. Print servers are not cached and can be added or removed at any time.

15.1.10.2 Protection from Failures and Expected Behaviors

Financial Reporting supports failover and session serialization if you also deploy the following components: 15-36 Oracle Fusion Middleware High Availability Guide ■ Oracle Business Intelligence Enterprise EditionOracle BI Presentation Services – Financial Reporting uses web service connections to Oracle BI Presentation Services, with failover from the current Oracle BI Presentation Services connection fails to other catalog nodes, assuming these conditions: – The catalog application server, Presentation Services, and file storage are clustered or replicated. – The catalog location configured during applications provisioning references the proxy server and not a direct catalog Web application server. ■ Essbase – Financial Reporting reports must target Essbase using the Provider Services URL, and Provider Services must be configured with active and passive Essbase servers. When Essbase fails, Financial Reporting connects through the Oracle Hyperion Provider Services URL to the backup server, and Essbase queries are reissued without interruption to the user request. ■ RDBMS – The database must support failover. Connections are handled through the WebLogic JDBC configuration and connection pooling. ■ Oracle Internet DirectoryOAM ■ Oracle HTTP Server is expected to provide failover and provide integration point for all components. Financial Reporting configuration should target Oracle BI Presentation Services through Oracle HTTP Server or a load-balanced URL and not directly target the catalog server. ■ Oracle Hyperion Financial Reporting, Fusion Edition PrintServer – At least two PrintServer hosts should be deployed on Windows machines and configured with the system.

15.1.11 Allocation Manager Component Architecture and Characteristics