Deployment sizing requirements
This topic is applicable only for a TrueSight Automation Console (on-premises) deployment.
BMC Helix Automation Console (SaaS) is not available for on-premises installation. For details about subscribing to this service, see BMC Helix subscriber information.
TrueSight Automation Console supports a variety of deployment configurations. Most configurations require the TrueSight Automation Console database and application to be installed on separate servers.
Minimum deployment sizing requirements
The following table describes minimum requirements based on various deployment sizes.
|Requirement||Large||Medium||Small||Minimum space required for installation (GB)|
|Number of |
Automation Console server requirements
|Database server requirements|
|CPUs per |
A small deployment assumes that the database and the application are hosted on the same server. Memory requirements refer to total memory, not heap size.
If you require a deployment larger than the Large deployment described above, extrapolate the system requirements based on the information in the table.
What conditions were used to develop these sizing requirements?
|Number of existing missing patches instances in the database||15 million|
Number of servers managed by the Automation Console
|Number of concurrent users (per node)||25|
|Maximum scan data file size||1GB|
|Average number of missing patches per server||300|
Number of servers enrolled in the Automation Console