Before you deploy the product, make sure that your environment meets the hardware and software requirements.
Make sure that your environment meets the following requirements:
|Java||Java 11 and later for AR System clients, such as Developer Studio, AI, and Kaazing.|
|Package Manager||Helm 3.2.3|
The default namespace of ingress controller is ingress-nginx.
Review the following parameter value requirements in the nginx-configuration configmap in the ingress-nginx namespace:
You can use the following command to view the parameters in the nginx-configuration configmap:
|Container Host OS|
BMC Helix Innovation Suite has no specific dependencies on the underlying Linux OS or release running on your Worker Nodes.
You can use any x86_64 GNU/Linux OS supported by your Kubernetes or OpenShift platform and release version.
|Host OS Bash Shell||Bash Shell 4.2 or later|
|Persistent or Elastic Storage|
BMC supports a Bring-Your-Own-Storage-Class model, for any block storage supporting high performance IOPS.
CephRBD is certified by BMC
F5 Load Balancer or other Load Balancer:
The following load balancer SSL methods are supported:
Important: Make sure that you configure the following headers for SSL Offloading at the load balancer:
DigiCert and R3 certificates.
Other CA signed certificates and self-signed certificates are not supported.
|Docker Registry||Direct access to BMC's Docker Trusted Registry (DTR) at https://containers.bmc.com|
Local Harbor 1.8 and later synchronized with BMC's Docker Trusted Registry
Microsoft Exchange Server 2016 (64-bit) and Microsoft Office 365 Exchange
BMC Helix uses the HorizontalPodAutoscaler (HPA) for its services so that the product can scale based on the customer usage. For the HPA to function, Kubernetes must expose metrics that are used to trigger scaling activities, for which a Metrics Server is required.
For information about the HPA, see .
For information about the Metrics Server, see .
The sshpass utility helps administrators use the 'ssh' connection type with passwords. Install the sshpass program to easily manage SSH connections in scripts.
For more information, see To install sshpass.
Jenkins server requirements
Review the following requirements for the Jenkins server:
|Jenkins server||1||4||Minimum 16 GB||200|
For information about setting up BMC Deployment Engine, see Setting up BMC Deployment Engine.
To install sshpass program
Install sshpass, if not already installed by using the following steps:
Verify that sshpass is not already installed in your system. The following command checks if sshpass is available in any of the available repositories.
# which sshpass
If sshpass is not found on any of the available repositories, the following response is returned:
/usr/bin/which: no sshpass in
Use the following command to know the possible repositories in which sshpass is available on the system:
# yum provides sshpass
Install sshpass by using the following command:
# yum -y install sshpass
Verify that sshpass is installed in your system by using the following command:
# which sshpass
Harbor repository requirements
Make sure that your system meets the following requirements to access images from a local Harbor repository:
Minimum 4 CPU with 8 GB memory and 500 GB disk space
Harbor installation uses the following ports as the default ports:
Learn about Harbor installation network port requirements at
For information about setting up Harbor repository, see Setting up a Harbor repository.
All supported operating systems and platforms
HARMAN Packaged Browser (See notes below)
Macintosh OS X 10.5
For information about system requirements for BMC Helix Platform deployment, see .
Review the following requirements for the namespaces in your cluster:
- Namespace to install the common 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 IT Service Management.
Make sure that the namespace name consists of only lowercase alphanumerics and hyphens. Example, 'bmc-itsm'.
The actual namespace names are specific to your environment.
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 https://www.elastic.co/guide/en/elasticsearch/reference/current//vm-max-map-count.html.