Optional Configuration for High Availability

The steps in this section describe how to perform optional configuration for high availability.

This section contains the following topics:

Set Optional Cluster Controller Parameters

You can set optional parameters that are related to Cluster Controller heartbeat frequency in the bi-cluster-config.xml file.

  1. Open the bi-cluster-config.xml file for editing at:

    BI_DOMAIN/config/fmwconfig/biconfig/OBICCS

  2. The following table describes default values for the cluster communication parameters under the ClusterProperties element. Optionally, modify the parameter values as required for the deployment.
    Use these cluster communication parameters in NQClusterConfig.INI.
    • ServerPollSeconds

      The frequency in seconds of heartbeat messages between the Cluster Controller and the Oracle BI Server and Oracle BI Scheduler nodes in the cluster. The default value is 5.

    • ControllerPollSeconds

      The frequency in seconds of heartbeat messages between the Cluster Controllers. The default value is 5.

  3. Save and close the file.
  4. Restart Oracle Analytics.

This code shows example parameters in the bi-cluster-config.xml file. Note that any additional elements that aren't shown in this example are centrally managed and can't be set manually.

<bi:ClusterProperties>
  <bi:ClusterEnabled>true</bi:ClusterEnabled>
  <bi:ServerPollSeconds>5</bi:ServerPollSeconds>
  <bi:ControllerPollSeconds>5</bi:ControllerPollSeconds>
</bi:ClusterProperties>

Set Optional Presentation Services Parameters

You can optionally configure certain parameters that control the communication between Presentation Services and the JavaHost component.

To configure Presentation Services, set parameters in the instanceconfig.xml file on each computer that hosts Presentation Services.

  1. Open the configuration file instanceconfig.xml for editing at:

    BI_DOMAIN/config/fmwconfig/biconfig/OBIPS

  2. Under the ServerInstance tag, the JavaHostProxy element has optional sub-elements. The following table describes these optional sub-elements.
    Subelement Attribute Description

    LoadBalancer/Ping

    keepAliveMaxFailures

    Specifies the number of ping failures required before the host is declared nonfunctioning. The default value is 5.

    LoadBalancer/Ping

    keepAliveFrequencySecs

    Specifies the ping frequency in seconds. The default value is 20.

  3. Save and close the file.
  4. Restart Oracle Analytics Server.

Set Optional Presentation Services Plug-in Parameters

You can optionally configure the Presentation Services Plug-in to control session redirection behavior.

  1. Open the bridgeconfig.properties file for editing, for example at:

    BI_DOMAIN/config/fmwconfig/biconfig/bridgconfig.properties

  2. Optionally, you can include the parameter AlwaysKeepSessionAffiliation to control whether requests that belong to the same session can be redirected to another Presentation Services component if the current Presentation Services Plug-in component score is too low.

    The instance score is an internal score that the load balancing algorithm associates with each Presentation Services Plug-in instance in the cluster. It's based on various metrics that are collected by the load balancer.

    Set this parameter to true to disallow request redirection, or false to allow requests to be redirected. For example:

    oracle.bi.presentation.sawconnect.loadbalance.AlwaysKeepSessionAffiliation=true
    
  3. Save and close the file.
  4. Restart the analytics application from the Oracle WebLogic Server Administration Console. If Presentation Services Plug-in is using the Presentation Catalog, then you must reastart the xmlpserver application.