Configure Active-Active (Read-Only) Essbase Clusters

To provide high-availability and load balancing for cubes that are heavily used for query and reporting, you can create active-active (read-only) clusters of identical Essbase cubes belonging to multiple, independently deployed Essbase servers.

After you complete the configuration using a Provider Services utility, Smart View users will be able to access all the cluster nodes using one centralized Provider Services URL.

Using the Provider Services startAPScmd utility, you can create active-active (read-only) clusters of identical cubes belonging to multiple Essbase servers. The benefit of active-active clusters is to add high-availability and load balancing for cubes that are heavily used for query and reporting, but do not need to be updated frequently. An active-active cluster enables client requests to be distributed amongst the cubes in the cluster. Active-active clusters support only read operations on the cubes. You cannot update data or modify the outlines.

To set up and manage active-active (read-only) clusters,

1. Complete steps 1-3 in Access Multiple Essbase Servers Using a Centralized Smart View URL.

2. Configure and manage your read-only clusters using available commands.

   1. Enter help to see all the commands.

   2. Enter signon to connect to Provider Services. Provide the administrator user name and password. Enter the Provider Services (APS) URL, ending in /japi. OLAP Server name can be left blank.

      APS>signon
      Enter user name : admin
      Enter password :
      Enter APS URL : https://myhost.example.com:9001/essbase/japi
      Enter OLAP server name : 
      You are signed on.

   3. Enter createCluster to create a read-only cluster.

      APS>createCluster
      Enter input as cluster name, component names to be enabled (if multiple, separate the components with a ';')
      (eg- cluster1, host:port:secure/sample/basic;host:port:secure/sample2/basic2)
      ROcluster,myhost2.example.com:6423:secure/Sample/Basic;myhost3.example.com:6424:secure/Sample/Basic
      The cluster is created

   4. Enter listClusters to list all read-only clusters by name.

      APS>listClusters
      ROcluster

   5. Enter getCluster to list the read-only cluster nodes and their current state.

      APS>getCluster
      Enter input as clusterName
      (Eg: demoBasicCluster):
      ROcluster
      Name: ROcluster
      Description:
      Service comp names: myhost2.example.com:6423:secure/Sample/Basic;myhost3.example.com:6424:secure/Sample/Basic
      Comp State: (0-BAD,1-GOOD,2-DISABLED)
              myhost2.example.com:6423:secure/Sample/Basic 1
              myhost3.example.com:6424:secure/Sample/Basic 2

   6. Enter enableCluster to enable a read-only cluster from a disabled state.

      APS>enableCluster
      Enter input as cluster name, component name to be enabled
      (eg- cluster1, host:port/sample/basic)
      ROcluster,myhost3.example.com:6424:secure/Sample/Basic
      The cluster component is enabled

   7. Enter disableCluster to disable a read-only cluster that is currently enabled.

      APS>disableCluster
      Enter input as cluster name, component name to be disabled
      (eg- cluster1, host:port/sample/basic)
      ROcluster,myhost3.example.com:6424:secure/Sample/Basic
      The cluster component is disabled

   8. Enter updateCluster to update a read-only cluster definition.

      APS>updateCluster
      Enter input as cluster name, component names to update (if multiple, separate the components with a ';')
      (eg- cluster1, host:port/sample/basic;host:port/sample2/basic2)
      ROcluster,myhost3.example.com:6424:secure/Sample/Basic
      The cluster component is updated

   9. Enter removeCluster to remove a read-only cluster by name.

      APS>removeCluster
      Enter input as cluster name to be removed
      (eg- cluster1)
      ROcluster
      The cluster is removed

   10. Enter signoff to sign out, and then exit to exit the utility.