Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Implementing high availability and load balancing for the reports server

Most enterprises have requirements for documenting and testing the ability of their infrastructure to sustain loss at various levels. These levels can range from the loss of a server to the loss of the physical infrastructure of an entire data center. This topic provides steps for deploying the BMC BladeLogic Decision Support for Server Automation system in highly available and load balancing configurations.

Complete the following steps to implement high availability and load balancing

  1.  Install BMC BladeLogic Decision Support for Server Automation on one computer, called Server1.
  2. Perform one of the following tasks:

    • Clone Server1 and name it Server2.

      Note

       After cloning, make sure that the IP address conflict has been resolved.

    • Back up various entities on Server1 and Install BMC BladeLogic Decision Support for Server Automation on another computer, called Server2, as follows:
      1. Back up following entities on Server1:
        • Entire Cognos Content Store
        • All objects under Public Folders

        • Content under My Folders if required

          Note

          When you install BMC BladeLogic Decision Support for Server Automation in step (ii), the ant installation script cleans up the Cognos Content Store. So, this backup can be used to restore the Content Store on Server2.

        • ETL Master and Work repositories
      2. Install BMC BladeLogic Decision Support for Server Automation on Server2 and point it to use the same databases to which Server1 points.
  2. Log on to Server1 and stop the Cognos services.
  3. Open IBM Cognos Configuration.
  4. In the left pane, navigate to Local Configuration > Environment.
  5. Under Gateway Settings, double-click Dispatcher URIs for gateway.
  6. Add Server2 details as an additional dispatcher, as shown in the following screenshot:
    HA1.png
  7. Under Gateway Settings, double-click Controller URI for gateway.
  8. Add Server2 details as an additional controller.
  9. Under Other URI Settings, double-click Content Manager URIs.
  10. Add Server2 details as an additional Content Manager.
  11. Save the configuration and start Cognos services.
  12. Log on to Server2 and stop the Cognos services.
  13. Open Cognos Configuration.
  14. If you created Server2 by cloning Server1, under Gateway Settings and Other URI Settings, change all the references of Server1 to Server2.
  15. Add Server1 details as described in step 7 through step 10.

  16. Disable Metadata Service on the secondary server. Due to a defect in Cognos version 8.4.1, you must perform this step so that the 4_UPDATE_COGNOS step is completed successfully during an ETL run.

    Note

    Due to some reason, if Server1 has failed or is down and only Server2 is working, enable Metadata Service on Server2 to run the ETL successfully.

  17. Save the configuration and start the Cognos services.
    Your environment is ready for high availability and load balancing.

    Note

    Ensure that a router exists that directs all the requests to a server that is immediately available (Server1 or Server2).

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*