So I'm too busy to care anymore about other blogging platforms. I looked at them, they all have some cool features. Given the preponderance of great Essbase and technical blogs on Blogger I was actually inclined to go somewhere else, it's probably my counterproductive instinct to be different. But I like Google, I like their vision, and their relentless investment in science and technology, often just for the sake of science and technology. That's as good a reason as any for me to pick a platform as opposed to "feature x" that can easily be implemented by someone else if they think it important.
And of course the point of a blog is the content, not that mine has anything meaningful to say, but worrying about a particular editing feature is truly the height of technical preoccupation.
Friday, September 28, 2012
JBoss 7 AS and Essbase APS Embedded mode
Wow,
Well 1 year later (or so), here is the solution. Kudos to Iris for finding this out and to Oracle for actually fixing something I cared about. As you might notice from previous notes, upgrading to any JBoss application server after 4 (5-7.2) broke our products ability to to connect to Essbase using an APS server in embedded mode. That's an incredibly esoteric expectation, so if you're here I expect you know what I mean, if you don't, move along it doesn't matter.
The solution ultimately was to use the ojdl.jar library from the Essbase 11.1.2.2 release. No previous release works (AFAIK) but the way the logging library cast failed no longer occurs.
So that's it...get your latest ojdl.jar and you're back in business. We continue to find embedded mode the way to go for intense Essbase communication problems. Having said that, a 64bit instance of APS as available in 11.1.2.0+ should have the same capability as embedded mode when deployed in a modern (6/7) 64bit JDK.
Well 1 year later (or so), here is the solution. Kudos to Iris for finding this out and to Oracle for actually fixing something I cared about. As you might notice from previous notes, upgrading to any JBoss application server after 4 (5-7.2) broke our products ability to to connect to Essbase using an APS server in embedded mode. That's an incredibly esoteric expectation, so if you're here I expect you know what I mean, if you don't, move along it doesn't matter.
The solution ultimately was to use the ojdl.jar library from the Essbase 11.1.2.2 release. No previous release works (AFAIK) but the way the logging library cast failed no longer occurs.
So that's it...get your latest ojdl.jar and you're back in business. We continue to find embedded mode the way to go for intense Essbase communication problems. Having said that, a 64bit instance of APS as available in 11.1.2.0+ should have the same capability as embedded mode when deployed in a modern (6/7) 64bit JDK.
Subscribe to:
Posts (Atom)