This is a bit of a repost with respect to content as I’ve already talked about installing Essbase Java API JAR files into a local Maven repo. The other day I installed the newest JAR files for 126.96.36.199 and thought I’d do a quick post. There doesn’t seem to be a “CPLD” JAR anymore – I’m not totally sure what it did but some googling awhile back suggested we don’t need it anymore. So that leaves the main JAPI JAR and the server JAR:
I’ve renamed them as thus:
Then the following two Maven commands:
mvn install:install-file -Dfile=essbase-japi-188.8.131.52.jar -DgroupId=com.essbase -DartifactId=essbase-japi -Dversion=184.108.40.206 -Dpackaging=jar
A whole ton of output will show – hopefully some version of a sucesss message. And then this:
mvn install:install-file -Dfile=essbase-es-server-220.127.116.11.jar -DgroupId=com.essbase -DartifactId=essbase-es-server -Dversion=18.104.22.168 -Dpackaging=jar
And again a bunch of output. If you use Eclipse like I do then you might want/need to rebuild your local Maven repository index so they are picked up there, then you can add them via the GUI if you’re so inclined by just filtering on “essbase”. Add them both to your project and then go from there. You might need some other dependencies for the new Oracle Diagnostic Logging (ODL) which seems to have been implemented. I haven’t played with this much but it seems to depend on the version of the server you use. I typically use SLF4J and bridge the Essbase JAPI logger, but with ODL things might have changed a bit. I’ll post an article at some point hopefully discussing a resolution. If you bump into any issues or solutions please let me know.