System requirements
Before you install the product, ensure that your environment meets the hardware and software requirements listed in the following topics:
- System requirements for TrueSight Orchestration – Classic mode
- Supported browsers
- Supported operating systems
- Supported databases for platform metrics
- Supported external databases for the repository
- Java requirements
- Authentication requirements
- Implementing system parameters in standard environments
- How log files affect disk space
To get complete compatibility information, use the BMC Product Compatibility Utility.
System requirements for TrueSight Orchestration – Classic mode
In a classic mode, you deploy the product on servers (physical or virtual).
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.
Component | Application memory (Java Heap) 1 | Number of processors (quad core or better) | Runtime disk space requirements | Installation disk space requirements |
---|---|---|---|---|
Repository | 2 GB | 1 | 40 GB | 100 MB |
CDP | 8 GB 2 | 2 | 40 GB | 140 MB |
AP | 8 GB 2 | 2 | 40 GB | 140 MB |
LAP | 4 GB | 2 | 40 GB | 100 MB |
HA-CDP | 8 GB 2 | 2 | 40 GB | 140 MB |
Development Studio | 2 GB | 2 | 20 GB | 300 MB |
Operator Control Panel | 1 GB | 1 | 1 GB | 100 MB |
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.
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.
Supported browsers
The following table lists the web browsers supported by
Platform.
Browser | Version |
---|---|
Google Chrome | 77 (64-bit) Validated against the version at the time of the release |
Microsoft Edge | Latest version |
Mozilla Firefox | Latest version |
Supported operating systems
The following table lists the supported operating systems for
Platform server components.
Platform component | Supported OS | Supported versions | Hardware |
---|---|---|---|
servers (Classic deployment) (Includes the repository and | Red Hat Enterprise Linux |
| x86_64 |
Microsoft Windows Server |
| x64 | |
SUSE Linux Enterprise Server | 15 SP2 | 64-bit |
The following table lists the supported operating systems for
Development Studio.
component | OS | Version | Hardware |
---|---|---|---|
Development Studio | Microsoft Windows Server |
| x64 |
Microsoft Windows | 10 Enterprise | x86_64 |
Supported databases for platform metrics
The following table lists the supported databases for
Platform metrics.
Database | Architecture |
---|---|
Microsoft SQL Server 2019 | 64-bit |
Microsoft SQL Server 2017 | 64-bit |
Microsoft SQL Server 2016 | 64-bit |
MySQL 5.7 | 64-bit |
Oracle 19c | 64-bit |
Oracle 19c RAC New in 20.02.01 Oracle Exadata supported on Enterprise Edition (Extreme Performance and High Performance) | 64-bit |
PostgreSQL 9.x | 64-bit |
Supported external databases for the repository
You can configure the repository with the following supported external databases:
- MySQL
- Oracle
- DB2
- Microsoft SQL Server
Java requirements
Platform uses AdoptOpenJRE8u202. BMC recommends that you upgrade to the latest platform version to get all the available fixes and security updates.
Authentication requirements
Remedy Single Sign-On (external or embedded) is the authentication tool that must be installed and configured with TrueSight Orchestration .
The following versions are supported:
Remedy SSO (external) |
|
---|---|
Remedy SSO (embedded) Note: Installed with platform components | 20.02 |
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.