To meet the demands of a larger data center, you can deploy additional Application Servers. The additional Application Server is used for improving the performance of BMC Server Automation. The method described here for adding additional Application Servers is relevant only if you installed your default Application Server node using the unified product installer.
(Windows only) To add an additional application server on a Windows machine, you must first set up a PsExec server on a Windows server. A PsExec server functions as a proxy to execute psexec requests on a Windows Application Server without an agent.
You can add an Application Server by clicking Add BSA Application Server Machine under the Configuration menu in the Console. Select the Node Details and Advance Options tabs and enter the following information:
Execution Protocol — (Linux only) Specifies the mechanism for accessing the agentless Application Server machine that you are setting up. Select one of the following:
- SSH Execution Protocol — Executes commands directly on the agentless host using the credentials defined on this panel.
- SSH + SUDO Execution Protocol — Executes commands directly on the agentless host using the credentials defined on this panel. The sudo
command is attached as a prefix to all commands. If sudo
requests a password, the passphrase entered on this panel is used.
- SSH + SU Execution Protocol — Executes commands directly on the agentless host using the credentials defined on this panel. The credentials defined on this panel are used to issue the su
command to gain elevated privileges.
Administrator ID — User name of an account with Administrator or Superuser privileges on the additional Application Server machine.
Note
If you are using a domain user, enter the ID in the <DominName>\<UserID> format. For example, bmc.com\TestID.
Temporary staging directory - (Linux only) During installation, the system stores temporary files in the /tmp directory. You can specify an alternate location to store the temporary files, if you do not have enough space or you do not have access to the /tmp directory.
Note
Progress messages and (in the case of problems) error messages are displayed on-screen and also written to the Application Server log file, appserver.log, which is located in installationDirectory/NSH/br (on UNIX or Linux) or installationDirectory\NSH\br (on Windows).
Harden the security configurations on each of the new application server nodes. Copy the following files from the default Application Server node to each of the newly added secondary nodes: