Calling Groovy code (like Java) is already possible via CDF and new CDF's make it even easier to call Groovy script without the need to register and re-deploy new jar files to the Essbase server.
I've been following Celvin Kattookaran series on using Groovy in PBCS on On-Premises. In Celvin's most recent post in this series,
he talks about a new script type that is coming soon to Calc Manager: Groovy Script. See: Groovy in PBCS and On-Premises Hyperion Planning - Part IV, It's Groovy time ~ Oracle - Hyperion Labs
This new feature will allow you to create Groovy scripts directly in Calc Manager without the need for CDF's. Pretty cool. We'll it seems that this new feature has
UNOFFICALLY / PARTIALLY made it's way into EPBCS 17.05 (latest drop as of this posting).
I've been playing around with some of the cool new functionality in EPBCS 17.05 and I've noticed a few of the delivered
Calc Manager scripts are already using this cool new feature. If you happen to be on the most recent
of EPBCS check out the following Calc Mgr scripts:
OPF_Execute Project to Capex Map Reporting - Capitalized (a rule in the OPF_Push data to Capex from Projects ruleset).
OPF_Add Project (a custom script template).
These Calc Manager scripts are pure Groovy script. There's only one problem. There doesn't seem to be a way to set the
script type yet. I can only assume that this new feature hasn't "officially" been released for public consumption. If anyone
has any more info, please update this discussion thread.
Both of the above Calc Manager scripts also reference a new groovy package called: EPMApplicationShell. Among other things,
this new package allows you to invoke planning utilities (i.e. PushData() ). This package also has a few nifty methods like:
doesMemberExist(); createChildMember(); and saveMember() which allow you to dynamically manipulate dynamic members
in the planning outline. Couldn't find any documentation on this new package (so there are probably a boat load of
nifty methods available). I assume this package is also not officially released yet or it may be just for internal use by EPBCS.
The need to incorporate a dynamic script language like groovy really makes sense in the context of EPBCS which must now support a
dynamic user configurable planning application. The new approach in EPBCS for delivering "user configurable" planning content is
a huge improvement over the prior solution which required the user to make all of their configuration decisions upfront at application create
time.