Enabling Client Lookup by Cluster Name

Essbase clients can use a URL to connect to an Essbase cluster, in the form: http(s)://host:port/essbase/agent?ClusterName=clusterName. To simplify login, Essbase clients can use the cluster name directly instead of the URL.

Designating a Specific Installation of JRE for use with Essbase

To designate a specific installation of JRE for use with Essbase, update the JVMMODULELOCATION setting in essbase.cfg.

The JVMMODULELOCATION setting in the essbase.cfg file (in ARBORPATH/bin) enables you to designate a specific installation of JRE for use with Essbase, and is required to enable Data Mining, Oracle Hyperion Shared Services, custom defined functions, triggers, and external authentication.

This setting is particularly useful if you have multiple versions of Java installed on the Essbase Server computer.

During Essbase Server configuration, the correct setting for JVMMODULELOCATION is automatically added to essbase.cfg.

To change the JVMMODULELOCATION parameters, you must specify the full path and file name of the Java Virtual Machine (JVM) library. The location and name of the library varies, depending on the operating system that you are using. EPM System Installer installs JRE in /1.8.0_181/jre.

Managing Memory with JvmModuleLocation

If you are not using Data Mining, Shared Services, custom defined functions, triggers, or external authentication, you can reduce the amount of memory used by editing essbase.cfg and setting JvmModuleLocation to null (empty).

If you are using these features, and need to reduce the amount of memory used, then you can reduce the JVM heap size by setting the following environment variables:

ESS_JVM_OPTION1=-Xmx16m

Because the default minimum and maximum for JVM heap size are different for different platforms and versions, set the correct value for your environment.