System requirements

Before you install the product, make sure that your environment meets the hardware and software requirements.

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 TrueSight Orchestration is the only product running on its host computer.

Related topics

Deployment-scenarios

Preparing-for-TrueSight-Orchestration-installation

Identifying-and-fulfilling-your-automation-and-orchestration-needs

The following table lists the system requirements for the TrueSight Orchestration components.

Component	Application memory (Java Heap)¹	Number of processors (quad core or better)	Runtime disk space requirements	Installation disk space requirements
Repository	16 GB	4	200 GB	4 GB
CDP	16 GB²	8	200 GB	4 GB
AP	16 GB²	8	200 GB	4 GB
LAP	8 GB	8	200 GB	4 GB
HA-CDP	16 GB²	8	200 GB	4 GB
TrueSight Orchestration Development Studio	8 GB	8	200 GB	4 GB
TrueSight Orchestration Operator Control Panel	4 GB	4	100 GB	4 GB
Dashboards	4 GB	8	40 GB	4 GB

Add the application memory noted to the operating system memory in accordance with the operating system vendor recommendations.
Notes
- Application memory is different than the physical RAM required for the server. Application memory is the amount of memory TrueSight Orchestration applications can use out of the total available physical memory on the server.
- Since TrueSight Orchestration consumes no more than 50 percent of the server memory, BMC recommends that if a server has an 16GB CDP, that server must have at least 32GB total memory.
- For optimal performance, BMC Software recommends that you use a 64-bit operating system.
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.
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.

Note

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 TrueSight Orchestration 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.

Product compatibility matrix

Third-party software requirements

Product version	Java version	Apache Tomcat web server version
22.2.01	AdoptOpenJRE8u345	9.0.83

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)	20.02
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 TrueSight Orchestration Operator Control Panel
8 CPUs
10 GB of runtime disk space allocated to TrueSight Orchestration

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 TrueSight Orchestration 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 TrueSight Orchestration 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.

System requirements