|gerdpee on Dimension does not contain any…|
|jasmine on Dimension does not contain any…|
|gerdpee on Oracle WebLogic and Hyperion S…|
|OBIEEfan on Oracle WebLogic and Hyperion S…|
Stuff about Hyperion and stuff
This time the requirement is to drill from any level in the hierarchy to transactions (a bit too much, right?). It’s a bit difficult to use OBIEE federation to do this which means a custom solution is required. Anyhow, I found an excellent post about this here.
So I’ve decided to follow the steps and write my own JSP page to manage the HTTP post request. Most of the steps worked like a charm except for the JSP deployment step since the WebLogic version I’m on requires a WAR file. To build a WAR file, a Java compiler (javac) is required and I was too lazy to install one. Luckily, WebLogic works with a directory structure to build a WAR file.
Follow these easy steps:
Create web application folder structure
<web-app> <display-name>Drillthrough</display-name> </web-app>
Deploy to Web Logic
We were puzzled the other day by the spikes in memory usage on our Essbase (AIX) server. This happened after we deployed an additional historical ASO cube. It seemed odd since the memory usage (Paging Space) of this particular application kept increasing with each user request. At point it got up to several hundred MBs. The first place we looked was the ASO cache limit which was set to 32 MB (default). After some trial and error, it turned out that all data files were stored on the default location at $HYPERION_HOME/products/EssbaseServer/app/APP/APP. So I changed this and point the data fil