Managing Essbase System Administration in Oracle Business Intelligence

You manage Essbase system administration in Oracle Business Intelligence by starting and stopping Essbase Agents, enabling and viewing log files, setting logging levels, migrating Essbase configuration between domains, monitoring Essbase metrics, and backing up and recovering Essbase data.

This topic contains the following sections:

For information about managing system administration in Oracle Business Intelligence, see Introduction to Oracle Business Intelligence System Administration.

Starting and Stopping Essbase Components

You can monitor status, and start and stop Essbase components using BI process control commands (uses JAgent).

For more information, see Managing Oracle Business Intelligence Processes.

Maintaining High Availability of Essbase Components in Oracle Business Intelligence

High availability for Essbase in Oracle Business Intelligence is automatically maintained using an active-passive fault tolerance model.

Scaling Out Essbase to Support High Availability

You scale out Essbase onto additional computers to support high availability between computers. Scale-out is achieved in a similar way to existing Oracle BI EE components (see Managing Availability in Oracle Business Intelligence (Horizontally Scaling).

About the Essbase Active-Passive Topology

The two-node active-passive topology applies to the Essbase Server and Agent plus the mid-tier Essbase Administration Services, Analytic Provider Services, and Essbase Studio Server components.

For information, see Oracle Essbase High Availability Concepts, Configuring Oracle Essbase Clustering, and Oracle Hyperion Provider Services Component Architecture in High Availability Guide.

Managing Essbase Capacity

You manage Essbase capacity within Oracle Business Intelligence by monitoring Essbase components and service levels using Fusion Middleware Control to answer the following questions:

Configuring Logging for Essbase Components

You configure logging for all Essbase components in the BI Domain logging.xml file.

The file is located in:

DOMAIN_HOME/config/fmwconfig/servers/<BI_MANAGED_SERVER_NAME>

Log configuration details for each Essbase subcomponent, along with the location of the corresponding Oracle Diagnostic Log (ODL) files are provided below:

Note:

To capture every possible level of logging information for a particular component, set the logger level field value to 'TRACE:32'.

Essbase Java-Agent specific Logging Configuration

<log_handler name='jagent-handler-text' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
   <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/essbase/jagent.log'/>
   <property name='maxFileSize' value='10485760'/>
   <property name='maxLogSize' value='104857600'/>
   <property name='useSourceClassAndMethod' value='true'/>
</log_handler> 
<logger name='oracle.JAGENT' level='NOTIFICATION:1' useParentHandlers='false'>
   <handler name='jagent-handler-text'/>
</logger>

Essbase Applications specific Logging Configuration

<log_handler name='serverhandler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
         <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/essbase/essbase'/>
         <property name='maxFileSize' value='10485760'/>
         <property name='maxLogSize' value='524288000'/>
</log_handler>
<logger name='DefSvrLogger' level='TRACE:1' useParentHandlers='false'>
         <handler name='serverhandler'/>
</logger>

Provider Services (APS) specific Logging Configuration

<log_handler name='provider-services-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
   <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/aps/apsserver.log'/>
   <property name='maxFileSize' value='10485760'/>
   <property name='maxLogSize' value='104857600'/>
</log_handler>
<logger name='oracle.EPMOHPS' level='WARNING' useParentHandlers='false'>
   <handler name='provider-services-handler'/>
</logger>

Essbase WebServices specific Logging Configuration

<log_handler name='essbase-ws-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
   <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/essbasews.log'/>
   <property name='maxFileSize' value='10485760'/>
   <property name='maxLogSize' value='104857600'/>
</log_handler>    
<logger name='oracle.EPMOHEWS' level='WARNING:1' useParentHandlers='false'>
   <handler name='essbase-ws-handler'/>
</logger>

Essbase Cube Deployment Service specific Logging Configuration

<log_handler name='cds-handler' class='oracle.core.ojdl.logging.ODLHandlerFactory'>
   <property name='path' value='${domain.home}/servers/${weblogic.Name}/logs/cds/cds.log'/>
   <property name='maxFileSize' value='10485760'/>
   <property name='maxLogSize' value='104857600'/>
</log_handler>
<logger name='oracle.essbase.cds' level='NOTIFICATION:1' useParentHandlers='false'>
   <handler name='cds-handler'/>
</logger>

Migrating Essbase Configuration Between Domains

You can migrate an Essbase configuration between domains for an Oracle Enterprise Performance Management System installation.

For more information, see Moving Oracle Hyperion Enterprise Performance Management System to a Target Environment in Administering Oracle Fusion Middleware.

Monitoring Essbase Metrics

You monitor Essbase metrics using Fusion Middleware Control.

For more information, see Monitoring Service Levels.

Backup and Recovery of Essbase Data

This section describes backing up and recovering Essbase data when Essbase is installed with Oracle Business Intelligence.

For information about backing up and recovering Essbase data, see: