Running Essbase in a foreground window aka what oh what version is Essbase?I am using John Booth’s excellent (and free) Amazon Web Services Planning AMI, and wanted to move to Smart View 184.108.40.206.102 (.103, actually) so I could get all of the goodies that come with the Smart View and of course get a copy of Smart View that finally looks like the Classic add-in. It’s like a time machine to 1994, only I have more grey hairs. Bummer about the last bit, but hooray for Smart View finally (I am talking about the below interface, btw) adopting the everything-on-the-grid look:
Given all of the really nice functionality Smart View has with Planning, I can finally start to move away from the Classic Add-In. About time.
What must be patchedThere are three components that need to be patched to the .102 level: Essbase, Application Proivider Services, and Smart View itself. Going backwards, Smart View is dead easy – it’s a simple case of installing it over whatever you already have. But Essbase and APS must be patched. The thing is, I didn’t know if John had already patched them on his AMI or not. How to to tell?
NB – I am not going to cover figuring out APS as figuring out Essbase was adventure enough. I’ll cover APS when I show how to use OPatch in a future post.
In days of yoreEssbase used to default to running in a Window. Ah yes, the halcyon days of Windows NT. This was also back when Essbase came on a CD, and all it took to look like a pro was to know that typing essbase.exe –service install made Essbase run as a service. Days long past.
Today, Essbase only runs as a service. So what you say? Well, how do you know what release of Essbase you are running? Oh, you can open up a MaxL window from the Start menu, and type display system version ;, but that isn’t going to give you detailed information.
When I stated that I just couldn’t figure out how run Essbase in a foreground window (a feature of every version of Essbase up to and including 220.127.116.11 but not in 18.104.22.168), MMIC, who, sad but true, is immeasurably smarter than me, emailed me:
“To run Essbase in fore ground, modify the startessbase.bat file (or is it cmd file) and change it to just run the essbase.exe. I had to do it for a client, but cant (sic) get to the server to look at it from this client arrrrg”
Well, the sad news is that as of 22.214.171.124 there is no startEssbase.bat. Actually, scratch that, there are four versions of startEssbase.bat, but none of them are designed to start Essbase as foreground window. OPMN rules over all. Read about it all here in Oracle Support document Starting and Stopping the Essbase Server 11.1.2 using OPMN [ID 1114453.1].
Here are the four instances of startEssbase.bat:
So how the he-double tootpicks do I run essbase.exe in a foreground window?I like to subscribe to the Infinite Monkey Theorem because when it comes to anything infrastructure-related nowadays, I am most definitely ape-like. After a frankly embarassing amount of searching, guessing, cursing (I am keeping this oh so safe for work so just use your imagination), it finally hit me that starting Essbase was sort of like starting the MaxL shell. And so it was.
The contents of startMaxL.batWhen I examined C:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\startMaxL.bat I saw:
@REM This file is created to startMaxl
rem Set ESSBASEPATH
I thought to myself, “Self, what happens if you changed essmsh.exe to essbase.exe?” I did a Save As from Notepad and called the new file EssbaseInAWindow.bat. Here’s the contents:
@REM This file is created to Essbase in a foreground window
rem Set ESSBASEPATH
And what do we see?
And lookie-lookie, right after the Single Sign-On Initialization succeeded:
What, it was in front of me all the time?Remember that MaxL window up above? The one that doesn’t show 126.96.36.199.102 as the version? Well, it all depends on what startMaxL you’re running (at least on my box). Why? Regardez-vous C:\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\bin\startMaxL.cmd’s output:
FWIW, now that you’re done with your mocking laughter (oh, I can hear it all too well, just like ol’ Charlie Brown), why exactly are the seven versions of startMaxL? And to make it fun, why are some templates, some .cmd files and others .bat? Beats me. Looks like I picked the wrong one to see the version. In my defense, the instance of startMaxL.cmd is the one that launches from the Start menu. Sigh.
NB – Smarter minds: please send me an email/write a comment to this post so my feeble brain can comprehend the madness that is startMaxL.
ConclusionWell, that was an interesting trip into the bowels of EPM 188.8.131.52. We’ve learnt a bunch of things:
- 184.108.40.206 really doesn’t want you to run Essbase as a foreground window. For production and probably even test reasons, this is a Good Thing.
- Running 220.127.116.11 as a foreground window is possible, if you are stubborn/stupid enough to persist in figuring out/stumbling upon the answer.
- There are four valid ways to launch MaxL, two of which will give you the right version number, but neither of these .bat files are opened from the Start menu. Why?
- You can get the version from the Essbase foreground window if you do a wee bit of code modification.
- Yr. Obdnt. Srvnt. should probably not muck about in infrastructure-related tasks.
- Figuring this out was a pretty cool Essbase hack.