- System requirements for TrueSight Orchestration – Classic mode
- System requirements for TrueSight Orchestration in containers
- Supported browsers
- Supported operating systems
- Supported databases for platform metrics
- Supported external databases for the repository
- Azul Java requirements
- Authentication requirements
- Implementing system parameters in standard environments
- How log files affect disk space
To get complete compatibility information, use the .
To access the product compatibility information on the Customer Support website, you must have a Support ID.
System requirements for TrueSight Orchestration – Classic mode
In a classic mode, you deploy the product on servers (physical or virtual). Starting version 8.2.00, TrueSight Orchestration is also available in containers.
You must allocate sufficient resources to a component that is running on a virtual machine. Ensure that is the only product running on its host computer.
The following table lists the system requirements for the components.
Application memory (Java Heap)1
Number of processors (quad core or better)
Runtime disk space requirements
Installation disk space requirements
Operator Control Panel
|Dashboards||4 GB||2||40 GB||100 MB|
1 Add the application memory noted to the operating system memory in accordance with the operating system vendor recommendations.
- Application memory is different than the physical RAM required for the server. Application memory is the amount of memory applications can use out of the total available physical memory on the server.
- Since consumes no more than 50 percent of the server memory, BMC recommends that if a server has an 8GB CDP, that server must have at least 16GB total memory.
For optimal performance, BMC Software recommends that you use a 64-bit operating system. You can configure an LAP to run on a 32-bit operating system, but the allocated memory is limited to 1.5 GB.
2.a If your environment runs with high concurrent volumes and workflow complexities, increase the recommended application memory by a factor of 2x or 3x: from 8GB to 16GB or 24GB; from 4GB to 8GB or 12GB.
2.b As the total size of the activated modules in your environment increases, you may need to increase the application memory by 2x: from 8GB to 16GB.
These recommendations are for production environments. Development grids may only require half the application memory documented above.
By default, the memory settings (-Xmx and -Xms parameters) for Platform components is set to minimal required to start the applications. For QA and production environments, BMC recommends that you specify the memory size values as per the application memory settings specified in the earlier table.
System requirements for TrueSight Orchestration in containers
This section lists the minimum system requirements for installing and planning TrueSight Orchestration in Docker containers.
|Resource||Supported resources and versions|
Docker Engine Enterprise Edition 18.09.1
|TrueSight Orchestration |
The following table lists the web browsers supported by Platform (applicable for both classic and container deployments).
|Google Chrome||70 (Validated against the version at the time of the release)|
|Microsoft Edge||Latest Version|
|Microsoft Internet Explorer|
|Mozilla Firefox||Latest Version|
Supported operating systems
The following table lists the supported operating systems for Platform server components (applicable for both classic and container deployments).
|Platform component||Supported OS||Supported versions||Hardware|
servers (Classic deployment)
(Includes the repository and
Red Hat Enterprise Linux
|Microsoft Windows Server|
2012 R2 Standard
2008 R2 Enterprise
|SUSE Linux Enterprise Server||11.2||64-bit|
The following table lists the supported operating systems for in containers.
|TrueSight Orchestration (Containerized deployment)||Supported OS|
|Container OS||CentOS 7|
Red Hat Enterprise Linux 7.5
The following table lists the supported operating systems for Development Studio.
Microsoft Windows Server
|Microsoft Windows||10 Enterprise||x86_64|
|Microsoft Windows||8 Enterprise||x86_64|
Supported databases for platform metrics
The following table lists the supported databases for Platform metrics (applicable for both classic and container deployments).
|Microsoft SQL Server 2017||64-bit|
Microsoft SQL Server 2016 (Enterprise)
|Microsoft SQL Server 2012||64-bit|
|Microsoft SQL Server 2008||64-bit|
Supported external databases for the repository
You can configure the repository with the following supported external databases (applicable for both classic and container deployments):
- MS SQL Server
Azul Java requirements
Starting version 8.2.00, Platform uses Azul Java 8. BMC recommends that you upgrade to TrueSight Orchestration Platform version 8.2 to get all the available fixes and security updates (applicable for both classic and container deployments).
Remedy Single Sign-On (external or embedded) is the authentication tool that must be installed and configured with TrueSight Orchestration (applicable for both classic and container deployments).
The following versions are supported:
|Remedy SSO (external)|
Remedy SSO (embedded)
Note: Installed with platform components
Implementing system parameters in standard environments
To implement the parameters from the preceding table in a single-server demonstration/POC environment, you must provide:
- 6-8 GB for the repository, CDP, and Operator Control Panel
- 2 CPUs
- 10 GB of runtime disk space allocated to
To implement the parameters from the preceding table in a two-server production environment, you must provide:
- Server 1: 2 GB, 1 CPU, 40 GB disk space allocated to the repository
- Server 2: 8 GB, 2 CPUs, 40 GB disk space allocated to a CDP and Operator Control Panel
How log files affect disk space
During runtime, each component creates at least one log file set, the size of which depends on your configuration. The CDP, AP, and Development Studio can also be configured to create a second log file set.
An individual log file can retain up to 4 MB of data. Upon reaching the maximum log size, the active log file is archived and a new active log is created. A standard log set might contain one active log and up to nine archive log files, each requiring 40 MB of disk space.