The core of the three-tier architecture in BMC Server Automation is the Application Server. Controlling communication between clients and servers as well as access to database, file, and mail servers, the Application Server can be adjusted to scale a system and to fine tune its performance.
The Application Server and the RCP client (BMC Server Automation Console) must be located on the same Local Area Network (LAN). Remote users can use the console through either remote desktop protocol (RDP) or Citrix from a remote machine to the machine where the console resides.
There are two general configurations for Application Servers in the BMC Server Automation environment:
The following topics provide instructions for configuring the Application Server:
Any directory or file that has the same name as an Application Server instance could interfere with launching Application Servers. Avoid creating any files or directories in the /opt/bmc/bladelogic/NSH/br/ directory with the same name as an Application Server instance. For example, creating a file with the name "default" in the /opt/bmc/bladelogic/NSH/br/ directory will cause problems launching the Application Server and blocks the Application Server from starting the required services. As a general rule, avoid placing any files in the directories that the Application Server uses for its own storage, such as the /opt/bmc/bladelogic/NSH/br/ directory.