This documentation supports the 21.05.02 version of BMC Helix Innovation Suite for on-premises deployment.
To view an earlier version, select the version from the Product version menu.

System requirements

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

Hardware requirements

For this release, BMC has certified BMC Deployment Engine by using Kubernetes (version 1.18) or OpenShift cluster (version 4.6).

We recommend that each node in the cluster should have at least the following infrastructure:


The following table shows only the minimum recommended size of each individual Worker/Master node. This is not the size of the overall Kubernetes deployment. The overall size of your Kubernetes cluster will depend on your usage. If you require estimated sizing details, please contact BMC Support.

SpecificationMaster nodeWorker node
CPU4 coreMinimum 8 core
Memory16 GBMinimum 32 GB
Available system disk in addition to the OS boot disk after OS installation60 GB60 GB

You must create the following namespaces in your cluster:

  • Namespace to install the infra services and platform services provided by BMC Helix Platform.
  • Namespace to install EFK for logging.
    For information about creating namespaces to install BMC Helix Platform services and EFK, see Setting up the installation environment.
  • Namespace to install BMC Helix Innovation Suite.
    Make sure that the namespace name consists of lowercase characters and consist of a hypen '-'


To support Elastic deployment, increase the maximum number of memory maps on each worker node by running following command:

 ]# echo vm.max_map_count=262144 > /etc/sysctl.d/es-custom.conf

 ]# sysctl -w vm.max_map_count=262144

 For more information, see

Review the requirements for Jenkins server. See .Setting up BMC Deployment Engine v21.05.02.

System requirements

Make sure that your environment meets the following requirements:

ComponentSupported Versions
Container Orchestration
Package ManagerHelm 3.2.3

nginx-ingress-controller 0.32

nginx-ingress-controller is installed by default in the ingress-nginx namespace. Review the following parameter value requirements in the nginx-configuration configmap in the ingress-nginx namespace:

  • enable-underscores-in-headerstrue
  • proxy-body-size256m
  • proxy-connect-timeout300
  • proxy-read-timeout600
  • proxy-send-timeout600
  • use-forwarded-headerstrue

You can use the following command to view the parameters in the nginx-configuration configmap:

kubectl describe cm nginx-configuration -n ingress-nginx
Container Host OSAny x86_64 GNU/Linux OS supporting Kubernetes 1.18, including;
  • Debian 9+
  • Fedora 25+
  • HypriotOS v1.0.1+
  • CentOS 7
  • RHEL 7
  • Photon OS
  • CoreOS 7+
Host OS Bash ShellBash Shell 4.2 or above
Persistent or Elastic Storage

BMC supports a Bring-Your-Own-Storage-Class model, for any Kubernetes Storage Class supporting high performance IOPS.
CephRBD is certified by BMC.

Load Balancer

F5 Load Balancer(s) or other Load Balancer supporting: 

  • SSL Offload,
  • Allow X-Forwarded- Headers Upstream of Ingress,
  • Reverse Proxy http back to https,
  • Unaltered response redirects.

Important: If you use the Sophos UTM 9.x load balancer, make sure that you configure the following parameter values:

  • X-Forwarded-Protohttps
  • X-Forwarded-Port443
  • In the nginx-ingress-controller, in the Config Map values, configure the use-forwarded-headers parameter value as true.
Security Certificates

DigiCert and R3 certificates.

CA signed certificates and self-signed certificates are not supported.

Docker RegistryDirect access to BMC's Docker Trusted Registry (DTR) at
Local Harbor 1.8 and above synchronized with BMC's Docker Trusted Registry
DB Support
  • Oracle Database 19c
  • Oracle Database 12.2
  • Oracle Database 12.1
  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2016 (SP2)
  • PostgreSQL 13


  • BMC Helix Multi-Cloud Broker is not supported on SQL server.
  • In general, BMC recommends running on the latest Service Pack, Maintenance Level, or other such update to listed databases.
  • AR System server and BMC Helix CMDB supports 'AlwaysOn' for Microsoft SQL Server.
  • Remedy AR System and BMC Helix CMDB server supports Oracle Real Application Clusters (Oracle RAC) feature of Oracle Database.
  • Oracle database pluggable/un-pluggable both are supported.
  • PostgreSQL supported configuration includes case sensitive and Unicode implementation.
Email Engine

Microsoft Exchange Server 2016 (64-bit)


  • Microsoft has discontinued MAPI support in Microsoft Exchange Server 2016; Support for EWS (exchange web service) is available for Microsoft Exchange Server 2016 only .
  • OAuth 2.0 based authentication is required for Microsoft Office 365 Exchange starting with 20.02.01 and later
  • Starting with AR System 20.02.01 (also known as 20.02 Patch 1), Email Engine supports OAuth 2.0 based authentication for the Exchange Web Services (EWS) protocol to access Microsoft Office 365 Exchange.
    For more information, see AR System 20.08 enhancements in the AR System online documentation.

Browser support

 Operating System


All supported operating systems and platforms



Windows 7     



Windows 8



Windows 10



Microsoft Edge

HARMAN Packaged Browser (See notes below)

Macintosh OS X 10.5

Safari 6.3.x


BMC Software provides Limited Support for Flash-based capabilities in BMC products when used in combination with the HARMAN browser (Chromium option only). This Limited Support is provided temporarily until Dec 31, 2021, to cover the time period until customers upgrade to the latest BMC product version that has replaced the Flash-based capabilities.

Refer to following resources from BMC, Adobe, and Harman for more details:

Kubernetes permissions

Support Assistant tool is essential for collecting Action Request SystemBMC Helix ITSM, and BMC Helix Innovation Studio logs and is a required part of the BMC Helix Innovation Suite installation. BMC cannot provide effective support for BMC Helix Innovation Suite without using this tool. Support Assistant tool is used by BMC Support for troubleshooting issues.

Support Assistant tool requires additional permissions to access the logs associated with BMC Helix Innovation Suite containers that are deployed in your Kubernetes environment.

Best Practice

We recommend that you validate the following permissions with your Kubernetes administrator:

  • You must have the cluster administrator permissions to create the clusterrole and clusterrolebinding permissions to install Support Assistant tool. 
  • The Support Assistant tool container must run with root user permission.

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


  1. Eric Wuensche

    Hi, I'm missing the system requirements for the "deployment engine" in this area.

    Jul 13, 2021 08:11
    1. Ariel Manka

      Hi Eric,

      it's here

      Sep 22, 2021 08:27
  2. Andreas Mitterdorfer

    I'm missing information on the number of required nodes? Are there recommendations on number of nodes depending on planned customer size?

    Sep 30, 2021 02:51
    1. Ariel Manka

      Hi Andreas,

      As a general rule any odd number of 3 or more should be able to do the trick. If you take the specs from here you will see that recommended number of CPUs on worker node is 8. When you unzip "Helix on prem deployment manager" you will find configuration files in the ./helix-on-prem-deployment-manager/configs. For instance poc.config has an entry for TOTAL_REQUIRED_CPU=150 which means that you need 150 CPU cores available on all worker nodes in total. This is a ridiculous number and means that you need at least 19 worker nodes. I have three worker nodes with 16 CPU each and I edited that file to more reasonable 50 total CPUs. Perhaps someone from BMC could review the requirements here? It will be joy explaining why production large environment needs 600 CPU cores. Similar scenario with RAM: TOTAL_REQUIRED_RAM=327798360 (327MB or am I converting something wrong?)


      Oct 05, 2021 01:57
      1. Robin Ashford

        This page does not currently show the sizing information for an overall deployment. We expect to be able to publish guidance on approximate sizing for Innovation Suite deployments in the coming few weeks.

        Until then we are able to provide provisional sizing estimates for customers who urgently need this information in order. You can reach this service by contacting your partner or account manager.

        Until we have issued formal sizing guidance, please do not plan sizing based on the data in this configuration file!

        For the avoidance of doubt:

        • An odd number of worker nodes is not a requirement, this typically applies to Master or Control nodes.
        • 8 CPU is listed as the minimum for a worker node. You may have any number or profile of worker nodes as long as you meet the overall compute requirements, which we will publish.
        Oct 11, 2021 09:03
  3. Gerardo Ramirez


    Could you please specify if the requirements: The storage of 60gb is that a separate disk from the OS boot disk? Or same boot disk plus 60G per node?

    Oct 01, 2021 01:29
    1. Poonam Morti

      Hi Gerardo,

      The storage of 60 GB can be same disk. However, the 60 GB storage is in addition to OS.



      Oct 27, 2021 03:28
  4. Jani Myllymaki

    Is RHEL 8 supported it is show as RHEL 7 not RHEL 7+ in the table of supported OS

    Nov 03, 2021 10:59
    1. Poonam Morti

      Hi Jani,

      RHEL 8 is not supported. The supported version is RHEL 7.



      Nov 11, 2021 04:02
  5. Balaji Kumbhar

    Hi Team - How many worker nodes (VMs) are required for the lower environment and production environment any rough sizing?

    Nov 10, 2021 07:37