Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Configuring a multiple Application Server environment

This section provides information about configuring a BMC Server Automation environment that uses multiple Application Servers (MAS). It includes the following sections:

Why use multiple Application Servers?

To meet the demands of a larger data center, you can deploy additional Application Servers. Most commonly, you need to add job servers to provide support for a larger number of managed servers. In some cases, you might also need to deploy additional configuration (UI) servers to support a larger user population.

Using separate Application Servers in this way, the performance of one Application Server does not affect the behavior of another. Defining multiple Application Servers also enables you to use more fixed memory on a host system because the Java Virtual Machine heap limit would otherwise restrict a single Application Server to a fixed amount of memory.

In an environment with multiple Application Servers, a master Application Server assigns jobs to the individual Application Servers where they are executed. The master Application Server ensures that jobs are assigned based on the available resources and capacity at each Application Server and that a proper failover mechanism is in place to minimize down time.

Considerations when using a MAS environment

Note the following when implementing a MAS environment:

  • You cannot control which Application Server is chosen to be the master Application Server. The choice of the master Application Server occurs automatically. If the master Application Server is shut down, a different Application Server takes its place automatically.
  • For the master application server to successfully assign jobs, all Application Servers with full database access (that is, not including stand-alone NSH proxies) must be able to communicate with each other on the network through the RegistryPort and the MaxPort/MinPort range. For more information about these communication ports, see Configuring communication ports.
  • When adding new Application Server deployments to the environment, consider the additional connections that will be made to the database back-end. In addition, to ensure that the database can handle the increased number of requests that the new Application Servers will add, review the database configuration parameters that control performance and handle connections.
  • For a discussion about adding BMC Server Automation components to provide greater management capacity, see Large-scale installations.
  • To see guidelines for sizing and scaling Application Servers in a large-scale environment, see Sizing and scalability considerations

Where to go from here

The following topics describe how to set up a multiple Application Server (MAS) environment:

About Application Server deployments and profilesProvides an overview of Application Server deployment and the different types of Application Servers.
Creating additional Application ServersDescribes how to create additional application servers from the BMC Server Automation Console and command line.
Configuring multiple Application Servers on the same hostProvides instructions for configuring multiple application servers on the same host.
Configuring multiple Application Servers on different hostsProvides instructions for setting up a multiple Application Server environment, with the Application Servers residing on different hosts.
Viewing and editing an Application Server profileProvides instructions for viewing a profile and changing the profile attributes.
Ensuring all bladelogic.keystore files are consistentProvides instructions for ensuring the consistency of all bladelogic.keystore files in a MAS environment.
Was this page helpful? Yes No Submitting... Thank you