System requirements
Before you install the product, ensure that your environment meets the hardware and software requirements listed in the following topics:
To get complete compatibility information, 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.
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.
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 GB2 | 2 | 40 GB | 140 MB |
AP | 8 GB2 | 2 | 40 GB | 140 MB |
LAP | 4 GB | 2 | 40 GB | 100 MB |
HA-CDP | 8 GB2 | 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.
Notes
- 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.
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 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 | Docker Engine Enterprise Edition 18.09.1 |
| TrueSight Orchestration components support |
|
Supported browsers
The following table lists the web browsers supported by Platform (applicable for both classic and container deployments).
| Browser | Version |
|---|---|
| Google Chrome | 70 (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 (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 | 7 6.x | x86_64 |
| Microsoft Windows Server |
| x64 | |
| 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 |
| Host OS | Red Hat Enterprise Linux 7.5 CentOS 7 |
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 (applicable for both classic and container deployments).
| Database | Architecture |
|---|---|
| Microsoft SQL Server 2017 | 64-bit |
Microsoft SQL Server 2016 (Enterprise) | 64-bit |
| MySQL 5.1 | 64-bit |
| Oracle 12c | 64-bit |
| PostgreSQL 9.x | 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):
- MySQL
- Oracle
- DB2
- 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).
Authentication requirements
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 | 18.11 |
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.
Comments
Hi! We recognized, that when we install TSO on windows server with german locale settings (and number formats), the convert to numeric TSO function is not working anymore. E.g. the result of 30.0 will be 300 instead of 30.
When we switched the language and locae settings of the server to english UK, copied the settings to all user accounts and rebooted the server, the convert to numeric function was working again.
Is this a bug or is there a specifiy language/locale requirement? If so, can you please add them to the TSO system requirements docu?
Thank you for reaching out, Patrik. I will work with the team to see if this is the case and update the documentation accordingly, if required.
Patrik Stanz. TSO does not support localization and internationalization in German. Hence, function might not work.
Why does this page show support for newer technologies (Windows Server 2016, Windows Server 2019, MS SQL Server 2016) and the Architecture Compatibility Matrix does not? SPAC is supposed to be retiring, and yet its replacement does not seem to be getting accurate information populated into it.
Hi,
We update the document for each release. The SPAC is also supposed to be updated. Thanks!
"The SPAC is also supposed to be updated."
If I'm leaving a comment about the documentation showing support for newer technologies, but your OFFICIAL compatibility tool does not, support will not be willing to investigate issues if the "official" source of supported technologies and platforms does not indicate support. Not to mention the fact that 2 dissenting statements of supported technologies does not make it easier to understand whether or not support is there.
If the document is updated with each release, and that information is sent to the team that supports SPAC, who is following up with them for their inability to ingest the new information? Where's the follow-through?
I agree, Greg. Let me investigate as to where and why is there a disparity between SPAC and the docs.
This issue has been highlighted to the team updating the SPAC and we have started working on making sure there's no discrepancy between the two. As of now, there is no update required on the docs. Thanks for the comment, Greg.
There needs to be an update added to the v8.2.0 document that Google Chrome is only supported up to version 72, at least according to the documentation I've seen.
20.02+ should support Chrome from v72 and up, correct?
Hi Greg,
We have updated the browser support in both 8.2 and 20.02 docs now.
Yes, the supported browser version for 20.02 is 77.
I think you've misunderstood. For version 8.2.0, Chrome only works UP TO version 72. Listing version 70 as the supported browser version to 9 out of 10 people says that ONLY version 70 of Chrome will work, when in fact any version of Chrome that supports Flash should work.
Similarly, with version 20.02 and beyond, support should START with Chrome version 77 and beyond.
OR
A statement similar to "if the browser supports HTML5, it should be supported."
What is posted actually makes it more difficult to work with BMC Support because it doesn't actually give a full picture.
Hi Greg,
Version 70 was the one against which the team has tested and validated this release. It was the latest at the time of the release. We cannot say "if the browser supports HTML5, it should be supported." because it hasn't been validated for such scenarios. Chrome versions are updated automatically, hence we specify the version that we tested against.
If you face challenges with using the platform with your current browser version, please let us know about the problem.
I stated exactly that in my previous replies. For TSO v8.2.0, the documentation doesn't indicate that the version of Chrome listed was the version tested at the time the documentation was published. I had to open a case with support in order to determine that Chrome v72 was the last officially supported version to work with TSO v8.2.0. Right now, the only browsers I know to work with TSO v8.2.0 are IE11, and Microsoft Edge. Microsoft Edge is likely to drop support of Flash before the end of the year, so the last remaining functioning browser may be IE11.
Documentation now indicates "Validated against the version at the time of the release" in the Supported browsers" section. SPAC is also updated to show the latest supported versions of OS. Please let us know if you are still facing any issues.
Please make sure that the updates are propagated to other versions. 8.2 is no longer the current version.
Sure, Greg. Changes done in 2002 version as well.
Log in or register to comment.