System requirements
Before you install the product, ensure that your environment meets the hardware and software requirements listed in the following topics:
Hardware requirements
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.
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.
Remedy Single Sign-On: To view the system requirements for Remedy Single Sign-On see, Remedy Single Sign-On System Requirements.
Supported operating systems
The following table lists the supported operating systems for
Platform.
Platform component | Supported OS | Supported versions | Hardware |
|---|---|---|---|
Servers (Including the repository and | Red Hat Enterprise Linux | 7 6.x | x86_64 |
Microsoft Windows Server | 2016 Standard 2012 R2 Standard 2008 R2 Enterprise | x64 | |
Oracle Solaris | 10 | 64-bit | |
SUSE Linux Enterprise Server | 11.2 | 64-bit | |
Development Studio | New in 8.0.01Microsoft Windows Server | 2016 2012 R2 | x64 |
Microsoft Windows | 7 | x86_64 | |
Microsoft Windows | 10 Enterprise | x86_64 | |
Microsoft Windows | 8.1 | x86_64 | |
Microsoft Windows | 8 Enterprise | x86_64 |
Requirements for metrics database
The following table lists the supported databases for
Platform metrics.
Database | Architecture |
|---|---|
New in 8.0.01 Microsoft SQL Server 2016 (Enterprise) | 64-bit |
Microsoft SQL Server 2012 | 64-bit |
Microsoft SQL Server 2008 | 64-bit |
MySQL 5.1 | 64-bit |
Oracle 12c | 64-bit |
PostgreSQL 9.x | 64-bit |
Java requirements
Platform 8.0.00 uses Java 8. Clients running on Java 7 may face issues with communication handshake due to incompatibilities between Java 7 and Java 8 versions. BMC recommends that you update your environment to Java 8.
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.