Documentation update


To provide a better user experience, we have now created a separate documentation space for BMC Helix Automation Console (previously called BMC Helix Vulnerability Management).
Users of BMC Helix Automation Console can find the latest documentation at BMC Helix Automation Console. .

Deployment scenarios

The number of concurrent end users determines how many TrueSight Automation Console components you must actually deploy. To determine the deployment size appropriate for your needs, see deployment sizing matrix. The sizing matrix also provides minimum hardware requirements for the servers where you are installing additional components. 

You can install a single TrueSight Automation Console database and the application on the same machine. For large deployments, you should segregate the TrueSight Automation Console and application to separate nodes. If additional capacity is necessary, you can install additional instances of the TrueSight Automation Console server.

Small deployment

A small deployment consists of a single database and a single Automation Console application installed on a single host. It connects to a single instance of the TrueSight Server Automation Application Server.

Typically, a small deployment is used for testing, demonstration, or proof-of-concept purposes.


Medium deployment

A medium deployment consists of two Automation Console application servers installed on separate hosts. This type of deployment uses a single database and relies on a single TrueSight Server Automation Application Server.


For details, see Configuring application clusters

Large deployment

A large deployment allows up to six instances of Automation Console application servers. The Automation Console servers employ a single database and rely on a single Server Automation Application Server.

For details, see Configuring application clusters

Related topic

Deployment sizing requirements

Was this page helpful? Yes No Submitting... Thank you