Oracle Essbase Component Characteristics

Configuring High Availability for Oracle Business Intelligence and EPM 15-21 Essbase Agent box. Below the Oracle Essbase Agent box are from left to right the OPMN box, an Essbase Application Server box, and another Essbase Application Server box. Below the APPHOST1 box is the Essbase Registry storage device. There is an arrow from the BI_SERVER1 box to the Essbase Registry. There is another arrow from the BI_SERVER1 box to the Oracle Essbase Agent. There is a two-headed arrow between the Oracle Essbase Agent box and the OPMN box. There is a two-headed arrow between the Oracle Essbase Agent box and the first Essbase Application Server box. There is a two-headed arrow between the Oracle Essbase Agent box and the second Essbase Application Server box. There is a two-headed arrow between the Oracle Essbase Agent box and the Essbase Registry. There is a two-headed arrow between the first Essbase Application Server box and the Essbase Registry. There is a two-headed arrow between the second Essbase Application Server box and the Essbase Registry.

15.1.3.1 Oracle Essbase Component Characteristics

Essbase component architecture comprises four tiers: ■ Web: Oracle HTTP Server ■ Application: Oracle Hyperion Provider Services, a mid-tier enterprise application deployed on a WebLogic application server Provider Services communicates with Essbase Agent and Essbase Servers using TCPIP. ■ Essbase Service: Essbase Analytical Services, comprising OPMN, Essbase Agent, and Essbase application servers OPMN communicates with Essbase Agent using Oracle Net Services. Essbase Agent acts as a coordinator between clients and Essbase application servers. Essbase Agent has a pipe communication channel with the servers. It also communicates using TCPIP. ■ Storage: The Hyperion Registry is a repository that stores configuration information in a relational database. Essbase Agent and Essbase application servers communicate with the back-end database using JDBC or ODBC.

15.1.3.1.1 State Information The Oracle Essbase session state is in memory, and there is

no session failover. If a client session is lost, the client must log on again.

15.1.3.1.2 Runtime Processes Essbase Analytical Services comprises these processes at

runtime: ■ Oracle Process Manager and Notification Server OPMN: A daemon that monitors Oracle Fusion Middleware components, including Essbase OPMN-managed components are specified in opmn.xml. You can use a command-line interface to OPMN to start, stop, restart, and monitor Essbase Agent; see Section 15.1.1.1.1, Process Lifecycle. It does not start or stop the Essbase Application Server process directly. OPMN communicates with Essbase Agent using Oracle Net Services. 15-22 Oracle Fusion Middleware High Availability Guide ■ Essbase Agent ESSBASE: The process responsible for coordinating user requests for applications. Essbase Agent is directly managed by OPMN. Essbase Agent manages application servers. ■ Essbase Application Server ESSSVR : The Essbase Application Server process handles all the data storage, caching, calculations, and data security.

15.1.3.1.3 Process Lifecycle Use the OPMN command opmnctl to start, stop, and

monitor Essbase Agent. Start To start OPMN and all its managed components, use ORACLE_ INSTANCEbinopmnctl startall. To start Essbase Agent only, with OPMN already running, use ORACLE_ INSTANCEbinopmnctl startproc ias-component=essbaseserver1, where essbaseserver1 is the name of the managed Essbase instance specified in opmn.xml. Stop To stop OPMN and all its managed components, use ORACLE_ INSTANCEbinopmnctl stopall. To stop Essbase Agent only if Essbase is configured in failover cluster mode and OPMN is already running, use ORACLE_INSTANCEbinopmnctl stopproc ias-component=essbaseserver1 process-type=Essbase, where essbaseserver1 is the name of the managed Oracle Essbase instance specified in opmn.xml. Monitor To get status information about the managed process, use ORACLE_ INSTANCEbinopmnctl status.

15.1.3.1.4 Request Flow Communication with Essbase can be through a cluster name

resolved by Provider Services, a URL resolved by the application, or a physical host and port.

15.1.3.1.5 External Dependencies Essbase uses Hyperion Registry, a database repository,

to store and retrieve configuration information. You can configure Essbase to work with an external directory service such as the Oracle Internet Directory OID. Essbase communicates with OID using LDAP protocol.

15.1.3.1.6 Configuration Artifacts The following table describes Essbase configuration

artifacts. Table 15–2 Essbase Configuration Artifacts File Location Description Essbase configuration file, essbase.cfg ARBORPATHbin Contains configurable parameter values for Essbase. The Essbase security file, essbase.sec ARBORPATHbin Contains information on security and applications Configuring High Availability for Oracle Business Intelligence and EPM 15-23

15.1.3.1.7 Deployment Artifacts Deployment artifacts required for correct setup of

Essbase include JDBC and ODBC, reg.properties, security artifacts, and so forth. Deployment artifacts must be passed to OPMN, which can then provision Essbase.

15.1.3.1.8 Log Files Diagnostic log files reside, by default, under ORACLE_

INSTANCEdiagnostics. Essbase Agent writes messages to Essbase.log: ■ Default location: ORACLE_INSTANCEdiagnosticslogsEssbasename of the Essbase instance essbase ■ Configured location: HYPERION_LOGHOMEessbase Essbase application server writes messages to application server log files: ■ Default location: ORACLE_INSTANCEdiagnosticslogsEssbasename of the Essbase instance ■ Configured location: HYPERION_LOGHOMEessbaseapp OPMN creates the Essbase console log, located by default in ORACLE_ INSTANCEdiagnosticslogsEssbasename of Essbase instance. The Essbase Forward Ping log, EssbasePing.log, is located by default in ORACLE_ INSTANCEdiagnosticslogsOPMNopmn. Lease manager logs are created only in a failover configuration. See Section 15.1.4.2, Protection from Failures and Expected Behaviors. The lease manager modules within Essbase Agent and Essbase Server write messages to their own logs: ■ Default location: ORACLE_INSTANCEdiagnosticslogsEssbaseias component nameessbase ■ Configured location: HYPERION_LOGHOMEessbase

15.1.4 Oracle Essbase High Availability Concepts