Configuring the Application Server
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:
- Single (Default) Application Server on the host — This configuration is the most common one and can be performed as a last step in the installation of an Application Server. During installation, you use the Post Install Configuration wizard to perform the initial configuration of the Application Server. With this basic configuration, you can start the Application Server and then change it as needed. See Using the Post-Install Configuration wizard to configure the default application server.
- Multiple Application Servers on the same host — This configuration lets you add multiple Application Servers to the host and configure them to perform one or more functions. See Configuring a multiple Application Server environment.
Use the following tools to make configuration changes:
- To make changes to basic configuration settings later, run the Application Server Configuration wizard. For information, see Using the Application Server Configuration wizard to change configuration settings.
- BMC Server Automation provides a utility called the Application Server Administration console, a command line utility that enables you to set:
- All of the parameters used by the Application Server.
- The same parameters as those available in the Post-Install Configuration wizard, and you can also use it to set other more complex configuration options.
For information, see Using the Application Server Administration console (
blasadmin) to configure Application Servers.
- To manage multiple Application Servers on the host or change their configurations, use the Infrastructure Management window. For information, see Managing multiple Application Servers on the same host.
The following topics provide instructions for configuring the Application Server:
- Understanding the Application Server
- Using the Application Server Administration console (blasadmin) to configure Application Servers
- Using blasadmin to perform initial application server configuration
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.