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.

3. For each additional Application Server that you installed (see step 2), run the Post-Install Configuration wizard, and provide database connection specifications. Enter specifications for the same database that is used by the first Application Server (which you installed in step 1), so that all Application Servers communicate with the same database.

    Use the following steps:

   1.  To start the Post-Install Configuration wizard, do one of the following:
      
      • From the Windows Start menu, select Programs > BMC Software > BladeLogic Server Automation Suite > Utilities > Application Server Configuration Wizard.
      • Start the wizard manually by running one of the following commands in the directory where BMC Server Automation is installed. Enter the following:

        • (Windows)

          bin\blappconf.exe

        • (UNIX)

          ./br/blappconf

   2. In the configuration wizard, read the introductory page and click Next.

   3. On the Database page, choose a Database Type (either Oracle or SQL Server).
   4. If you are not using a custom connection string, provide the following database configuration information (and do not select the Advanced option):
      • Database Server — Host name or IP address (IPv4 or IPv6) of the server running the database.

      • Database Port— Port the database listens on. By default a BMC Server Automation installation uses the following database ports:

        Database Type	Port Number
        Oracle	1521
        SQL Server	1433

      • Database Name — Microsoft SQL server database name. By default, the database name is bladelogic . (This option is only available for SQL server databases.)
      • SID — System ID of the Oracle database. (This option is only available for Oracle databases.)
      • User ID — User name that the database needs to authenticate your connection.
      • Password — Password assigned to the user ID.
        or...
        If you are using a custom connection string, provide the following database configuration information:
      • User ID — User name that the database needs to authenticate your connection.
      • Password — Password assigned to the user ID.
      • Advanced — Select this option to indicate that you are providing a custom connection string.
      • Connection String — Type the custom connection string in the field below the Advanced check box.
   5. Click Finish to apply the configuration that you specified while skipping any further wizard panels.
4. Copy the bladelogic.keystore file from the <installationDirectory>/NSH/br/deployments directory on the first Application Server host to the same location on each new Application Server.
5. 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.
6. 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.
7. 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.