With the aim to provide a fabulous integration between Oracle BI/EPM, i.e.: OBIEE and Oracle Essbase / HFM , etc Oracle has made some wonderful strides. OBIEE 11g is a testament to that integration’s roadmap. This post is all about just getting OBIEE 11g configured for interaction with Oracle Hyperion Essbase as close to right out of the box as possible. Although the Essbase integration doesn’t completely work directly OOTB, Oracle has at least set the stage for the infrastructure. What do I mean by that? Let me explain.
OOTB the Oracle BI 11g instance already installs/contains the following items for integration with Oracle Essbase 11.1.2:
- Essbase JAPI files
- Essbase C API files
What is missing for this OOTB Oracle Essbase integration is:
- Configuration of PATH variables pointing to the location of the Essbase API files
- Configuration of the Administration Tool to know where to point for the Essbase API files
- Oracle BI Server (now managed by OPMN) to know where to point to the Essbase API files
- Actually this is done OOTB but one will want to confirm the location is indeed set propertly
- This has to do with the machine where the OBI Server itself is installed and is not an issue if just running the OBIEE 11g Client Tools




