Oracle Hyperion Provider Services High Availability Architecture

15-26 Oracle Fusion Middleware High Availability Guide domain.db file information. All of this information is stored under the Registry’s LOGICAL_WEB_APP component of Provider Services.

15.1.5.1.6 Configuration Artifacts Provider Services has a configuration file,

essbase.properties, which resides in ORACLE_ HOMEproductsEssbaseapsbin. The Provider Services startup script requires the following JVM setting ESS_ES_HOME so that it can identify the configuration file at runtime. This setting specifies the PROVIDER_SERVICES_HOME folder, in which the binessbase.properties file resides.

15.1.5.1.7 Deployment Artifacts

Provider Services deployment artifacts include these files: ■ logging.xml: Configuration file for managing Provider Services logs ■ essbase.properties: Provider Services configuration file ■ aps.ear: Provider Services enterprise application archive

15.1.5.1.8 Log Files Provider Services logging is based on ODL logger. The Provider

Services startup script requires these JVM settings related to logging: ■ oracle.core.ojdl.logging.config.file: To specify the ODL logging.xml file path for Provider Services. ■ logging.folder: The location to store the Provider Services server log files.

15.1.6 Oracle Hyperion Provider Services High Availability Concepts

Provider Services deploys and runs within an application server environment such as Oracle WebLogic Server. To support Provider Services high availability, you can deploy multiple instances of Provider Services, using the WebLogic Server clustering and load balancing capabilities. For details on clustering enterprise applications such as Provider Services, see the WebLogic Server documentation.

15.1.6.1 Oracle Hyperion Provider Services High Availability Architecture

Figure 15–2 shows Oracle Hyperion Provider Services in a highly available Oracle BI EE deployment.

15.1.6.1.1 Hyperion Registry Structure for a Provider Services Cluster In the preceding

figure, LOGICAL_WEB_APP represents a cluster consisting of Provider Services instances. Each PROVIDER_SERVICES_WEB_APP component stores the actual server and port of its Provider Services instance; for example: LOGICAL_WEB_APPCluster_URL | ----- PROVIDER_SERVICES_WEB_APP 1 server1:port | Note: In a cluster including several Provider Services instances, a separate unique log location is defined for each instance. If the log location for an instance is under a Provider Services home, the administrator must grant read and write permissions to that folder for all Provider Services instances. Configuring High Availability for Oracle Business Intelligence and EPM 15-27 ----- PROVIDER_SERVICES_WEB_APP 2 | ----- PROVIDER_SERVICES_WEB_APP 2 server2:port_y The LOGICAL_WEB_APP component information specifies the Provider Services cluster URL, which is unique.

15.1.6.1.2 Cluster-Wide Configuration Changes Provider Services reads the

essbase.properties file only during startup. If the Provider Services administrator changes this file, the administrator must restart the Provider Services cluster so that all Provider Services instances in the cluster are synchronized with configuration settings.

15.1.6.1.3 OPMN Essbase Cluster Support To support Essbase clusters, clients

communicate with Provider Services to fetch the active Essbase node in the cluster. API clients CAPIJAPI must specify an Provider Services URL which contains the OPMN Essbase cluster name to obtain the active Essbase host instance details. Provider Services then retrieves the active Essbase node details from the Hyperion Registry. The remainder of this section describes the behavior for Provider Services and CJAPI client use cases.

15.1.6.1.4 Essbase Database Clustering by Provider Services Provider Services supports

high availability of Essbase databases with active-active clustering. Clustering Essbase cubes databases enables load balancing and failover support. Provider Services manages a series of active, duplicate databases that respond to user requests. Users connect to the database by specifying an Essbase cluster; the database that is accessed must be transparent to users. Provider Services facilitates the routing of connections between databases in a cluster, based on availability and precedence rules using the round-robin technique. The Essbase cluster supports read-only operations on the Essbase database. Write-back operations such as data load and outline editing are not supported.

15.1.6.2 Protection from Failures and Expected Behaviors