Oracle^® Business Intelligence Enterprise Edition Deployment Guide > Clustering, Load Balancing, and Failover in Oracle Business Intelligence > Configuration of BI Components for Clustering, Load Balancing, and Failover >

Configuring BI Presentation Services

The BI Presentation Services component communicates with other BI components. To enable communication in a clustered deployment, BI Presentation Services must be configured to point to clustered instances of the other BI components.

BI Presentation Services must be configured to communicate with BI Scheduler instances via the Primary and Secondary Cluster Controllers. BI Presentation Services must also be configured to point to the Javahost cluster. In addition, BI Presentation Services must be configured to use the Presentation Catalog on the network share.

This configuration is done by setting parameters in the BI Presentation Services configuration file, instanceconfig.xml. This file is located in the following directory:

• Under Windows, OracleBIData_HOME\web\Config
• Under Linux or UNIX, OracleBIData_HOME/web/Config

The configuration must be done for all instances of BI Presentation Services in the BI deployment.

NOTE:  BI Presentation Services communicates with BI Servers via the BI ODBC Client Data Source. The BI ODBC Data Source must be configured to communicate with the Primary and Secondary Cluster Controllers as described in Modifying BI ODBC Data Sources For Communication With BI Cluster.

Communication with BI Scheduler

Communication with the clustered Scheduler instances occurs through the Cluster Controllers. The configuration file must identify the Primary Cluster Controller and Secondary Cluster Controller in the Alerts section of the instanceconfig.xml file:

<Alerts>
   <ScheduleServer
   ccsPrimary="<Primary Cluster Controller>"

ccsPrimaryPort="<CLIENT_CONTROLLER_PORT>" ccsSecondary="<Secondary Cluster Controller>" ccsSecondaryPort="<CLIENT_CONTROLLER_PORT>"/>

</Alerts>

• where:
• ccsPrimary is set to the Primary Cluster Controller machine identified by the PRIMARY_CONTROLLER parameter in the NQClusterConfig.INI file.
• ccsSecondary is set to the Secondary Cluster Controller machined identified by the SECONDARY_CONTROLLER parameter in the NQClusterConfig.INI file.
• ccsPrimaryPort and ccsSecondaryPort are set to the port identified in the CLIENT_CONTROLLER_PORT parameter in the NQClusterConfig.INI file. The default is 9706.

Communication with BI Javahost Cluster

The communication of BI Presentation Services with the Javahost cluster is enabled by identifying the Javahost instances and the listening ports in the instanceconfig.xml file. This is done by specifying the JavaHostProxy element and Hosts sub-elements. The Host element contains one or more Host sub-elements that identify specific instances of BI Javahost and port. If these elements are not set, BI Presentation Services will connect to a single Javahost on the default listening port on the local machine

<ServerInstance>

.
.
   <JavaHostProxy>

<Hosts>
   <Host address="<Javahost Machine1>" port="9810" />
   <Host address="<Javahost Machine2>" port="9810" />
</Hosts>

   </JavaHostProxy>
.
.
</ServerInstance>

The default Javahost port is 9810, and can be obtained from the Port element in the config.xml file on the machine where Javahost is installed. The config.xml file is located in the following directory:

• Under Windows, OracleBI_HOME\web\javahost\config
• Under Linux or UNIX, OracleBI_HOME/web/javahost/config

When two or more Host elements are uniquely identified, load balancing of requests to the Javahost cluster automatically takes effect.

The JavaHostProxy node has an optional element LoadBalancer that contains the sub-element Ping.

The following table shows the attributes of the LoadBalancer/Ping and Hosts/Host elements.

Identifying the Shared Presentation Catalog

If you are using a shared Presentation Catalog on a storage device, you must point BI Presentation Services to the shared location for the Presentation Catalog.

To identify the shared Presentation catalog

• Modify the <CatalogPath> element to point to the shared Presentation Catalog.

  For example:

  <CatalogPath>\\FS-HOST\OracleBIData\web\catalog\customCatalog</CatalogPath>

  where customCatalog is the name of the shared Presentation Catalog.

  When multiple BI Presentation Services instances are deployed, the following elements and their values must be specified in the isntanceconfig.xml file:

  <Catalog>
     AccountIndexRefreshSecs>120</AccountIndexRefreshSecs>
     <AccountCacheTimeoutSecs>180</AccountCacheTimeoutSecs>
     <CacheTimeoutSecs>120</CacheTimeoutSecs>
     <CacheCleanupSecs>600</CacheCleanupSecs>
     <PrivilegeCacheTimeoutSecs>180</PrivilegeCacheTimeoutSecs>
  </Catalog>

  NOTE:  The above settings manage when BI Presentation Services cache is updated from disk in environments with multiple BI Presentation Services instances.