Essbase clients can use a URL to connect to an Essbase cluster, in the form:
http(s)://host:port/aps/Essbase?ClusterName=clusterName&SecureMode=yesORno
To simplify login, Essbase clients should use the logical cluster name directly, in the form <name>:<secure>, instead of the URL. If you want to enable client login using the cluster name, you must first specify a property to configure Provider Services. The cluster name is resolved by the Provider Services servers specified in configuration files:
APSRESOLVER in essbase.cfg—Server-to-server communication; for example, when defining Essbase servers for partitions, XRefs, and XWrites
See Oracle Essbase Technical Reference.
aps.resolver.urls in essbase.properties—Client-to-server communication; for example, when connecting to Essbase from Spreadsheet Add-in or Smart View
See Oracle Hyperion Provider Services Administration Guide.
The Login API adheres to this precedence order when resolving the server name:
Look up the server name in the internal cache (maintained in the API layer).
If the server name is not found in the cache, contact each Provider Services server listed in essbase.cfg and attempt to resolve the server name.
If the server name is not found, treat the server name as a physical server name.