This chapter explains what you need to know about using Oracle Essbase and associated components when installed with Oracle Business Intelligence. The chapter includes a high-level roadmap; contains information about installation, system administration, service-level maintenance and security, and links to alternative sources of information.
This chapter includes the following sections:
High-Level Roadmap for Working with Essbase and Associated Tools in Oracle Business Intelligence
Installing Essbase and Associated Components with Oracle Business Intelligence
Managing Essbase System Administration in Oracle Business Intelligence
When you deploy Essbase with Oracle Business Intelligence in Release 12.2.1 the role of Essbase is specifically to accelerate Oracle Business Intelligence queries. Any other use of Essbase in the context of being used as a data source for Oracle Business Intelligence should leverage an EPM deployment of Essbase and related tools from 11g (see the EPM deployment guides). In future releases the role of Essbase deployed through Oracle Business Intelligence will expand. Therefore Oracle recommends installing the Essbase software to avoid future challenges with expanding the BI Domain. For more information, see "Understanding Essbase Deployed in BI 12.2.1" in Oracle Essbase Database Administrator's Guide.
Read this section before you start working with Essbase and associated tools in Oracle Business Intelligence. This high-level roadmap explains the tasks to perform and what choices are available. This section also indicates when to refer to the Oracle Business Intelligence documentation or the EPM System documentation.
To understand about working with Essbase and associated tools in Oracle Business Intelligence:
Read the rest of this chapter for an overview of Essbase concepts and configuration tasks.
Select the Essbase Suite option to install Essbase with Oracle Business Intelligence as described in Section 24.4, "Installing Essbase and Associated Components with Oracle Business Intelligence.".
Perform essential system administration tasks as described in Section 24.6, "Managing Essbase System Administration in Oracle Business Intelligence."
Perform these tasks after installing Essbase with Oracle Business Intelligence to ensure that Essbase is correctly configured.
Create, manage and use Essbase cubes as described in Section 24.7, "Working with Essbase Data in Oracle Business Intelligence."
When you install Essbase and associated tools as components of Oracle Business Intelligence, you do not perform a full Enterprise Performance Management System installation. Therefore, instructions for completing certain tasks can be different to those documented in the EPM documentation. When Essbase and associated tools are installed as components of Oracle Business Intelligence, they are configured to work with the same Oracle Fusion Middleware components as Oracle Business Intelligence rather than the EPM infrastructure components. Specifically, Hyperion Shared Services (HSS) are not installed with Oracle Business Intelligence, so you can ignore any references to HSS in the EPM documentation.
Use Table 24-1 to help you decide what to use to perform certain tasks in Oracle Business Intelligence compared to EPM systems, and which guides to reference.
Table 24-1 How to Perform Essbase-Related Tasks in Oracle Business Intelligence or EPM Systems and Which Guides to Reference?
| Essbase-Related Tasks Performed in Oracle BI and EPM Systems | How to Perform Essbase-Related Tasks in an Oracle BI System and Which Guides to Reference | How to Perform Essbase-Related Tasks in an EPM System and Which Guides to Reference |
|---|---|---|
|
Authentication |
Essbase should be setup as part of the installation process and all security in the 12.2.1 release should be handled automatically through the BI security. Refer to EPM 11g guides. |
When using an EPM system, use HSS, MaxL. Refer to EPM guides. |
|
Authorization |
Essbase should be setup as part of the installation process and all security in the 12.2.1 release should be handled automatically through the BI security. Refer to EPM 11g guides. |
When using an EPM system, use HSS, MaxL. Refer to EPM guides. |
|
Data Security (Provisioning) |
When using Essbase and associated tools installed with Oracle Business Intelligence, use Fusion Middleware Control and Security. Refer to EPM 11g guides. Note: There is no need to define Essbase filters for row level security, it is handled by BI security privileges. |
When using an EPM system, use HSS. Refer to EPM guides. |
|
Data Security (filter definitions) |
When using Essbase installed with Oracle Business Intelligence, use MaxL. Refer to EPM 11g guides. There is no need to define Essbase filters for row level security, it is handled by BI security privileges. |
When using an EPM system, use HSS and MaxL. Refer to EPM guides. |
|
System Configuration |
When using Essbase and associated tools installed with Oracle Business Intelligence, use Fusion Middleware Control, and essbase.cfg. Refer to Oracle Business Intelligence guides. |
When using an EPM system, use a text editor and MaxL, essbase.cfg. Refer to EPM guides. |
|
Backup and Recovery |
When using Essbase and associated tools installed with Oracle Business Intelligence use Fusion Middleware Control. Refer to Oracle Fusion Middleware Administrator's Guide and Oracle Business Intelligence guides. |
Refer to EPM guides. |
|
Migration (Test to Production) |
In 12.2.1 there is no ability to migrate existing Essbase content. |
NA. |
|
Essbase cubes |
When using Essbase you use the Acceleration Wizard. |
Refer to Oracle Essbase Database Administrator's Guide. |
|
Capacity |
N/A, Uses Active/Passive model (one cluster only). Refer to Oracle Business Intelligence guides. |
Use N Clusters 1, 2, 3, 4 agents. Uses the Active/Active or Active/Passive model. Refer to EPM guides. |
|
Availability |
Use Fusion Middleware Control. Uses - Active/Passive model. Refer to Oracle Business Intelligence guides. |
Refer to EPM guides. Uses Active/Active or Active/Passive model. |
|
Financial Reporting |
Enables you to use all Essbase-related FR functionality. |
Refer to EPM guides. |
|
Calculation Manager |
Enables you to use all Essbase-related Calculation Manager functionality. Refer to EPM 11g guides, but ignore the prerequisite to install HSS. Note that BI security is translated to EPM security model through CSS. |
Refer to EPM guides. |
|
Workspace |
Enables you to use all Essbase-related Workspace functionality Cannot register EPM Apps. Enables you to use: Refer to Oracle Business Intelligence guides. |
Refer to EPM guides. |
|
APIs |
No need for custom API work in 12.2.1. |
NA |
You can install Essbase and associated components when you install Oracle Business Intelligence. When you install these components with Oracle Business Intelligence, Essbase databases become available to Oracle Business Intelligence users, and you can manage Essbase components using a combination of Oracle Business Intelligence tools and Essbase EPM System tools. For information about which version of Essbase is installed, go to the Certifications page in Oracle Support and check the product details for appropriate releases of Oracle Business Intelligence Enterprise Edition with Oracle Essbase at:
Note:
You cannot add Essbase to an existing Oracle Business Intelligence installation although you can still use Essbase as a data source. The only way to install Essbase and associated components with Oracle Business Intelligence is to perform a new Oracle Business Intelligence installation and select the Essbase component.This topic contains the following sections:
You install Essbase Suite as part of an Oracle Business Intelligence Enterprise installation.
For more information, see Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
The Enterprise Install type creates and configures a single WebLogic Server Domain that contains a cluster with an Administration Server, and a Managed Server. If you select Essbase Suite during the install, then Essbase JEE components and Oracle Business Intelligence JEE components are installed on Managed Servers. For information, see Section 24.4.2, "Selecting the Essbase Suite Option During Install."
Selecting the Essbase Suite option during the install does the following:
Pre-selects the "Oracle Business Intelligence Enterprise Edition" option.
Installs the following Essbase-related JEE applications and services into the local Oracle BI EE Managed Server in an Enterprise Install:
Essbase Agent.
Cube Deployment Services.
Workspace (EPM application with limited functionality).
Calculation Manager (EPM application also known as Allocations Manager).
Hyperion Provider Services (APS).
Installs the following Essbase server processes:
Essbase App.
Enables you to download the following Essbase-related client applications from the Download BI Desktop Tools option, which is available in the Get Started area of the Home page for Oracle BI EE:
Smart View for Office (EPM application).
For more information, see "Downloading BI Desktop Tools" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Enables users to log in to the following Essbase command line tools:
ESSCMD.
ESSMSH (MaxL).
Enables users to log in through the following supported Essbase API languages:
JAPI.
C-API.
Note:
Client applications and API languages that are not included in this section are not supported with Essbase and related components installed with Oracle Business Intelligence.There are limitations for using the following Essbase tools when Essbase is installed with Oracle Business Intelligence:
MaxL command line interface.
The MaxL command line supports most of the tasks for Oracle Business Intelligence Essbase that are also possible with Oracle EPM System Essbase.
Note that you cannot use the MaxL command line to provision security.
When Essbase is installed with Oracle Business Intelligence, you do not get a full Enterprise Performance Management installation, and the only features supported are the Active/Passive cluster Acceleration Wizard and the Maxl commands to manage the acceleration wizard deployment.
Essbase Agent runs on two types of ports. Since Agent runs on BI Manged WebLogic Server, it has an HTTP Port that it listens to. Since this port is common to all the applications hosted on the BI managed server, this section is cover the changing the Essbase specific ports.
By default, Essbase Agent is always designed to run on 9799 port. To change this port, edit the AGENTPORT setting in essbase.cfg.
The Essbase Server uses a port range and by default it uses the available ports. To explicitly specify a server port range, define SERVERPORTBEGIN and SERVERPORTEND settings in essbase.cfg.
To manually update the Essbase Server port range or Essbase Agent port number:
Edit the essbase.cfg under DOMAIN_HOME/config/fmwconfig/biconfig/essbase.
Update AGENTPORT and add SERVERPORTBEGIN and SERVERPORTEND entries to suit your environment.
For example:
AGENTPORT 9799
SERVERPORTBEGIN 9000
SERVERPORTEND 9499
Save the essbase.cfg file.
Restart the BI Managed Server.
Note:
If you are performing this step after a scaleout, make sure to edit the corresponding essbase.cfg on all other nodes, to have the same entries as primary and restart the BI Cluster (all the managed servers of bi_cluster).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:
Section 24.6.3, "Configuring Logging for Essbase Components"
Section 24.6.5, "Migrating Essbase Configuration Between Domains"
For information about managing system administration in Oracle Business Intelligence, see Chapter 1, "Introduction to Oracle Business Intelligence System Administration."
You can monitor status, and start and stop Essbase components using BI process control commands (uses JAgent). For more information, see Chapter 2, "Managing Oracle Business Intelligence Processes."
High availability for Essbase in Oracle Business Intelligence is automatically maintained using an active-passive fault tolerance model.
Section 24.6.2.1, "Scaling Out Essbase to Support High Availability"
Section 24.6.2.2, "About the Essbase Active-Passive Topology?"
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 Section 3.4, "Managing Availability in Oracle Business Intelligence (Horizontally Scaling)."
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 Oracle Fusion Middleware High Availability Guide.
You manage Essbase capacity within Oracle Business Intelligence by monitoring Essbase components and service levels using Fusion Middleware Control to answer the following questions:
How do I know that Essbase components are running?
For information, see Section 8.2.2, "Displaying Oracle Business Intelligence Pages in Fusion Middleware Control."
How do I know if my system is overloaded?
For information, see Section 5.1, "Monitoring Service Levels."
You configure logging for all Essbase components in the BI Domain logging.xml file 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>
You configure logging for EPM components in the BI Domain logging.xml file located in:
DOMAIN_HOME/config/fmwconfig/servers/<BI_MANAGED_SERVER_NAME>
Log configuration details for each EPM subcomponent, along with the location of the corresponding Oracle Diagnostic Log (ODL) files are provided below:
Note:
All log configuration files conform to the Oracle Diagnostic Log (ODL) standard, although they can differ slightly in appearance.EPM Workspace logging configuration
<log_handlers>
<log_handler name="workspace_handler" class ="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/workspace/workspace.log"/>
<property name="maxFileSize" value="10485760"/>
<property name="maxLogSize" value="52428800"/>
<property name="useSourceClassAndMethod" value="true"/>
</log_handler>
<log_handler name="bpmui_handler" class ="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/workspace/Framework.log"/>
<property name="maxFileSize" value="10485760"/>
<property name="maxLogSize" value="52428800"/>
<property name="useSourceClassAndMethod" value="true"/>
</log_handler>
</log_handlers>
<loggers>
<logger name="oracle.bi.bifndnepm.workspace" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="workspace_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.workspace.config" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="workspace_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.workspace.prefs" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="workspace_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.workspace.security" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="workspace_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.bpmui" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="bpmui_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.bpmui.config" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="bpmui_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.bpmui.prefs" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="bpmui_handler"/>
</logger>
<logger name="oracle.bi.bifndnepm.bpmui.security" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="bpmui_handler"/>
</logger>
</loggers>
EPM Calculation Manager logging configuration
<log_handlers>
<log_handler name="calc-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/calc/CalcManager.log"/>
<property name="maxFileSize" value="1000000"/>
<property name="maxLogSize" value="5000000"/>
<property name="useSourceClassAndMethod" value="true"/>
</log_handler>
</log_handlers>
<loggers>
<!-- Logger levels: SEVERE,WARNING,INFO,CONFIG,FINE,FINER,FINEST,ALL -->
<logger name='oracle.bi.bifndnepm.calcmgr' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.common.GenericLogger' level='INFO' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.common.DefaultLogger' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.common.JSON' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.web.common.BaseAction' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.database.DBImport' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.provider.essbase.EssbaseProvider' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.provider.planning.PlanningProvider' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.provider.epma.DimensionServerService' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.core.CalcMgrSession' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.security.ObjectPrivilege' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.database.DBConnectionManager' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.net.HttpClientMessage' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.metadata.MetadataCache' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.beans.TemplateWizardHelper' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.beans.TemplateReferenceBean' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.beans.TemplatePrompt' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
<logger name='oracle.bi.bifndnepm.calcmgr.core.LCMManager' level='WARNING' useParentHandlers='false'>
<handler name='calc-handler'/>
</logger>
</loggers>
<log_handlers>
<log_handler name="css-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/css/css.log"/>
<property name="maxFileSize" value="1000000"/>
<property name="maxLogSize" value="5000000"/>
<property name="useSourceClassAndMethod" value="true"/>
</log_handler>
</log_handlers>
<loggers>
<logger name='oracle.EPMCSS' level='NOTIFICATION:32' useParentHandlers='false'>
<handler name='css-handler'/>
</logger>
</loggers>
EPM Financial Reporting logging configuration
<log_handlers>
<log_handler name="fr-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name='format' value='ODL-Text'/>
<property name='retentionPeriod' value='week'/>
<property name='path' value="${domain.home}/servers/${weblogic.Name}/logs/financialreporting/fr.log"/>
<property name="useThreadName" value="true"/>
<property name='rotationFrequency' value='daily'/>
<property name='useSourceClassAndMethod' value='true'/>
<property name="encoding" value="UTF-8"/>
</log_handler>
<log_handler name="epmhp-planning-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="${domain.home}/servers/${weblogic.Name}/logs/Planning_WebApp.log" />
<property name="rotationFrequency" value="daily"/>
<property name="retentionPeriod" value="week"/>
<property name="encoding" value="UTF-8" />
<property name="useSourceClassAndMethod" value="true" />
</log_handler>
</log_handlers>
<loggers>
<logger name="oracle.EPMFR" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="fr-handler"/>
</logger>
<logger name="oracle.EPMAnnotations" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="fr-handler"/>
</logger>
<logger name="oracle.EPMJCR" level="NOTIFICATION:1" useParentHandlers="false">
<handler name="fr-handler"/>
</logger>
<logger name="oracle.EPMADM" level="ERROR:1" useParentHandlers="false">
<handler name="fr-handler"/>
</logger>
<logger name='oracle.EPMADM.performance' level='OFF' useParentHandlers='false'>
<handler name='fr-handler'/>
</logger>
<logger level="NOTIFICATION:1" name="oracle.EPMHSP" useParentHandlers="false">
<handler name="epmhp-planning-handler" />
</logger>
</loggers>
For information about migrating an Essbase configuration between domains for an Oracle Enterprise Performance Management System installation, see "Moving Oracle Hyperion Enterprise Performance Management System to a Target Environment" in Oracle Fusion Middleware Administrator's Guide.
You monitor Essbase metrics using Fusion Middleware Control.
For more information, see Section 5.1, "Monitoring Service Levels."
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:
Oracle Business Intelligence and Essbase - When installed using the Oracle Business Intelligence installer, see "Backup and Recovery Recommendations for Oracle Essbase" in Oracle Fusion Middleware Administrator's Guide.
EPM System products - When installed using the EPM System Installer, see Oracle Enterprise Performance Management System Backup and Recovery Guide at:
http://www.oracle.com/technetwork/middleware/performance-management/documentation/index.html
This section introduces working with Essbase cubes in Oracle Business Intelligence:
Section 24.7.1, "Enabling Single Sign-On for Essbase Data Sources"
Section 24.7.3, "Enabling Oracle BI EE to Connect to Essbase Over SSL"
To enable SSO for Essbase data sources installed using the Oracle Business Intelligence installer, you select SSO in the General tab of the connection pool object that corresponds to the Essbase data source in the Oracle BI repository. Also select the Virtual Private Database option in the corresponding database object to protect cache entries.
For more information, see "Multidimensional Connection Pool Properties in the General Tab" in Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition.
Also see note 1993210.1 at:
A user with the BI Author application role can create, schedule, and run analyses and reports where Essbase is the data source, where filters are applied using the identity of the end user, and where SSO is configured.
For more information about:
Creating, scheduling, and running Oracle Business Intelligence analyses, see:
Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition
Creating and running BI Publisher reports, see:
Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Publisher
This section addresses how Oracle BI Server handles Essbase connectivity when both the Oracle BI Server and Essbase are installed and configured as part of the Oracle Business Intelligence.
If Essbase is configured for SSL, the BI Server (which uses the Essbase RTC client), must perform all the client side SSL configuration as an Essbase client.
If the BI Server and Essbase run on the same machine, and the Essbase server is configured for SSL, then the BI Server can simply point to the Essbase configuration file (essbase.cfg). To do this you add the ESSBASE_CONFIG_PATH property to obis.properties to specify the location of essbase.cfg.
If you need the Oracle BI Server to have a custom client side essbase.cfg (for example, to control specific Essbase client settings), but you do not want to use the Essbase server configuration file, then refer to the sections "Setting up an Essbase Client Wallet" and "Copying and Configuring the Wallet Path" in the 12c version of Essbase Database Administrator Guide. In this case, the obis.properties file must point to the directory location which contains essbase.cfg defined for the Oracle BI Server.
To make the BI Server to point to the essbase.cfg location:
Open the obis.properties file located here:
DOMAIN_HOME/config/fmwconfig/bienv/OBIS/obis.properties
Add the ESSBASE_CONFIG_PATH property with a value that either represents the path to location of essbase.cfg defined for Oracle BI EE, or the location that is already being used by Essbase Server.
For example, to point to the Essbase server's configuration file, then:
ESSBASE_CONFIG_PATH=DOMAIN_HOME/config/fmwconfig/biconfig/essbase
Save the obis.properties file.
Note:
End-to-End SSL configuration in 12.2.1.0.0 release is not supported. That is, if the Oracle BI Server is also configured for SSL, then connectivity between Oracle BI Server and the Essbase server will not work. However, this will be supported in a future release of 12c.Use the following links to learn more about Essbase in Oracle Enterprise Performance Management System.
For all Essbase and EPM documentation, use the Performance Management Documentation page:
http://www.oracle.com/technetwork/middleware/performance-management/documentation/index.html
This page also contains links to EPM System Supported Platform Matrices, My Oracle Support, and other information resources.
Drill down to view specific documents for a release.
For information about meeting system requirements and understanding release compatibility, use Oracle Enterprise Performance Management System Certification Matrix:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
When Essbase is installed as part of Oracle BI Enterprise Edition, refer to System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition for information about system requirements and release compatibility.