Configuring multiple Application Servers on different hosts

This topic describes how to set up a multiple Application Server environment, with the Application Servers residing on different hosts.

To configure the Application Servers on different hosts

To configure multiple Application Servers on different physical hosts, follow these steps:

  1. If you have not done so already, install and configure an Application Server on one host machine and point it to a database.
     Note the keystore password given for the above installation of the Application Server. You will need to provide the same password for the Application Server installations on the other physical hosts.
  2. Install additional Application Servers on other physical machines, providing the same keystore password used by the first Application Server, and pointing to the same database and file server.
  3. Copy the bladelogic.keystore file from the _template directory from the first Application Server host to every deployment folder on the new Application Server. The file location is <installationDirectory>/NSH/br/deployments/_template/bladelogic.keystore.
  4. Ensure that the time on all Application Server hosts are synchronized. BMC recommends that you configure the Network Time Protocol (NTP) service to point to the same NTP server.
  5. If you have more than one Application Server running on each host in a multiple host environment, ensure that you synchronize the keystore files and the corresponding password for all deployments. See Synchronizing keystore files of multiple Application Servers.
  6. Start the Application Servers, in any order.

Additional folders to synchronize

If you are using local folders on the Application Server for Extended Object scripts, NSH Scripts, or custom CLI commands, then you must also synchronize those folders across all hosts in a multiple Application Server environment.

The following table contains some examples of folders that you may need to synchronize across hosts.

Folder

Description

NSH/share/sensors

You will need to synchronize this folder if:

  • You have installed any BMC Server Automation compliance content, as this folder contains NSH scripts used by the compliance rules.
  • The folder contains any Extended Object scripts. 
    Recommendation: Create Extended Object scripts on the file server, specifying a complete path to the fileserver host. 

    Tip: BMC recommends that you create an alias to the file server host, so that even if the physical file server is moved, you would not need to change the Extended Objects or synchronize the folder.

NSH/Scripts

If this folder contains any Extended Object scripts, synchronize this folder on the new Application Server.

Other folders

If you have any other folders that contain Extended Object scripts, custom grammar files, NSH scripts, or BLCLI commands, you also need to synchronize those folders on the new Application Server. The NSH/br/xml/cli folder is an example of a folder that might need to be synchronized, if you had created custom BLCLI xml file command definitions.

 

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