Implementing High Availability, Failover, and Load Management


This chapter outlines best practices for creating systems that are robust and reliable to meet Service Level Agreements.

A summary of best practices in this chapter include:

  • Consider implementing both hardware and WebFOCUS application high availability and failover measures for minimal downtime. Enable session affinity on the load balancer, if it is being used.
  • Leverage WebFOCUS Reporting Server Data Services to identify the source of the request and also to manage throughput.
  • Use a cluster of JSCOMs for Java Services.
  • Use CLM for both WebFOCUS Client and ReportCaster to provide high availability, failover, and load management.
  • Use a cluster of CLMs to provide high availability and failover. If one CLM becomes unavailable, the remaining CLMs will continue processing requests.
  • Use the Smart CLM dispatch algorithm for all Remote Servers, unless there is a need for individual Remote Servers to use a different dispatch algorithm.
  • Configure ReportCaster to use all available Client, Cluster, and CLM processing nodes defined on the WebFOCUS Client.
  • Configure the Primary ReportCaster Distribution Server completely, then validate on the Failover ReportCaster Distribution Server to ensure that the configuration is in effect.
  • Increase capacity of remaining cluster members or add additional cluster members when system is operating at reduced capacity due to unavailability of one or more cluster members.

Information Builders