System requirements
Before you install the product, make sure that your environment meets the hardware and software requirements.
To get complete compatibility information for Automation Console, use the BMC SOLUTION AND PRODUCT AVAILABILITY AND COMPATIBILITY UTILITY (SPAC) .
Note
To access the product compatibility information on the Customer Support website, you must have a Support ID.
Endpoint manager requirements
The following tables list the compatible versions of these endpoint managers: TrueSight Server Automation and TrueSight Network Automation
Compatible TrueSight Server Automation versions
TrueSight Automation Console version | TrueSight Server Automation versions | Hotfix required | Notes |
---|---|---|---|
21.02.01 | 21.02.01 Supports the following feature: Creation of batch jobs | No | |
21.02 Supports the following feature: Creation of batch jobs | Yes | Download and apply TSAC 21.02.P1_with_TSSA 21.02GA-Hotfix.zip. For details, see Knowledge Article 000385439. | |
20.02.01 The following features are not supported with this version:
| Yes | Download and apply TSAC 21.02.P1_with_TSSA 20.02.01-Hotfix.zip. For details, see Knowledge Article 000385439. | |
21.02 | 21.02 | Yes | Download and apply DRBLG-126137_TSSA-rest.war_hotfix. For details, see Knowledge Article 000382124. |
20.02.01 The following features are not supported with this version:
| Yes | Download and apply TSAC2102_with_TSSA200201_HF. For details, see Knowledge Article 000380374. |
Compatible TrueSight Network Automation version
TrueSight Automation Console version | TrueSight Network Automation version | Notes |
---|---|---|
21.02.01 | 20.02.03 | Automation Console supports only vulnerability management for the network devices and the following features are NOT supported:
|
Supported BMC product versions
The following table describes the supported versions required for integrating with BMC products:
Product | Version |
---|---|
BMC Discovery (on-premises only) |
|
BMC Remedy Single Sign-On |
|
BMC Remedy IT Service Management (on-premises only) |
|
TrueSight Orchestration Platform (Classic deployment only) | 20.02 |
TrueSight Orchestration Content |
|
Supported browsers
Component | Requirement |
---|---|
Minimum supported resolution | 1920*1080 |
Supported browsers |
Best viewed in Google Chrome 64+ and Microsoft Edge 87+ |
Supported scanning systems
The following table describes the vulnerability scanning systems supported by Automation Console.
System name | Version |
---|---|
Nessus | 8.10 |
Rapid7 | 6.6.51 |
Qualys | Cloud Platform |
Third-party software
Automation Console is bundled with the following third-party software:
Product version | PostgreSQL version | Java version | Apache Tomcat web server version | Docker container operating system |
---|---|---|---|---|
21.02/21.02.01 | 12 | AdoptOpenJDK 11.0.7+10 | 9.0.41 | Alpine Linux 3.10.3 |
Docker requirements and supported operating systems
Automation Console is supported on Linux-enabled Docker, and it requires the following version of Docker:
Utility | Version |
---|---|
docker | 18.09.7 or later (Docker CE) |
docker-compose | 1.19.0 or later |
The following table lists the supported operating systems and Docker Editions:
Operating system | Supported Docker Edition |
---|---|
Red Hat Enterprise Linux 7.9 | Mirantis Container Runtime (MCR) 20.10.0 or later (Formerly known as Docker EE) * For more details, see MCR documentation. |
CentOS 7.x | Docker CE |
*If you want to use Mirantis Container Runtime in a production environment, you need to purchase the license. You can use the trial version for a non-production environment. For more information, see the Mirantis website.
Memory and disk space requirements
Minimum RAM | Minimum free storage for application at <installedLocation> |
---|---|
10 GB | 10 GB |
Minimum hardware requirements
The following table describes the minimum hardware requirements for a small deployment.
Requirement | Small | Minimum space required for installation (GB) |
---|---|---|
Number of concurrent users | 25 | - |
Automation Console server requirements | ||
Number of | 1 | - |
CPUs per | 8 | - |
Automation Console | 32 | 10 |
Automation Console | 100 | 10 |
Database server requirements | ||
CPUs per database server | 8 | - |
Database server memory (GB) | 16 | 8 |
Database disk space (GB) | 100 | 25 |
For more information about sizing requirements based on deployment scenarios, see Deployment sizing requirements.
External database requirements
The following table describes the supported database and its versions.
Database | Supported versions |
---|---|
PostgreSQL |
|
Verify whether the PostgresSQL contrib
modules are also installed. These are optional utilities shipped with the standard package, which may not installed by default. To verify whether the contrib
modules are installed, run the following commands based on your version:
yum list installed | grep postgresql12-contrib
yum list installed | grep postgresql11-contrib
You can install the database by using the executables provided on the BMC Electronic Product Distribution (EPD) site, or you can use an existing PostgreSQL installation.
The following table describes the recommendations for a PostgreSQL database that you can use for optimal performance.
Configuration | Recommendation |
---|---|
Users, Roles |
|
Schema and Tablespaces |
|
Client Authentication |
|
Instance parameters | BMC recommends adding or updating the following parameters in the configuration of the database server in the postgresql.conf or equivalent file: listen_addresses = '*' max_connections = 500 default_statistics_target = 50 constraint_exclusion = on wal_buffers = 8MB min_wal_size = 1GB max_wal_size = 2GB checkpoint_timeout = 15min checkpoint_completion_target = 0.9 log_min_messages = fatal log_min_error_statement = fatal #following parameters should be tuned according #to actual memory available to Database server machine #example of configuration for 8GB RAM maintenance_work_mem = 512MB effective_cache_size = 5GB work_mem = 48MB shared_buffers = 2GB After changing these values, restart the database server. |
External Redis Server requirement
If you want to configure Automation Console in a high availability environment, make sure that you have a non-cluster and non TLS 5.05 or later Redis Server.
Port requirements
The port on which the Automation Console communicates with an endpoint manager must be open, and the application and the endpoint manager must be able to communicate with each other.
The following table provides the port numbers that you must enable for the product. If you intend to use any custom ports during installation, ensure that you open the ports before installing the product.
Important
You cannot change the port numbers after the installation or upgrade. You can use port numbers of your choice only during installation.
Port | Protocol | Configured on | User can change the port number? | Firewall exception needed? | Description |
---|---|---|---|---|---|
10443 | TCP | Host containing the Automation Console application installation | Yes | Yes | Secure port used to access the Automation Console application. |
5000 | TCP | Host containing the Automation Console application installation | Yes (at the time of installation) | Yes | Port used for communication with the Docker repository |
5432 | TCP | Host containing the database installation | No | Yes | Port used by the database (PostgreSQL) for communication |
9843 | TCP | Host containing the Automation Console application | No | Yes | Port used by the application to communicate with Server Automation |
Comments
Link for Endpoint Manager for TrueSight Automation Server KB for HotFix info for 21.02 appears to be an invalid URL?
Thanks for the feedback, Daniel. The link is fixed now.
Could you please include the endpoint manager port and application port to communicate each other in case of integration ? For ex. TSSA to TSAC : 10443, TSAC to TSSA : 9843, AO to TSAC:10443, TSAC to AO 38080, similarly for TSNA and Discovery
Log in or register to comment.