Specifies the Oracle Hyperion Provider Services server to use for name resolution, which enables connections to be made using logical Essbase cluster names.
APSRESOLVER APSurl[;APSurl]Where APSurl is the URL to a Provider Services server, in this format:
http[s]://host:port/contextRootThis configuration setting enables the use of logical Essbase cluster names instead of the Essbase URL (for example, http[s]://host:port/aps/Essbase?ClusterName=logicalName&Secure= yesORno) during the login process.
When logging in to an Essbase Server, if the server name specified is not a URL, the Essbase client treats the name as a logical name. The Provider Services server specified in APSRESOLVER then resolves the logical name to a physical host.
Multiple URLs can be given, delimited by semicolons
Use https:// for SSL
The logical name must be of the form name:secure.
If Provider Services cannot resolve the logical name, the name is treated as a physical name.
On successful resolution of the logical name of a standalone Essbase Server, the mapping is cached for 5 minutes (not configurable). Subsequent attempts to log in on the same API handle are resolved by the cache. After 5 minutes, the cache entry is discarded and Oracle Hyperion Provider Services is used to resolve the logical name.
This setting applies only for server-to-server communication (Essbase and C API). For client-to-server communication (Java API), use the essbase.properties file. See the Oracle Hyperion Provider Services Administration Guide and the Oracle Hyperion Enterprise Performance Management System High Availability and Disaster Recovery Guide.
http://qtfsvr1:1234/aps http://qtfsvr1:1234/aps;http://qtfsvr2:1234/aps https://qtfsvr1:1234/aps https://qtfsvr1:1234/aps;http://qtfsvr2:1234/aps