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.
To implement high availability and load balancing
- Install BMC BladeLogic Decision Support for Server Automation on one computer, called Server1.
- Perform one of the following tasks:
Clone Server1 and name it Server2.
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:
- Back up the following entities on Server1:
- Entire Cognos Content Store
- All objects under Public Folders
Content under My Folders if required
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
Log on to Server1 and stop the Cognos services.
Open IBM Cognos Configuration.
In the left pane, navigate to Local Configuration > Environment.
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.
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.
Save the configuration and start the Cognos services.
Your environment is ready for high availability and load balancing.
Ensure that a router exists that directs all the requests to a server that is immediately available (Server1 or Server2).