Oracle Hyperion Provider Services Component Characteristics

Configuring High Availability for Oracle Business Intelligence and EPM 15-25 Figure 15–4 Provider Services Single Instance Architecture This figure shows the single instance Oracle Hyperion Provider Services architecture Provider Services contains three subcomponents: Essbase Java API, SmartView Provider, and an XMLA XML for Analysis provider. These subcomponents service Java API clients, SmartView clients, and XMLA clients, respectively. Provider Services is designed with three different servlets, one for each subcomponent. Communication between clients and Provider Services is over the HTTPS protocol. The JAPI and XMLA clients are designed for Essbase communication. The Smart View client enables users to connect to data sources such as Essbase, Oracle Hyperion Planning, Fusion Edition and Oracle BI EE servers.

15.1.5.1 Oracle Hyperion Provider Services Component Characteristics

The following sections describe Prover Services Component characteristics.

15.1.5.1.1 State Information Provider Services session information is stored in memory

until the user disconnects or the session times-out.

15.1.5.1.2 Runtime Processes Provider Services is a Java-based enterprise application

deployed on the WebLogic server application container. At runtime, there is a single Java process, which is the container. Provider Services runs no other external processes.

15.1.5.1.3 Process Lifecycle The lifecycle of the Provider Services process is the same as

the process lifecycle for any standard Java- based enterprise application deployed on a WebLogic server.

15.1.5.1.4 Request Flow A dispatcher such as Oracle HTTP Web Server acts as a

gateway, delivering requests to the Provider Services instances that are part of the cluster. Provider Services supports sticky sessions, so that when a user session establishes with a Provider Services instance, the same instance handles all subsequent requests from the client until the user disconnects. If a Provider Services instance fails, the user must disconnect the existing invalid session and log on again, using the same URL the dispatcher URL as for the failed session.

15.1.5.1.5 External Dependencies Provider Services is dependent on Hyperion Registry.

The SmartView Provider component stores the Data Sources datasources.xml and Smart Slices in the registry database using Registry Java APIs. The Essbase Java API component also uses the Hyperion registry for maintaining domain-related HTTP HTTP HTTP TCPIP JDBC Smart View Client Excel Provider Services Smart View Provider XMLA Provider Java API Hyperion Registry XMLA Client Java API Client Essbase BI EE 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