I have long used Oracle Essbase's JAPI (HAS/EDS/APS) to query and push data and metadata to Essbase. All our code typically runs in JBoss 4.x (other app servers tested as well) however I recently decided to upgrade to JBoss 6. I have finally solved almost everything with a couple of exceptions. I had all the typical spring/hibernate/cxf issues. I felt these links helped the most with those issues.
CXF/Spring/Hibernate in JBoss 6
JAXB Issue
But my last issue is quite obscure because you have to use special jars from Oracle to connect to Essbase. As of Essbase @11.1.x.x their came some new required jars to connect to Essbase when using embedded mode (ojdl.jar and theoretically cpld.jar). Up until the 11.1.2 release we had to use external APS mode due to some bugs in the implementation of saves when run in embedded mode. They were fixed as of 11.1.2 however so we switched to embedded mode for a variety of reasons. It worked in a fairly straight forward way by adding the relevant jars, until I upgraded to JBoss 6.
In JBoss 6 their seems to be a new logging framework being used that extends or wraps log4j. I get an error along the lines of ...
java.lang.ClassCastException: org.jboss.logmanager.Logger cannot be cast to oracle.core.ojdl.logging.ODLLogger@at oracle.core.ojdl.logging.ODLLogger.getODLLogger(ODLLogger.java:102)at com.hyperion.dsf.server.framework.BaseLogger.(Unknown Source) at com.hyperion.dsf.server.framework.DsfLoggingService.sm_initialize(Unknown Source)at com.essbase.server.framework.EssOrbPluginDirect.setupLoggingService(Unknown Source)at com.essbase.server.framework.EssServerFramework.(Unknown Source) Why this happens in embedded mode and not external mode is a mystery to me.
To see it in JBoss 6 and not 4 says classloading, but any attempts at isolating the app via jboss-classloading.xml only produces a different exception in the same spot.
java.lang.NullPointerException@at com.essbase.api.session.EssbaseProperties.(Unknown Source) at com.essbase.api.session.EssbaseProperties.getInstance(Unknown Source)at com.essbase.api.session.Essbase.(Unknown Source) at com.essbase.api.session.IEssbase$Home.create(Unknown Source)
I've stuck the Essbase jars in every directory you can imagine (/lib /lib/endorsed, /common/lib/endorsed, /profile/lib / profile/lib/endorsed)
I think it might come down to an essbase.properties file, a logging.xml file or the existence of a /data/domain.db file, all of wich are available in external mode on the APS server but not in embedded mode, but again why was none of that required in JBoss 4 vs 6
So that's where I'm at, I'm publishing this in the interest of hearing any ideas. I will solve it at which point I'll edit this post to reflect the right answer.
