How can we run a Business Rule against an Essbase location using the Essbase cluster name (“EssbaseCluster-1” by default) rather than the name of a particular Essbase server? This does not work in the EAS console or from the command line.
When using the CmdLnLauncher.bat utility to launch a rule from the command line we receive an error:
com.hyperion.hbr.excp.ExceptionAdapter: Error generating calc script: 01_BR_KM_CalcFXRate_Budget_4
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at com.hyperion.hbr.common.Util.getExcpAdapter(Unknown Source)
at com.hyperion.hbr.core.LanguageManagerServerRemote.generateExecutable(Unknown Source)
at com.hyperion.hbr.api.LanguageManagerClient.generateExecutable(Unknown Source)
at com.hyperion.hbr.cmdlnlauncher.LaunchManager.launchRule(Unknown Source)
at com.hyperion.hbr.cmdlnlauncher.CmdLineLauncher.main(Unknown Source)
Detail:Error connecting to Essbase server EssbaseCluster-1.
Detail:Exception occurred. Please check your log file for details.
Error generating calc script: 01_BR_KM_CalcFXRate_Budget_4
2012-02-16 17:56:33,506 WARN main com.hyperion.hbr.cmdlnlauncher.CmdLineLauncher – Error generating calc script: 01_BR_KM_CalcFXRate_Budget_4
The “EssbaseCluster-1” cluster name is not being resolved correctly. How can this be addressed?
To use the cluster name (rather than an individual Essbase server name) as a location when launching Business Rules from the EAS console or the CmdLnLauncher, you first need to create an essbase.properties file (or edit it if it already exists) so that the “EssbaseCluster-1” name can be resolved successfully.
- Create a new text file called “essbase.properties” on the EAS server in the following location:
(If the file already exists, edit it)
- Add the following line in this file:
(Replace “vm0dacarter61” with the name of the server where Hyperion Provider Services is running. If you are using a non-standard port amend as appropriate)
- Restart the EAS service
- Ensure that the Hyperion Provider Services service is running. Since the essbase.properties file directs EAS to contact Provider Services to resolve the cluster name, Provider Services must be running for this to work.
This solution is also documented in the 126.96.36.199 Business Rules readme: http://docs.oracle.com/cd/E17236_01/epm.1112/hbr_1112100_readme.pdf