Configuration file settings

Use the following configuration files to determine the applications and settings that you want to deploy:

infra.config
deployment.config

The following sections describe the configuration file parameters in detail.

infra.config file parameters

Refer to the following table for details about the infra.config file:

Parameter	Description	Example
Docker registry details
IMAGE_REGISTRY_HOST	Specify the host where the Docker registry runs with the BMC container images. For the images that are synchronized to a local Harbor registry, make sure the Harbor registry is set up with HTTPS and set the local repository value to this parameter. Important: Do not specify the host path, specify only the host name.	For BMC repository: IMAGE_REGISTRY_HOST=containers.bmc.com. For a local repository: IMAGE_REGISTRY_HOST= value-investing.cluster3.bmc.com.
IMAGE_REGISTRY_USERNAME	Specify the user name to access the Docker registry.	IMAGE_REGISTRY_USERNAME = symphony.aircooler@summer.hot
Load balancer details
NAMESPACE	Specify a valid Kubernetes namespace to deploy BMC Helix IT Operations Management.	NAMESPACE=dark-helmet
LB_HOST	Specify a URL to create the load balancer host. The BMC Helix Single Sign-on Ingress uses this URL to access the BMC Helix Single Sign-on administration console.
LB_PORT	Specify the port number that the load balancer listens to for accepting the client request. The default value is 443.	LB_PORT=443
TMS_LB_HOST	Specify a URL to create the Tenant Management System (TMS) host. The tenant management system Ingress uses the value of this parameter.	TMS_LB_HOST=tms.mydomain.bmc.com.
DOMAIN	Specify the domain that will be used to create a valid base URL. This value is used to create a valid base URL for tenants in the specified format: $TENANT_NAME-$TENANT_TYPE-$TENANT_ENVIRONMENT.$DOMAIN	DOMAIN=mydomain.bmc.com For example, purplekite-tyrion-dev.mydomain.bmc.com
MINIO_LB_HOST	Specify a URL to create a MinIO storage. This value is used by the MinIO Ingress. Important: If you need access to the MinIo console, provide load balancer URL which has a DNS entry, else keep the value of MINIO_LB_HOST as blank MINIO_LB_HOST="".	MINIO_LB_HOST=minio.mydomain.bmc.com.
MINIO_API_LB_HOST	Specify a URL to create a MinIO storage. All the API based operations are performed using this URL. This URL is also used to create a MinIO bucket.	MINIO_API_LB_HOST=minio-api.mydomain.bmc.com
TENANT_ENVIRONMENT	Specify the environment type. The value that you specify is used to create Tenant URL, BMC DiscoveryURL, and BMC Helix Continuous OptimizationURL. The value that you specify is used to create the tenant URL in the following format: $TENANT_NAME-$TENANT_TYPE-$TENANT_ENVIRONMENT.$DOMAIN For example, purplekite-tyrion-dev.mydomain.bmc.com The value of this parameter depends on the kind of setup that you want to create, such as: dev, qa, or production. Important: Do not use special characters. The value of this parameter is not based on deployment size, such as, compact, small, medium, or large.	TENANT_ENVIRONMENT=dev
Cluster type
CLUSTER_TYPE	Specify the cluster type. If the CLUSTER_TYPE is OpenShift, this parameter can have values openshift or ocp. If you do not set a value, cluster type is treated as Kubernetes cluster. Important: If you do not want to set a value for CLUSTER_TYPE, leave it blank as shown: CLUSTER_TYPE=	CLUSTER_TYPE=openshift
Tenant details
TENANT_NAME	Specify the name of the tenant. The value that you specify is used to create the tenant URL in the following format: $TENANT_NAME-$TENANT_TYPE-$TENANT_ENVIRONMENT.$DOMAIN For example, purplekite-tyrion-dev.mydomain.bmc.com Important: Use only lowercase letters to specify the name of the tenant.	TENANT_NAME=purplekite
TENANT_EMAIL	Specify the email address of the admin user of the primary tenant.	TENANT_EMAIL=abc@bmc.com
TENANT_FIRST_NAME	Specify the first name of the admin user of the primary tenant.	TENANT_FIRST_NAME=Myfirstname
TENANT_LAST_NAME	Specify the last name of the admin user of the primary tenant.	TENANT_LAST_NAME=Mylastname
TENANT_TYPE	Specify a value to uniquely identify different groups within a tenant (TENANT_ENVIRONMENT). The value that you specify is used to create the tenant URL in the following format: $TENANT_NAME-$TENANT_TYPE-$TENANT_ENVIRONMENT.$DOMAIN For example, purplekite-tyrion-dev.mydomain.bmc.com The URL must align with the URL that you created for BMC Discovery. The Discovery URL must be in the following format: disc-$TENANT_TYPE-$TENANT_ENVIRONMENT.$DOMAIN For example, disc-purplekite-tyrion-dev.mydomain.bmc.com	TENANT_TYPE=tyrion
TENANT_COUNTRY	Specify the country where the servers are located or from where you are deploying BMC Helix ITOM. Click here to view a list of the supported country names. Important: Make sure that the value of TENANT_COUNTRY is enclosed within double quotation marks.	TENANT_COUNTRY="Virgin Islands"
SMTP details
SMTP_HOST	Specify a valid host name for the SMTP server. All SMTP mail servers are supported.	SMTP_HOST=mailhost.bmc.com
SMTP_PORT	Specify a value for the port of the SMTP server. Important: Specify only integer values.	SMTP_PORT=25
SMTP_USERNAME	If the SMTP server does not need authentication, set the value of this parameter to false. The default value is true.	SMTP_AUTH_DASHBOARD=true
SMTP_FROM_EMAIL	Specify the authorization value for SMTP server. Use one of the following values: PLAIN If you set the value as PLAIN, it is mandatory to set valid values for SMTP_USER and SMTP_PASSWORD. LOGIN If you set the value as LOGIN, it is mandatory to set valid values for SMTP_USER and SMTP_PASSWORD. NONE Use this value when you want to skip SMTP authentication. If you set the value as NONE, set the user name and password values as shown below: SMTP_USERNAME="" SMTP_PASSWORD="" Important: The values that you specify are case-sensitive.	SMTP_AUTH=PLAIN
SMTP_TLS	Specify a user name to connect to the SMTP server. If SMTP_AUTH value is set to NONE, keep the SMTP_USERNAME and SMTP_PASSWORD values blank: SMTP_USERNAME="" SMTP_PASSWORD=""	SMTP_USERNAME=abc@bmc.com
SMTP_AUTH_DASHBOARD	Specify a valid email ID for the from address in all emails. Important: Special characters are not allowed in an email address.	SMTP_FROM_EMAIL=helix-activation@bmc.com
SMTP_AUTH	If your SMTP server is using TLS certificates, set the value of this parameter to true. If SMTP_TLS is set to true, and the SMTP_HOST certificate is signed by a custom or self-signed CA, make sure that you append the custom or self-signed CA certificate (full CA chain) to the commons/certs/custom_cacert.pem file. The default value is false.	SMTP_TLS=false

OPS_GROUP_EMAIL	Specify a valid email address for your organization's operations team. All emails related to tenant activities such as tenant creation, registration, and offboarding are sent to this email address. Important: Special characters are not allowed in an email address.	OPS_GROUP_EMAIL=abc@bmc.com
APPROVAL_GROUP_EMAIL	Set a valid email address of the approval group that would approve a new tenant. Important: Special characters are not allowed in an email address.	APPROVAL_GROUP_EMAIL=abc@bmc.com
Storage class details
PG_STORAGE_CLASS	Specify a storage class for PostgreSQL. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	PG_STORAGE_CLASS=acme-block-storage
VMSTORAGE_STORAGE_CLASS	Specify a storage class for VictoriaMetrics. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	VMSTORAGE_STORAGE_CLASS=acme-block-storage
VMAGGSTORAGE_STORAGE_CLASS	Specify a storage class. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	VMAGGSTORAGE_STORAGE_CLASS=acme-block-storage
ES_MASTER_STORAGE_CLASS	Specify a storage class for Elasticsearch master nodes. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	ES_MASTER_STORAGE_CLASS=acme-block-storage
ES_DATA_STORAGE_CLASS	Specify a storage class for Elasticsearch data nodes. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	ES_DATA_STORAGE_CLASS=acme-block-storage
MINIO_STORAGE_CLASS	Specify a storage class for MinIO. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	MINIO_STORAGE_CLASS=acme-block-storage
EFS_STORAGE_CLASS	Specify a storage class for Amazon Elastic File System (EFS). SmartGraph uses the dynamic NFS mount storage class. Repeat the same value for all infra services.	EFS_STORAGE_CLASS=acme-nfs-storage
REDIS_HA_GLOBAL_STORAGECLASS	Specify a storage class for REDIS. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	REDIS_HA_GLOBAL_STORAGECLASS=acme-block-storage
REDIS_CLUSTER__STORAGE_CLASS	Specify a storage class for REDISCLUSTER. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.
KAFKA_STORAGECLASS	Specify a storage class for Kafka. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	KAFKA_STORAGECLASS=acme-block-storage
AIOPS_STORAGE_CLASS	Specify a storage class for BMC Helix AIOps. Usually, a single storage class by using block storage is configured for all the infra services. Repeat the same value for all infra services.	AIOPS_STORAGE_CLASS=acme-block-storage
BHAC_STORAGE_CLASS	Specify a storage class for BMC Helix Automation Console. BHAC supports only the NFS storage class. Repeat the same value for all infra services.	BHAC_STORAGE_CLASS=acme-nfs-storage
Optimize storage details
OPT_STORAGE_CLASS	Specify a ReadWriteMany storage class for BMC Helix Continuous Optimization.	OPT_STORAGE_CLASS=acme-opt-storage
Self-signed/Custom CA/Public CA
CUSTOM_CA_SIGNED_CERT_IN_USE	If you are using self-signed or custom CA signed certificate, set the value of the parameter CUSTOM_CA_SIGNED_CERT_IN_USE to true . Name the custom CA certificate file (full chain) as custom_cacert.pem and copy it to the commons/certs/ directory; that is, commons/certs/custom_cacert.pem. Deployment-repository-service (DRS) requires a CA certificate file (full chain). If you set the value of the parameters CUSTOM_CA_SIGNED_CERT_IN_USE to false and MONITOR to yes (in configs/deployment.config ), you must name the public CA certificate file (full chain) as public_cacert.pem and copy it to the commons/certs directory; that is, commons/certs/public_cacert.pem. Additionally, you must add the self-signed or custom CA signed certificate in trust of each worker node. Important: For instructions about using self-signed or custom CA certificates, see Using-custom-CA-signed-certificates. For information about adding a self-signed or custom CA certificate in BMC Discovery, see Integrating with BMC Helix Single Sign-On. The default value is false.	CUSTOM_CA_SIGNED_CERT_IN_USE=false
Service account details
CUSTOM_SERVICEACCOUNT_NAME	If the user running the installation has permission to create ServiceAccount, Role, and RoleBinding, you must retain the CUSTOM_SERVICEACCOUNT_NAME value as helix-onprem-sa. The installer will create the ServiceAccount during installation. If the user running the installation does not have permission to create ServiceAccount, Role, and RoleBinding, perform the following steps: Create a ServiceAccount, Role, and RoleBinding. See Creating-ServiceAccount-Role-and-RoleBinding. Note: If you are creating the service account before the installation, you must not use the default service account name helix-onprem-sa for the new account. Set the value of CUSTOM_SERVICEACCOUNT_NAME to the name of the ServiceAccount that you created.	CUSTOM_SERVICEACCOUNT_NAME=helix-onprem-sa
JAVA keystore
RSSO_CUSTOM_JAVA_KEYSTORE_IN_USE	Use this parameter if you want to integrate BMC Helix Single Sign-on(RSSO) with SAML identity provider (IdP), which requires RSSO to sign SAML assertions. RSSO acts as a SAML service provider. To configure BMC Helix Single Sign-on server as a SAML service provider, see Configuring the BMC Helix SSO server as a SAML service provider . To use custom Java keystore for RSSO SAML keystore configuration, p erform the following steps: Set the RSSO_CUSTOM_JAVA_KEYSTORE_IN_USE variable to true. Save the java_keystore file in the commons/certs directory and r ename it to rsso_custom_java_keystore. During deployment, commons/certs/rsso_custom_java_keystore file is mounted in the RSSO container at the following location: /etc/rsso_custom_java_keystore. For more information about creating a keystore, see Creating and updating the SP signing certificate for SAML authentication The default value is false.	RSSO_CUSTOM_JAVA_KEYSTORE_IN_USE=false
Smart graph details
SMART_SYSTEM_USERNAME	Specify a user name to connect to the BMC Discovery.	SMART_SYSTEM_USERNAME=system
NGINX Controller details
INGRESS_CLASS	Specify the Ingress class to be used while deploying the Ingress controller. The default value is nginx. For BHAC deployment, NGINX Plus is not supported.	INGRESS_CLASS=nginx
NGINX_CONTROLLER new in 24.3	Specify the value as NGINX_PLUS if you are using the F5 NGINX Plus Ingress Controller; else, specify the value as NGINX_OPENSOURCE. The default value is NGINX_OPENSOURCE.	NGINX_CONTROLLER=NGINX_OPENSOURCE
INGRESS_TLS_SECRET_NAME new in 24.3	If you are using the F5 NGINX Plus Ingress Controller, specify the secret that contains the certificate for SSL. The default value is blank.	INGRESS_TLS_SECRET_NAME=my-tls-secret
Binary paths on your system
HELM_BIN	Specify the absolute path of the Helm binary that is supported for the current release.	HELM_BIN=/usr/local/bin/helm
KUBECTL_BIN	Specify the absolute path of the kubectl binary that is supported for the current release.	KUBECTL_BIN=/usr/bin/kubectl
OC_BIN	Specify the absolute path of the OpenShift binary. Important: OC_BIN path should be set if CLUSTER_TYPE is openshift or ocp.	OC_BIN=/usr/local/sbin/oc
Security Context details
RUN_AS_USER	Set the security context that the infrastructure components must use to enforce security. Set this parameter only if the value of the CLUSTER_TYPE variable is openshift or ocp. If the value of the CLUSTER_TYPE variable is kubernetes, set the value of this parameter to null. Set the correct context for this variable according to the OpenShift namespace. For example, in OpenShift namespace, run the following command to get the ID range: oc describe namespace <namespace-name> After you run the command, look for the following line in the output: openshift.io/sa.scc.uid-range : 1000670000/10000. Copy 1000670000 for RUN_AS_USER, RUN_AS_GROUP and FS_GROUP. Important:The command and output changes for each namespace.	RUN_AS_USER=null
RUN_AS_GROUP	Set the security context that the infrastructure components must use to enforce security. Set this parameter only if the value of the CLUSTER_TYPE variable is openshift or ocp. If the value of the CLUSTER_TYPE variable is kubernetes, set the value of this parameter to null. Set the correct context for this variable according to the OpenShift namespace. For example, in OpenShift namespace, run the following command to get the ID range: oc describe namespace <namespace-name> After you run the command, look for the following line in the output: openshift.io/sa.scc.uid-range: 1000670000/10000 Copy 1000670000 for RUN_AS_USER, RUN_AS_GROUP and FS_GROUP. Important: The command and output changes for each namespace.	RUN_AS_GROUP=null
FS_GROUP	Set the security context that the infrastructure components must use to enforce security. Set this parameter only if the value of the CLUSTER_TYPE variable is openshift or ocp. If the value of the CLUSTER_TYPE variable is kubernetes, set the value of this parameter to null. Set the correct context for this variable according to the OpenShift namespace. For example, in OpenShift namespace, run the following command to get the ID range: oc describe namespace <namespace-name> After you run the command, look for the following line in the output: openshift.io/sa.scc.uid-range : 1000670000/10000 Copy 1000670000 for RUN_AS_USER, RUN_AS_GROUP and FS_GROUP. Important: The command and output changes for each namespace.	FS_GROUP=null
OPT_FSGROUP	Specify the value for the Optimize File System Group. For BMC Helix Continuous Optimization, if the value of the CLUSTER_TYPE variable is openshift or ocp, set the value of this parameter to null: OPT_FSGROUP=null If the value of the CLUSTER_TYPE variable is Kubernetes, set the value of this parameter to 1001: OPT_FSGROUP=1001 The default value is 1001.	OPT_FSGROUP=1001
ML_FSGROUP	Specify the value for the File System Group. If the value of CLUSTER_TYPE is openshift or ocp and the value of INSTALL_MODE is fresh, the value of this parameter must be same as the value that you set for the FS_GROUP parameter. If the value of CLUSTER_TYPE is not openshift or ocp and the value of INSTALL_MODE is not fresh , set the value of this parameter to 998: ML_FSGROUP=998 The default value is 998.	ML_FSGROUP=998
ENABLE_PRIORITY_CLASS_SUPPORT	Use this parameter to enable the priority class for data lake and application services. Default value is set to no. Review the Kubernetes documentation to learn about how PriorityClass works. As a cluster admin, create the PriorityClass objects, by running the following script: utilities/priority_class/create_priority_class.sh Set the ENABLE_PRIORITY_CLASS_SUPPORT value to yes. This enables priority in the below order: Infra services application services Minio and victoria-metrics-aggregate-vmstorage-agg Other services, if any	ENABLE_PRIORITY_CLASS_SUPPORT=yes
ENABLE_DEDICATED_NODES_FOR_INFRA	Use this parameter to dedicate nodes to infra components. Default value is set to no. FOr more information, see Preparing for deployment.	ENABLE_DEDICATED_NODES_FOR_INFRA=yes

deployment.config file parameters

Refer to the following table for details about the deployment.config file:

Parameter	Description	Example
DEPLOYMENT_SIZE	Specify your deployment size. Possible values are: compact small medium large itsmcompact itsmsmall extralarge bhaccompact bhacsmall bhacmedium bhaclarge Default value is small. To deploy only BMC Helix Automation Console, use the value as bhaccompact. If you are deploying other products with BHAC, use the general deployment sizes - small, compact, medium, large.	DEPLOYMENT_SIZE=small
Docker registry project details
IMAGE_REGISTRY_PROJECT	The name of the organization within the Docker registry (where the container image repositories are located) is assigned as the value of this parameter. Construct the URL as shown: IMAGE_REGISTRY_HOST/IMAGE_REGISTRY_PROJECT/ IMAGE_REGISTRY_ORG:<Image-name> Example: If the image name of the Docker registry is containers.bmc.com/bmc/, the name of IMAGE_REGISTRY_HOST is containers.bmc.com, and the name of IMAGE_REGISTRY_PROJECT is bmc.	IMAGE_REGISTRY_PROJECT=bmc
CORE_IMAGE_REGISTRY_ORG	The default value of the external repository. The default value is lp0lz.	CORE_IMAGE_REGISTRY_ORG=lp0lz
IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is lp0lz.	IMAGE_REGISTRY_ORG=lp0lz
IA_IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is lp0oz.	IA_IMAGE_REGISTRY_ORG=lp0oz
OPTIMIZE_IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is lp0pz.	OPTIMIZE_IMAGE_REGISTRY_ORG=lp0pz
BHOM_IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is lp0mz.	BHOM_IMAGE_REGISTRY_ORG=lp0mz
AIOPS_IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is la0cz.	AIOPS_IMAGE_REGISTRY_ORG=la0cz
BHAC_IMAGE_REGISTRY_ORG	The default value of the external (public facing) repository. The default value is lpdbt.	BHAC_IMAGE_REGISTRY_ORG=lpdbt
Installation mode details
INSTALL_MODE	Set the value of INSTALL_MODE to fresh for a new deployment of BMC Helix ITOM. Set the value of INSTALL_MODE to upgrade to upgrade BMC Helix ITOM. The default value is fresh.	INSTALL_MODE=fresh
Infrastructure service installation
INFRA	Set the value of INFRA to yes to deploy all the infra services. The default value is yes .	INFRA=yes
Individual infra services installation
_PTPOSTGRESS	Set the value of _PTPOSTGRESS to yes to deploy PostgreSQL database. The default value is yes .	_PTPOSTGRESS=yes
_KAFKA	Set the value of _KAFKA to yes to deploy Kafka. The default value is yes .	_KAFKA=yes
_REDISCLUSTER	Set the value of _REDISCLUSTER to yes to deploy Redis cluster. The default value is yes. During Fresh deployment: If _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then both redis-cluster and redis-ha are deployed 2. _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed. 3. _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then redis is not deployed 4. _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then only redis-ha is deployed. During upgrade: If Redis-ha is already deployed, and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then only redis-cluster is deployed because redis-ha already exist. If Redis-ha already deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then redis-ha remains same. If Redis-ha already deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed, and redis-ha remains same. Redis-ha already deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then redis-ha remains same. Redis-ha is not deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed. Redis-ha is not deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then only redis-ha is deployed. Redis-ha is not deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then no redis is deployed. Redis-ha not deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then both redis are deployed.	_REDISCLUSTER=yes
_RSSO	Set the value of _RSSO to yes to deploy RSSO. The default value is yes.	_RSSO=yes
_VICTORIAMETRICS	Set the value of _VICTORIAMETRICS to yes to deploy VictoriaMetrics. The default value is yes.	_VICTORIAMETRICS=yes
_ELASTICSEARCH	Set the value of _ELASTICSEARCH to yes to deploy Elasticsearch. The default value is yes.	_ELASTICSEARCH=yes
_MINIO	Set the value of _MINIO to yes to deploy MinIO. The default value is yes.	_MINIO = yes
Product services details
HELIX_DASHBOARD_SERVICES	Set the value of HELIX_DASHBOARD_SERVICES to yes to deploy BMC Helix Dashboards. The default value is yes. During Fresh deployment: If _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then both redis-cluster and redis-ha are deployed 2. _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed. 3. _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then redis is not deployed 4. _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then only redis-ha is deployed. During upgrade: If Redis-ha is already deployed, and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then only redis-cluster is deployed because redis-ha already exist. If Redis-ha already deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then redis-ha remains same. If Redis-ha already deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed, and redis-ha remains same. Redis-ha already deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then redis-ha remains same. Redis-ha is not deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=no, then only redis-cluster is deployed. Redis-ha is not deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=yes, then only redis-ha is deployed. Redis-ha is not deployed and _REDISCLUSTER=no and HELIX_DASHBOARD_SERVICES=no, then no redis is deployed. Redis-ha not deployed and _REDISCLUSTER=yes and HELIX_DASHBOARD_SERVICES=yes, then both redis are deployed.	HELIX_DASHBOARD_SERVICES=yes
ITSMINSIGHT_SERVICES	Set the value of ITSMINSIGHT_SERVICES to yes to deploy BMC Helix IT Service Management . The default value is no.	ITSMINSIGHT_SERVICES=no
AIOPS_SERVICES	Set the value of AIOPS_SERVICES to yes to deploy BMC Helix AIOps. The default value is no.	AIOPS_SERVICES=no
MONITOR	Set the value of MONITOR to yes to deploy BMC Helix Operations Management. Important: If you set the value of the parameters CUSTOM_CA_SIGNED_CERT_IN_USE to false and MONITOR to yes, you must name the public CA certificate file (full chain) as public_cacert.pem and copy it to the commons/certs directory; that is, commons/certs/public_cacert.pem. The default value is no.	MONITOR=no
LOG_ANALYTICS_SERVICES	Set the value of LOG_ANALYTICS_SERVICES to yes to deploy BMC Helix Log Analytics and BMC Helix Developer Tools. The default value is no.	LOG_ANALYTICS_SERVICES=no
INTELLIGENT_AUTOMATION	Set the value of INTELLIGENT_AUTOMATION to yes to deploy BMC Helix Intelligent Automation. The default value is no.	INTELLIGENT_AUTOMATION=no
OPTIMIZE	Set the value of OPTIMIZE to yes to deployBMC Helix Continuous Optimization. The default value is no.	OPTIMIZE=no
ARSERVICES	Set the value of ARSERVICES to yes to specify whether the BMC Helix Innovation Suite jobs are created as part of the installation. Set the value of ARSERVICES to no if you are using only BMC Helix IT Operations Management. The default value is no.	ARSERVICES=no
AUTOANAMOLY	The auto anomaly services are part of BMC Helix Operations Management and BMC Helix AIOps. To enable the automatic generation of anomaly events, set the value of the AUTOANAMOLY parameter to yes. The default value is no. For more information, see Autoanomalies in the BMC Helix Operations Management documentation.	AUTOANAMOLY=no
AUTOMATION_CONSOLE	Set the value of AUTOMATION_CONSOLEto yes to deploy BMC Helix Automation Console. The default value is no.	AUTOMATION_CONSOLE=no

To know more about configurations specific to each component, see the following sample configuration files:

Configuration file settings

infra.config file parameters

NGINX Controller details

deployment.config file parameters

On this page