Configuring BMC Server Automation for HA

Perform the following steps to configure BMC Server Automation for high availability (HA).

To configure BMC Server Automation servers behind a load balancer

1. Configure the load balancer as follows:
   1. Load balance port 10840 (the BL Authorization port) port on all the servers contributing to Multiple Application Servers (MAS).
   2. Load balance port 10841 (the BL Application service port) on all the servers contributing MAS.
   3. Load balance port 10843 (the https port used in the OSGI configuration) on all the servers contributing MAS.
2. Update the config server with the load balancer host name on each application server as follows:
   1. At the command prompt, type the following command:
      <NSH home>/br/blasadmin --s "config server name"
      The config server names to update are listed in the /br/deployments folder.
   2. If the IP address of the BMC Server Automation load balancer is not reachable from the primary and secondary BMC Server Automation computers, run the following command:
      set AuthServer AppServiceURLs service:appsvc.bladelogic:blsess://<Loadbalancer ip>:10841, service:appsvc.bladelogic:blsess://<BBSA Primary Server ip>:10841
   3. Execute the following commands from the BMC Server Automation Administration Console if Client request is sent using a VIP (since the load balancer network and the client network are not trusted for which a NAT group must be configured in the load balancer):
      set AppServer ValidateClientIpAddress false
set AppServer ValidateRequestURL false
   4. Restart both application servers.
3. Log on to the BMC Server Automation Console using the load balancer IP or host name.
4. Go to Configuration > Atrium Integration > Configuration and specify the Enterprise AR System server load balancer host name and port information.
5. Click Test connection button to verify that the integration connection is properly working.

_{Back to top}

To configure Oracle RAC

If you are using an Oracle Real Application Clusters (RAC) database on Linux, configure each server to replace the Primary node with the RAC server name. 

1. Stop the BladeLogic Application Server service on both the Primary and Secondary servers.

2. Open the global.properties file (located at <BladeLogic_Home>\NSH\br\deployments) and update the Oracle RAC details.
   For example:

   jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)
   (HOST = cdlrac01v)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)
   (HOST = cdlrac02v)(PORT = 1521))(LOAD_BALANCE = yes)
   (CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = CDL)
   (FAILOVER_MODE =(TYPE = SELECT)
   (METHOD = BASIC)(RETRIES = 180)(DELAY = 5))

3. Restart the BladeLogic Application Server service on both the Primary and Secondary servers.

_{Back to top}