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. 

Note

For software requirements and compatibility information for this release of see BMC Solution and Product Availability and Compatibility Utility (SPAC requires a Support login). Log in using your support ID, search for Platform and choose the current release to display compatibility information.

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

Dashboards4 GB240 GB100 MB

1 Add the application memory noted to the operating system memory in accordance with the operating system vendor recommendations.

Note

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.


 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 BAO 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. For more information about adjusting memory settings, see Configuring memory settings.

Remedy Single Sign-On: To view the system requirements for Remedy Single Sign-On see, Remedy Single Sign-On System Requirements .

Note

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.

Supported operating systems

The following table lists the supported operating systems for  Platform.

Platform componentSupported OSSupported versionsHardware

Servers

(Including the repository and
peers such as CDP, AP, LAP, and HA-CDP)


















Red Hat Enterprise Linux

7

6.x

x86_64
Microsoft Windows Server

2016 Standard

2012 R2 Standard

2008 R2 Enterprise

x64
Oracle Solaris1064-bit
SUSE Linux Enterprise Server11.264-bit

Development Studio


NEW IN 8.0.01Microsoft Windows Server

2016

2012 R2

x64
Microsoft Windows 7x86_64
Microsoft Windows 10 Enterprisex86_64
Microsoft Windows 8.1x86_64
Microsoft Windows 8 Enterprisex86_64

Requirements for metrics database

The following table lists the supported databases for  Platform metrics.

DatabaseArchitecture

NEW IN 8.0.01 Microsoft SQL Server 2016 (Enterprise)

64-bit
Microsoft SQL Server 201264-bit
Microsoft SQL Server 200864-bit
MySQL 5.164-bit
Oracle 12c64-bit
PostgreSQL 9.x64-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.

Was this page helpful? Yes No Submitting... Thank you

Comments