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.

Related topic
Load balancer requirements Open link

infra.config file parameters



ParameterDescriptionExample
Docker registry details

IMAGE_REGISTRY_HOST


Specify the host where the Docker registry is running 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_USERNAMESpecify the user name to access the Docker registry.IMAGE_REGISTRY_USERNAME = symphony.aircooler@summer.hot 
Infrastructure details
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 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.
ENVIRONMENT=dev
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. 

If the value of the  CUSTOM_CA_SIGNED_CERT_IN_USE  parameter is  true,
use the DNS that is configured for self-signed certificate.

If the value of the CUSTOM_CA_SIGNED_CERT_IN_USE  parameter is   false ,
use the DNS that is configured for the CA signed certificate. 

If the value of  CUSTOM_CA_SIGNED_CERT_IN_USE
parameter is true,
LB_HOST=lb.mydomain.bmc.com. 

If the value of  CUSTOM_CA_SIGNED_CERT_IN_USE
parameter is false,
LB_HOST=max-india-app.acme.bmc.com.

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 value of this parameter is used by t
he tenant management system ingress.

If the value of the CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true,
use the Domain Namer Server (DNS) that is configured for self-signed certificate.

If the value of the CUSTOM_CA_SIGNED_CERT_IN_USE parameter is false,
use the DNS that is configured for the CA signed certificate.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true, TMS_LB_HOST=tms.mydomain.bmc.com.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is false,
TMS_LB_HOST=max-india-api.acme.bmc.com.

DOMAIN

Specify the URL for the domain of the load balancer .
This value is used to create a valid base URL for tenants and needs a wildcard certificate.
Having a wildcard certificate helps you to create multiple URLs.

DOMAIN=mydomain.bmc.com
MINIO_LB_HOST

Specify a URL to create a  MinIO storage. This value is used by the MinIO Ingress. 

If the value of the CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true,
use the DNS that is configured for self-signed certificate.

If the value of the CUSTOM_CA_SIGNED_CERT_IN_USE parameter is  false ,
use the DNS that is configured for the CA signed certificate.

Important: 

If you need access to the Minio console, then provide load balancer URL which has a DNS entry, else keep the value of  MINIO_LB_HOST  as blank MINIO_LB_HOST="".

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true, MINIO_LB_HOST=minio.mydomain.bmc.com.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is false,
MINIO_LB_HOST=minio-private-poc.acme.bmc.com.

MINIO_API_LB_HOST RECENTLY ADDED

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

KIBANA_LB_HOST

Specify a URL to create a Kibana load balancer host. 
The BMC Helix Logging ingress uses the value of this parameter. 
The value of this parameter depends on the self-signed/CA-signed certificate or
CA custom certificate. 
 

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true,
use the DNS configured for the self-signed/CA-signed certificate.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is false,
use the DNS configured for the CA custom certificate.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is true ,
KIBANA_LB_HOST= kibana-private-poc.mydomain.com.

If the value of CUSTOM_CA_SIGNED_CERT_IN_USE parameter is false,
KIBANA_LB_HOST = kibana-private-poc.mydomain.acme.com.

Cluster details
CLUSTER_TYPESpecify the cluster type. 

If the CLUSTER_TYPE is O penShift,  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 for onboarding
COMPANY_NAME

Specify the name of the tenant.

The value that you specify is used to create the tenant URL in the following format:
$COMPANY_NAME-private-$ENVIRONMENT.$DOMAIN

Important: Use only lowercase letters to specify the name of the tenant.

COMPANY_NAME=bmc
TENANT_EMAILSpecify the email address of the admin user of the primary tenant.
  
TENANT_EMAIL=abc@bmc.com
TENANT_FIRST_NAMESpecify the first name of the admin user of the primary tenant.
  
TENANT_FIRST_NAME=Myfirstname
TENANT_LAST_NAMESpecify 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 (COMPANY_NAME).


The value that you specify is used to create the tenant URL
and it must align with the URL that you created for BMC Discovery.

TENANT_TYPE=bhom
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 COUNTRY is enclosed within double quotation marks.

COUNTRY="Virgin Islands"
SMTP Config details
SMTP_HOSTSpecify 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_AUTH

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_USERNAME

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_FROM_EMAIL

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_TLS

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 who 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 Postgres.
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
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-block-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
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
ESLOG_MASTER_STORAGE_CLASS

Specify an Elasticsearch storage class log for master.
Usually, a single storage class by using block storage is configured for all the infra services.

Repeat the same value for all infra services.

ESLOG_MASTER_STORAGE_CLASS=acme-block-storage
ESLOG_DATA_STORAGE_CLASS

Specify an Elasticsearch storage class log for data.
Usually, a single storage class by using block storage is configured for all the infra services.

Repeat the same value for all infra services.

ESLOG_DATA_STORAGE_CLASS=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
VMAGGSTORAGE_STORAGE_CLASS

Specify a storage class for NFS Storage.
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
Optimize storage details
OPT_STORAGE_CLASS

Specify a  ReadWriteMany  storage class for BMC Helix Continuous Optimization .

OPT_STORAGE_CLASS=acme-opt-storage
Certificate details
CUSTOM_CA_SIGNED_CERT_IN_USE

Set the value of this parameter to true if you are using a self-signed or custom CA certificate.

If the public CA you are using is not present in the commons/certs/non_java_cacerts.crt file, set this parameter to true.

Important:

  • For instructions about using a 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 Open link .


The default value is false.

CUSTOM_CA_SIGNED_CERT_IN_USE=false
CUSTOM_SERVICEACCOUNT_NAME

If you have permission to create ServiceAccount, Role, and RoleBinding, retain the
CUSTOM_SERVICEACCOUNT_NAME value as 
helix-onprem-sa. 
The installer will create the ServiceAccount during installation.


If you do not have permission to create ServiceAccount, Role, and RoleBinding, perform the following steps:

  1. Create a ServiceAccount, Role, and RoleBinding. See Creating ServiceAccount, Role, and RoleBinding.
  2. Assign the ServiceAccount that you created to CUSTOM_SERVICEACCOUNT_NAME. 
CUSTOM_SERVICEACCOUNT_NAME=helix-onprem-sa
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 Open link
.


To use custom Java keystore for RSSO SAML keystore configuration,
p
erform the following steps:

  1. Set the RSSO_CUSTOM_JAVA_KEYSTORE_IN_USE variable to true.
  2. 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 Open link


The default value is false.

RSSO_CUSTOM_JAVA_KEYSTORE_IN_USE=false 
Deployment Repository Service client root cert

CLIENT_ROOT_CERT



Important: This parameter is available only after you apply the hotfix  itom-drs-predeploy-hotfix-23.2.02.002-2 or itom-predeploy-hotfix-23.2.02.002-6 .
For more information about downloading the hotfixes and the prerequisites to apply them, see  Downloading the deployment manager

Specify the value for Deployment Repository Service client root cert.

The value of this parameter should be the root CA certificate of the load balancer.

If the MONITOR parameter in the deployment.config file is set to yes, the value of this parameter is required.

Example scenario: To download the root CA certificate for google.com from the Chrome browser:

  1. Open google.com in a Chrome browser instance.
  2. Click the lock icon on the address bar and select Connection is secure  >  Certificate is valid.
  3. In Certificate Viewer window, go to the  Details  tab.
    The first certificate in the Certificate Hierarchy is the root CA certificate.
  4. Click the first entry (www.google.com) in the  Certificate Hierarchy  list and click  Export.
  5. Browse to the location of your choice and save the certificate.
  6. Copy the certificate to a Linux computer and run the following command: 

    $ cat </path/to/the/certificate/file> | grep -iv "certificate" | tr [:space:] ' '  | tr -d ' '

  7. Make sure that the remaining content in the certificate is in a single line.

  8. Set this single line as a value for the  CLIENT_ROOT_CERT  variable.


Important:

Ensure that the value of CLIENT_ROOT_CERT is enclosed within double quotation mark.

CLIENT_ROOT_CERT=""
Discovery details
SMART_SYSTEM_USERNAME

Specify a user name to connect to the BMC Discovery.

SMART_SYSTEM_USERNAME=system

Ingress class details
INGRESS_CLASS

Specify the Ingress class to be used while you are deploying Ingress controller.

The default value is nginx.

INGRESS_CLASS=nginx
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

OpenShift details
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 used by infra components
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

The BMC Helix Continuous Optimization security context

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
Login details
LOGIN_ID

Specify a value for Login ID for the Helix portal.

If the value of the ITSMINSIGHT_SERVICES parameter in the deployment.config file is set to no,
set the value of login ID as admin:
LOGIN_ID=admin

If the value of the ITSMINSIGHT_SERVICES parameter in the deployment.config file is set to yes ,
set the value of login ID as
hannah_admin:
LOGIN_ID=hannah_admin

LOGIN_ID=hannah_admin

Individual infra services installation 



deployment.config file parameters

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

ParameterDescriptionExample
DEPLOYMENT_SIZE

Specify your deployment size.

Possible values are:

  • compact
  • small
  • medium
  • large
  • itsmcompact
  • itsmsmall
  • extralarge

Default value is small.

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

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

_REDIS RECENTLY ADDED

Set the value of _REDIS to yes to deploy Redis.

The default value is yes.
_REDIS=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  RECENTLY ADDED

Set the value of _ELASTICSEARCH to yes to deploy Elasticsearch.

The default value is yes.
_ELASTICSEARCH=yes

_MINIO RECENTLY ADDED

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.

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.

The default value is no.

MONITOR=no
INTELLI_INT_SERVICES

Setting the  INTELLI_INT_SERVICES  flag to  yes results in the installation of BMC Helix Developer Tools.

Important:

If you want to install the on-premises version of
BMC Helix Intelligent Integrations
, you must install the BMC Helix Intelligent Integrations gateway.
For more information, see  Deploying the BMC Helix Intelligent Integrations on-premises gateway Open link
in the BMC Helix Intelligent Integrations documentation.

The default value is no.

INTELLI_INT_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
BMC_HELIX_LOGGING

The default value is no

BMC_HELIX_LOGGING=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

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

Comments