Recommendations for Configuring Essbase Middleware

SAP COMMUNITY NETWORK scn.sap.com

2013 SAP AG 1

Recommendations for configuring

Essbase middleware

Applies to:

SAP BusinessObjects Business Intelligence platform 4.0 Feature Pack 3.

Summary

You need to configure your environment to be able to use Essbase data source version 11.1.2.1 and higher with the BI platform. This document covers four specific system configurations, including BI platform Client Tools on 32-bit MS Windows, 64-bit MS Windows and 64-bit Linux machines, and BI platform server on a 64-bit MS Windows machine.

Author: Frederic MOITEL

Company: SAP

Created on: 1 February 2012

Author Bio

Information Developer at SAP

Recommendations for configuring Essbase middleware


2013 SAP AG 2

Table of Contents

BIP Client Tools on 32-bit MS Windows ............................................................................................................. 3

Result .............................................................................................................................................................. 3

BIP Server on 64-bit MS Windows ..................................................................................................................... 3

Result .............................................................................................................................................................. 4

Important ......................................................................................................................................................... 4

BIP Client Tools on 64-bit MS Windows ............................................................................................................. 4

Result .............................................................................................................................................................. 4

Important ......................................................................................................................................................... 5

BIP Client Tools on 64-bit Linux ......................................................................................................................... 5

Result .............................................................................................................................................................. 5

Important ......................................................................................................................................................... 5

Related Content .................................................................................................................................................. 6



2013 SAP AG 3

BIP Client Tools on 32-bit MS Windows

1. Install Oracle Enterprise Performance Management (EPM) System 11.1.2.1 and select Essbase/Essbase Client during installation.

2. Install the BIP Client Tools.

3. Set the following environment variables:

o ESSBASEPATH=%EPM_ORACLE_HOME%\common\EssbaseRTC\11.1.2.0

o PATH=%EPM_ORACLE_HOME%\bin;%EPM_ORACLE_HOME%\common\EssbaseRTC\11.1.2.0\bin;%PATH%

4. Copy the 3 following JAR files from the Oracle Essbase client installation directory to the java\lib

BIP installation directory. This ensures that hierarchy levels are determined spontaneously in the Query Panel and can be selected in the query.

o %EPM_ORACLE_HOME%\_vpddb\Gen1\engine\1.0\library\ojdl.jar

o %EPM_ORACLE_HOME%\common\EssbaseJavaAPI\11.1.2.0\lib\ess_japi.jar

o %EPM_ORACLE_HOME%\common\EssbaseJavaAPI\11.1.2.0\lib\ess_es_server.jar

Note: You do not need to copy the files if you are using the information design tool only.

Result

In this configuration, you can run a query:

on a .unx universe on Oracle Essbase 11 in the information design tool (hierarchy levels are

determined spontaneously)

on a .unx universe on Oracle Essbase 11 in Web Intelligence Rich Client (hierarchy levels are


on a .unv universe on Oracle Essbase 11 in Web Intelligence Rich Client

BIP Server on 64-bit MS Windows

1. Install Oracle EPM System 11.1.2.1 and select Essbase/Essbase Client during installation.

2. Install the BIP server.


o ESSBASEPATH=%EPM_ORACLE_HOME%\common\EssbaseRTC-64\11.1.2.0

o PATH=%EPM_ORACLE_HOME%\bin;%EPM_ORACLE_HOME%\common\EssbaseRTC-64\11.1.2.0\bin;%PATH%

Note: [Oracle identified the path conflict issue and fixed it in 11.1.2.2 according to readme 12665494.] The

Essbase bin path must be added at the beginning of the PATH environment variable, because the Oracle client

installed can interfere with the Oracle Essbase 11 client installation directory. If you have not installed the

Oracle client on the machine, the bin path can be added at the end of PATH.


BIP server installation directory. This ensures that hierarchy levels are determined spontaneously in the Query Panel and can be selected in the query.




2013 SAP AG 4




Result

In this configuration, you can run a query on .unx universes on Oracle Essbase 11 in the BI launch pad.

You cannot run a query on .unv universes on Oracle Essbase 11 in the BI launch pad, because the 32-bit

Connection Server is used when accessing .unv universes.

Important

If the BIP Client Tools are also installed in this configuration, you can run a query on a .unx universe in the

information design tool, but not on a .unv or .unx universe in Web Intelligence Rich Client. To be able to

use them in Web Intelligence, configure the system with two clusters on two separate machines. See Essbase connections, in the Data Access Guide.

BIP Client Tools on 64-bit MS Windows




o ESSBASEPATH=%EPM_ORACLE_HOME%\common\EssbaseRTC\11.1.2.0

o PATH=%EPM_ORACLE_HOME%\bin-32;%EPM_ORACLE_HOME%\common\EssbaseRTC\11.1.2.0\bin;%PATH%

Note: [Oracle identified the path conflict issue and fixed it in 11.1.2.2 according to readme 12665494.] The

Essbase bin path must be added at the beginning of the PATH environment variable, because the Oracle client

installed can interfere with the Oracle Essbase 11 client installation directory. If you have not installed the

Oracle client on the machine, the bin path can be added at the end of PATH.


BIP Client Tools installation directory. This ensures that hierarchy levels are determined spontaneously in the Query Panel and can be selected in the query.





Result


on a .unx universe on Oracle Essbase 11 in the information design tool

on a .unx universe on Oracle Essbase 11 in Web Intelligence Rich Client



2013 SAP AG 5

on a .unv universe on Oracle Essbase 11 in Web Intelligence Rich Client (hierarchy levels are


Important

If a BIP server is also installed in this configuration, you can run a query on .unv universes on Oracle

Essbase 11 in the BI launch pad, but not on .unx universes. To be able to use them, configure the system

with two clusters on two separate machines. See Essbase connections, in the Data Access Guide.

BIP Client Tools on 64-bit Linux




o ESSBASEPATH=%EPM_ORACLE_HOME%\common\EssbaseRTC-64\11.1.2.0

o LD-LIBRARY-PATH=$LD-LIBRARY-PATH:$/lib:$EPM_ORACLE_HOME/common/EssbaseRTC-64/11.1.2.0/bin export LD-LIBRARY-PATH

o PATH=$PATH:$EPM_ORACLE_HOME/lib:$EPM_ORACLE_HOME/common/EssbaseRTC-64/11.1.2.0/bin

export PATH


BIP Client Tools installation directory. This ensures that hierarchy levels are determined spontaneously in the Query Panel and can be selected in the query.





Result


on a .unx universe on Oracle Essbase 11 in the information design tool

on a .unx universe on Oracle Essbase 11 in Web Intelligence Rich Client

on a .unv universe on Oracle Essbase 11 in Web Intelligence Rich Client

Important

If a BIP server is installed in this configuration, you can run a query on .unv universes on Oracle Essbase

11 in the Bi launch pad, but not on .unx universes. To be able to use them, configure the system with two

clusters on two separate machines. See Essbase connections, in the Data Access Guide.



2013 SAP AG 6

Related Content

SAP BusinessObjects BI Platform Installation Guide

SAP BusinessObjects BI platform Administrator Guide

Data Access Guide

Information Design Tool User Guide



2013 SAP AG 7

Copyright

Copyright 2013 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Oracle Corporation.

JavaScript is a registered trademark of Oracle Corporation, used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Recommendations for Configuring Essbase Middleware

Documents

Transcript of Recommendations for Configuring Essbase Middleware