Configuring the params.ini file

Edit online

The installation process needs a configuration parameters file called params.ini that contains variables essential for a successful deployment. The params.ini file defines the environment-specific settings that the installation script uses to configure your Concert, Concert Workflows, and Concert Data Apps instances. The params.ini file adheres to a standard .ini file format, comprising key-value pairs that store essential configuration settings.

The $INSTALL_DIR/etc/sample-params/ directory contains a set of sample files, each corresponding to a specific installation type. The all-params.ini file lists all the possible parameters that can be used for installation on VM and Kubernetes environments.

Sample params.ini files

Refer to the following table for the sample params.ini files that apply to your installation type (VM or Kubernetes).

Installation type	params.ini file name for VM	params.ini file name for Kubernetes
Concert, Concert Workflows, and Concert Data Apps	concert-dataapps-workflows-vm-quickstart-params.ini	concert-dataapps-workflows-k8s-params.ini
Concert and Concert Workflows	concert-workflows-vm-quick-start-params.ini	concert-workflows-k8s-quickstart-params.ini
Concert and Concert Data Apps	concert-dataapps-vm-quickstart-params.ini	concert-dataapps-k8s-quickstart-params.ini
Concert	concert-vm-quick-start-params.ini	concert-k8s-quick-start-params.ini
Concert Workflows	workflows-quickstart-vm-params.ini	workflows-quickstart-k8s-params.ini
Concert Data Apps	dataapps-vm-quick-start-params.ini	dataapps-k8s-quickstart-params.ini

Parameters for installing on a VM

Refer to the following table for the list of parameters for installing on a VM.

Table 1. List of parameters for installing on a VM
Parameter	Description
`INSTALL_VM`	The specified configuration parameter determines the deployment environment for the application. If set to true, it indicates that the installation is being performed on a VM. Conversely, if this option is not set or is set to false, the deployment will be executed on a Kubernetes cluster. This setting is crucial in distinguishing between the two deployment environments, ensuring that the application is properly configured and installed according to the chosen environment.
`INSTALL_CONCERT`	The `INSTALL_CONCERT` parameter is a configuration option that controls whether Concert should be installed as part of the deployment process. If set to true, Concert will be installed, while a value of false or keeping blank this variable will result in Concert not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert based on specific requirements or use cases.
`INSTALL_DATAAPPS`	The `INSTALL_DATAAPPS` parameter is a configuration option that controls whether Concert Data Apps should be installed as part of the deployment process. If set to true, Concert Data Apps will be installed, while a value of false or keeping blank this variable will result in Concert Data Apps not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert Data Apps based on specific requirements or use cases.
`INSTALL_WORKFLOWS`	The `INSTALL_WORKFLOWS` parameter is a configuration option that controls whether Concert Workflows should be installed as part of the deployment process. If set to true, Concert Workflows will be installed, while a value of false or keeping blank this variable will result in Concert Workflows not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert Workflows based on specific requirements or use cases.
`INSTALL_SECURECODER`	The `INSTALL_SECURECODER` parameter is a configuration option that controls whether Secure Coder should be installed as a part of the deployment process. By default, this parameter is set to false, which means Secure Coder is disabled. If set to true, Secure Coder will be enabled, providing integration with Mend for security and vulnerability scanning.
`REG_USER`	This flag is used to specify the user for the registry. By default, this user is set to `cp`, indicating that if no alternative user is specified, `cp` will be used as the default registry user.
`IMAGE_REGISTRY_PREFIX`	Specifies the registry where container images are hosted, serving as a crucial indicator for image storage and retrieval. By default, the value is set to `cp.icr.io/cp`, which points to a specific registry location. This default value can be modified to point to a different registry if needed, allowing for flexibility in managing container images across various environments.
`SKIP_DISK_SPACE_CHECK`	By default, when you run the installation script on a VM, the installation script checks for sufficient free disk space on a VM to ensure a successful installation. To skip this check, you can set the parameter to `TRUE`. This allows the installation to proceed without verifying the available disk space.
HUB parameters
`HUB_URL`	Optional: The `HUB_URL` parameter is a configuration setting that specifies the URL of an existing Hub. This parameter is used when installing the products to an existing Hub, rather than installing a fresh Hub instance. This means that the installation process will not include the setup of a fresh Hub instance. Instead, the system will be configured to connect to an existing Hub at a specified URL. If the `HUB_URL` is empty, then Hub will be installed with the deployment.
`HUB_IMAGE_REGISTRY_SUFFIX`	This flag indicates the registry where the Hub images are hosted. The `params.ini` file has a default image registry suffix value of `/platform-hub`. You should not modify this value, as `/platform-hub` is a fixed setting for your installation.
`HUB_ACCESS_KEY`	Optional: The `HUB_ACCESS_KEY` parameter is a required configuration setting when the `HUB_URL` is set. This means that if the `HUB_URL` is provided, The `HUB_ACCESS_KEY` must also be specified in order to authenticate and authorize access to the existing Hub.
`HUB_HTTPS_PORT`	Optional: The `HUB_HTTPS_PORT` is a configuration setting that specifies the port number used for secure access to the Hub. A default HTTPS port for Hub is set to 12443. You can customize this port by setting a different port number, if required.
`ENABLE_CROSS_PRODUCT_INTEGRATION`	The `ENABLE_CROSS_PRODUCT_INTEGRATION` parameter is a configuration option that controls whether ITOM should be enabled as a part of the deployment process. By default, this parameter is set to false, which means ITOM is disabled. If set to true, ITOM will be installed with the HUB in the same namespace. Note: ITOM will use the same configuration as Hub (namespace, scale config, storage class, and build tag).
`HUB_SYSTEMD_ENABLE`	The `HUB_SYSTEMD_ENABLE` parameter is used to control whether systemd should be enabled in Hub. To enable systemd, set the value of `HUB_SYSTEMD_ENABLE` to `y`.
Concert parameters
`CONCERT_IMAGE_REGISTRY_SUFFIX`	Indicates the registry where the Concert images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
Concert Data Apps parameters
`DATAAPPS_IMAGE_REGISTRY_SUFFIX`	Indicates the registry where the Concert Data Apps images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
Concert Workflows parameters
`WORKFLOWS_INSTANCE_ADDRESS`	Indicates the instance address, which is the fully qualified domain name (FQDN) (e.g., `hostname.domain.com`) of the VM where Concert Workflows is hosted. To find the FQDN, you can use commands such as `hostname -f` on Linux® systems, which returns the FQDN of the host. The FQDN is a complete domain name for a host on a network, and it includes both the hostname and the domain name. For example, if the hostname of your VM is `concert-vm` and it is part of the domain `example.com`, the FQDN would be `concert-vm.example.com`.
`WORKFLOWS_ENABLE_FAAS`	Optional: The `WORKFLOWS_ENABLE_FAAS` parameter is an optional configuration setting that controls whether FaaS functionality is enabled for Concert Workflows. By default, this parameter is set to true, which means FaaS functionality is enabled. If required, you can set to false, then the FaaS functionality will be disabled. This parameter allows for flexibility in Concert Workflows configuration, enabling or disabling FaaS support based on specific requirements or use cases. Note: In Concert Workflows installation on a Power (ppc64le) VM and instances where Istio is enabled, the FaaS workflow integration is not supported.
`WORKFLOWS_FAAS_NS`	Optional: The `WORKFLOWS_FAAS_NS` parameter is utilized to specify the namespace for FaaS components. By default, this namespace is set to faas. If required, you can set the FaaS namespace value.
`WORKFLOWS_ENABLE_ISTIO`	Optional: The `WORKFLOWS_ENABLE_ISTIO` parameter is an optional configuration setting that controls whether Istio is enabled for mutual Transport Layer Security (mTLS). By default, this parameter is set to false, which means Istio is disabled. If set to true, Istio will be enabled, providing mTLS capabilities for secure communication between services.
`WORKFLOWS_NS`	Optional: Specifies the namespace where Concert Workflows will be installed. By default, the Concert Workflows will be installed in the `concert-workflows` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`WORKFLOWS_OVERRIDE_VALUES`	Optional: Indicates the file path of the `custom values` configuration file created, which is used to customize AI model settings.
`WORKFLOWS_INSTALL_ALL_INTEGRATIONS`	Optional: To install all integrations, leave this parameter unset or set it to true. To install only the most commonly-used integrations, set this parameter to false. To install a customized set of integrations, set this parameter to false, edit the ibm-concert/ibm-concert-std-workflows/charts/rna-core/files/integrations.cfg file, and for each integration that you want to install, remove the leading hash (#) character.
`WORKFLOWS_FLOW_PAUSE_ENABLED`	By default, this parameter is set to true. It enables a Concert Workflows worker to pause its running workflows and save the workflow state to the database before it is terminated. To force workers to complete their workflows before termination, set this parameter to false.
`WORKFLOWS_TERMINATION_TIMEOUT`	Before a Concert Workflows worker is terminated, it pauses the workflows that it is running. To prevent workflows from being paused indefinitely, a timeout period is applied. If a workflow is still paused when the timeout is reached, the workflow is terminated. Use this parameter to define the termination timeout period in seconds for local workers. The default timeout period is 1800 seconds (30 minutes).
`WORKFLOWS_USER_WORKER_TOKEN_DURATION`	When a worker runs a workflow, it generates a user-scoped token to impersonate the user that triggered the workflow. The worker uses this token to fetch workflow definitions and authentication objects. Use this parameter to define the validity period of the token. The default validity period is 3600 seconds (1 hour).
Secure Coder parameters
`SECURECODER_IMAGE_REGISTRY_SUFFIX`	Indicates the registry where the Securecoder images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
`SECURECODER_NS`	Optional: Specifies the namespace where Securecoder will be installed. By default, the Securecoder will be installed in the `concert-securecoder` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`ENABLE_BUDDY`	If you want to enable Concert Buddy to use the Secure Coder browser experience, set this value to `true` or set it to `false` to disable it. By default, Concert Buddy is disabled.
`FILE_STORAGE_CLASS_CONCERT`	If `ENABLE_BUDDY` is `true`, set this value to pass the storage class name for Concert.
`SECURECODER_MEND_ENABLED`	Secure Coder offers a workspace scans feature, which utilizes the MendCLI tool to provide Static Application Security Testing (SAST) and Software Composition Analysis (SCA) scans. By default, this parameter is set to false, which means Mend scanning is disabled. If set to true, enables Mend SAST or OSS scanner integration.
`SECURECODER_MEND_ORG_NAME`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the Mend organiszation name. This is the organization identifier in your Mend account, for example: my-company-org.
`SECURECODER_MEND_PRODUCT_NAME`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the Mend product name.
`SECURECODER_MEND_SERVICE_URL`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the Mend service endpoint URL, for example: `https://app.mend.io`.
`SECURECODER_MEND_EMAIL_ADDRESS`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the email address associated with your Mend account, for example: `security-team@company.com`.
`SECURECODER_MEND_PROJECT_NAME`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the name of the Mend project associated with the deployment.
`WATSONX_API_URL`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the URL of the watsonx.ai instance, for example: `https://us-south.ml.cloud.ibm.com`.
`WATSONX_API_PROJECT_ID`	If `SECURECODER_MEND_ENABLED` is `true` and your chosen provider is `watsonx`, set this value to the ID of the watsonx.ai project that you want to use.
`WATSONX_API_MODEL_ID`	Optional: If `SECURECODER_MEND_ENABLED` is `true` and your chosen provider is `watsonx`, you can set this value to the watsonx.ai model that is used. The default value for this attribute is `"ibm/granite-4-h-small"`, which represents IBM's Granite-4.0-H-Small model.
AI configuration parameters
`ENABLE_AI`	Set this value to `true` to enable the AI assistant or to `false` to disable it. By default, the assistant is disabled.
`LLM_PROVIDER`	The large language model (LLM) provider that you want to use. You can specify one of the following values: `watsonx` `vllm` By default, this parameter’s value is set to `watsonx`. Note: If your chosen provider is `watsonx`, you must specify values for the `WATSONX_API_URL`, `WATSONX_API_PROJECT_ID`, and `WATSONX_API_USER` parameters. If your chosen provider is `vllm`, you must specify values for the `LLM_MODEL`, `EMBED_MODEL`, and `LLM_BASE_URL` parameters.
`WATSONX_API_URL`	If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, set this value to the URL of the on-premises or SaaS watsonx.ai instance, for example: `https://your-cp4d-cluster.example.com` (for an on-premises watsonx.ai instance). `https://us-south.ml.cloud.ibm.com` (for a SaaS watsonx.ai instance).
`WATSONX_API_PROJECT_ID`	If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, set this value to the ID of the watsonx.ai project that you want to use.
`WATSONX_API_USER`	Your Concert license entitles you to use an instance of watsonx.ai via IBM Cloud Pak for Data. If `ENABLE_AI` is `true`, your chosen provider is `watsonx`, and you want to connect to this instance, set this value to the username that IBM Cloud Pak for Data uses to authenticate to the watsonx.ai instance.
`WATSONX_API_MODEL_ID`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, you can set this value to the watsonx.ai model that is used. The default value for this attribute is `"ibm/granite-4-h-small"`, which represents IBM's Granite-4.0-H-Small model.
`WATSONX_API_VERSION`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, you can set this value to the IBM watsonx.ai version that is used. The default value, and only valid value, is "2024-03-14".
`WATSONX_API_INSTANCE_ID`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, and the watsonx.ai instance is a dedicated one, you can set this value to the instance ID.
`LLM_MODEL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the name of the vLLM-provided model that you want to use for generating workflows. Only IBM Granite and Mistral AI models are supported, and the following models are recommended: IBM’s Granite-4.1-30B model. To use this model, set this value to `“ibm-granite/granite-4.1-30b“`. Mistral AI’s Mistral Small 4 model. To use this model, set this value to `“mistralai/Mistral-Small-4“`.
`EMBED_MODEL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the name of the vLLM-provided text embedding model that you want to use. Embedding models use vector-based comparisons between embedded prompts, block descriptions, and documentation to retrieve the most relevant blocks and documentation extracts in response to prompts. Only IBM Granite Embedding models are supported, and the Granite-Embedding-125m-English model is recommended. To use this model, set this value to `“ibm-granite/granite-embedding-125m-english“`.
`LLM_BASE_URL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the URL of the vLLM-provided model instance, for example: `https://ml-serving.example.com:8443`

Parameters for installing on Kubernetes

Refer to the following table for the list of parameters for installing on a Kubernetes cluster.

Table 2. Parameters for installing on Kubernetes
Parameter	Description
`INSTALL_EKS`	Set the value to true or false. The flag `INSTALL_EKS` determines whether the installation should proceed on an EKS cluster or an OCP cluster. If you unset the parameter or setting the value to `false` indicates that the installation should be performed on an OCP cluster instead of an EKS cluster. Set the value `INSTALL_EKS=true`, if you want to install these applications on an EKS cluster.
`INSTALL_CONCERT`	The `INSTALL_CONCERT` parameter is a configuration option that controls whether Concert should be installed as part of the deployment process. If set to true, Concert will be installed, while a value of false or keeping blank this variable will result in Concert not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert based on specific requirements or use cases.
`INSTALL_DATAAPPS`	The `INSTALL_DATAAPPS` parameter is a configuration option that controls whether Concert Data Apps should be installed as part of the deployment process. If set to true, Concert Data Apps will be installed, while a value of false or keeping blank this variable will result in Concert Data Apps not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert Data Apps based on specific requirements or use cases.
`INSTALL_WORKFLOWS`	The `INSTALL_WORKFLOWS` parameter is a configuration option that controls whether Concert Workflows should be installed as part of the deployment process. If set to true, Concert Workflows will be installed, while a value of false or keeping blank this variable will result in Concert Workflows not being installed. This setting allows for flexibility in the installation process, enabling or disabling the installation of Concert Workflows based on specific requirements or use cases.
`REG_USER`	This flag is used to specify the user for the registry. By default, this user is set to `cp`, indicating that if no alternative user is specified, `cp` will be used as the default registry user.
`IMAGE_REGISTRY_PREFIX`	The flag is used to specify the registry where container images are hosted, serving as a crucial indicator for image storage and retrieval. By default, the value is set to `cp.icr.io/cp`, which points to a specific registry location. This default value can be modified to point to a different registry if needed, allowing for flexibility in managing container images across various environments. This provides a reference point for the system to locate and access the required container images.
Hub parameters
`HUB_URL`	Optional: The `HUB_URL` parameter is a configuration setting that specifies the URL of an existing Hub. This parameter is used when installing the products to an existing Hub, rather than installing a fresh Hub instance. This means that the installation process will not include the setup of a fresh Hub instance. Instead, the system will be configured to connect to an existing Hub at a specified URL. If The `HUB_URL` is empty, then Hub will be installed with the deployment.
`HUB_HTTPS_PORT`	Optional: The `HUB_HTTPS_PORT` is a configuration setting that specifies the port number used for secure access to the Hub. A default HTTPS port for Hub is set to 12443. You can customize this port by setting a different port number, if required.
`HUB_ACCESS_KEY`	Optional: The `HUB_ACCESS_KEY` parameter is a required configuration setting when the `HUB_URL` is set. This means that if the `HUB_URL` is provided, the `HUB_ACCESS_KEY` must also be specified in order to authenticate and authorize access to the existing Hub.
`HUB_NS`	Specifies the Kubernetes namespace where Hub will be installed. By default, Hub will be installed in the `platform-hub` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`HUB_IMAGE_REGISTRY_SUFFIX`	This flag indicates the registry where the Hub images are hosted. The `params.ini` file has a default image registry suffix value of `/solis-hub`. You should not modify this value, as `/solis-hub` is a fixed setting for your installation.
`SCALE_CONFIG_HUB`	Optional: This flag is used to set the scaling configuration level for a Hub instance. The default value for this flag is `level_1`, but it can be adjusted to `level_2`, `level_3` or `level_4` as needed. This allows users to control the scaling of their Hub instance, with higher levels providing more resources and capacity.
`STORAGE_CLASS_HUB`	This flag sets the storage class for storing Hub data. Add the storage class name where the data is stored. Specify the storage class name you are using to store Hub data.
Concert parameters
`CONCERT_NS`	Specifies the Kubernetes namespace where Concert will be installed. By default, Concert will be installed in the `concert` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`CONCERT_IMAGE_REGISTRY_SUFFIX`	This flag indicates the registry where the Concert images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
`SCALE_CONFIG_CONCERT`	Optional: This flag sets the scaling configuration level for Your Concert instance. The default value for this flag is `level_1`, but it can be adjusted to `level_2`, `level_3` or `level_4` as needed. For more information, refer to Scaling resources for a Kubernetes deployment.
`STORAGE_CLASS_CONCERT`	This flag sets the storage class for storing Concert data. Give the storage class name you are using to store Concert data.
Concert Data Apps parameters
`DATAAPPS_NS`	Specifies the Kubernetes namespace where Concert Data Apps will be installed. By default, Concert Data Apps will be installed in the `concert-dataapps` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`DATAAPPS_IMAGE_REGISTRY_SUFFIX`	This flag indicate the registry where the Concert Data Apps images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
`SCALE_CONFIG_DATAAPPS`	Optional: This flag sets the scaling configuration level for your Concert Data Apps instance. The default value for this flag is `level_1`. Concert Data Apps only supports `level_1` scale configuration.
`STORAGE_CLASS_DATAAPPS`	This flag sets the storage class for storing Concert Data Apps data. Give the storage class name you are using to store Concert Data Apps data.
Concert Workflows parameters
`WORKFLOWS_NS`	Specifies the Kubernetes namespace where Concert Workflows will be installed. By default, Concert Workflows will be installed in the `concert-workflows` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`WORKFLOWS_IMAGE_REGISTRY_SUFFIX`	This flag indicates the registry where the Concert Workflows images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
`WORKFLOWS_INSTANCE_ADDRESS`	The flag indicates the Concert Workflows instance address, which is the fully qualified domain name (FQDN) of the cluster where Concert Workflows is hosted. An example of this address would be `hostname.domain.com`. To find the FQDN, you can use commands such as `hostname -f` on Linux systems, which returns the FQDN of the host. The FQDN is a complete domain name for a host on a network, and it includes both the hostname and the domain name.
`WORKFLOWS_ENABLE_FAAS`	Optional: The `WORKFLOWS_ENABLE_FAAS` parameter is an optional configuration setting that controls whether FaaS functionality is enabled for Concert Workflows. By default, this parameter is set to true, which means FaaS functionality is enabled. If required, you can set to false, then the FaaS functionality will be disabled. This parameter allows for flexibility in Concert Workflows configuration, enabling or disabling FaaS support based on specific requirements or use cases. Note: In Concert Workflows instances where Istio is enabled, the FaaS workflow integration is not supported.
`WORKFLOWS_FAAS_NS`	Optional: The `WORKFLOWS_FAAS_NS` parameter is utilized to specify the namespace for FaaS components. By default, this namespace is set to faas. If required, you can set the FaaS namespace value.
`WORKFLOWS_ENABLE_ISTIO`	Optional: The `WORKFLOWS_ENABLE_ISTIO` parameter is an optional configuration setting that controls whether Istio is enabled for mutual Transport Layer Security (mTLS). By default, this parameter is set to false, which means Istio is disabled. If set to true, Istio will be enabled, providing mTLS capabilities for secure communication between services.
`WORKFLOWS_OVERRIDE_VALUES`	Optional: This flag indicates the file path of the `custom values` configuration file created, which is used to customize AI model settings.
`STORAGE_CLASS_WORKFLOWS`	Optional:`STORAGE_CLASS_WORKFLOWS` is a global parameter for the Concert Workflows Helm chart that specifies which Kubernetes storage class should be used for all PVCs created by the Concert Workflows components (for example, MySQL, PostgreSQL, MinIO, Redis, RabbitMQ, and InfluxDB). By default, the Helm chart provisions PVCs for the application’s `StatefulSets` (for example, MySQL, PostgreSQL, MinIO, Redis, RabbitMQ, and InfluxDB) without a specific storage class. If your cluster uses a custom storage class, use the global parameter `STORAGE_CLASS_WORKFLOWS` in `params.ini` file to specify the name of the storage class available in your cluster. For more granular control, you can provide per-component overrides in a `custom-values.yaml` file.
`WORKFLOWS_INSTALLATION_TYPE`	Keep this value empty.
`WORKFLOWS_INSTALL_ALL_INTEGRATIONS`	Optional: To install all integrations, leave this parameter unset or set it to true. To install only the most commonly-used integrations, set this parameter to false. To install a customized set of integrations, set this parameter to false, edit the ibm-concert/ibm-concert-std-workflows/charts/rna-core/files/integrations.cfg file, and for each integration that you want to install, remove the leading hash (#) character.
`WORKFLOWS_FLOW_PAUSE_ENABLED`	By default, this parameter is set to true. It enables a Concert Workflows worker to pause its running workflows and save the workflow state to the database before it is terminated. To force workers to complete their workflows before termination, set this parameter to false.
`WORKFLOWS_TERMINATION_TIMEOUT`	Before a Concert Workflows worker is terminated, it pauses the workflows that it is running. To prevent workflows from being paused indefinitely, a timeout period is applied. If a workflow is still paused when the timeout is reached, the workflow is terminated. Use this parameter to define the termination timeout period in seconds for local workers. The default timeout period is 1800 seconds (30 minutes).
`WORKFLOWS_USER_WORKER_TOKEN_DURATION`	When a worker runs a workflow, it generates a user-scoped token to impersonate the user that triggered the workflow. The worker uses this token to fetch workflow definitions and authentication objects. Use this parameter to define the validity period of the token. The default validity period is 3600 seconds (1 hour).
Secure Coder parameters
`SECURECODER_IMAGE_REGISTRY_SUFFIX`	Indicates the registry where the Securecoder images are hosted. The `params.ini` file has a default image registry suffix value of `/concert`. You should not modify this value, as `/concert` is a fixed setting for your installation.
`SECURECODER_NS`	Specifies the Kubernetes namespace where Securecoder will be installed. By default, Securecoder will be installed in the `concert-securecoder` namespace. Leave this parameter unset to use the default namespace. If you cannot use the default namespace, set your own namespace value.
`SECURECODER_MEND_ENABLED`	Secure Coder offers a workspace scans feature, which utilizes the MendCLI tool to provide Static Application Security Testing (SAST) and Software Composition Analysis (SCA) scans. By default, this parameter is set to false, which means Mend scanning is disabled. If set to true, enables Mend SAST or OSS scanner integration.
`SECURECODER_MEND_ORG_NAME`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the Mend organiszation name. This is the organization identifier in your Mend account, for example: my-company-org.
`SECURECODER_MEND_PRODUCT_NAME`	If`SECURECODER_MEND_ENABLED` is`true`, set this value to the Mend product name.
`SECURECODER_MEND_SERVICE_URL`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the Mend service endpoint URL, for example: `https://app.mend.io`.
`SECURECODER_MEND_EMAIL_ADDRESS`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the email address associated with your Mend account, for example: `security-team@company.com`.
`SECURECODER_MEND_PROJECT_NAME`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the name of the Mend project associated with the deployment.
`WATSONX_API_URL`	If `SECURECODER_MEND_ENABLED` is `true`, set this value to the URL of the watsonx.ai instance, for example: `https://us-south.ml.cloud.ibm.com`.
`WATSONX_API_PROJECT_ID`	If `SECURECODER_MEND_ENABLED` is `true` and your chosen provider is `watsonx`, set this value to the ID of the watsonx.ai project that you want to use.
`WATSONX_API_MODEL_ID`	Optional: If `SECURECODER_MEND_ENABLED` is `true` and your chosen provider is `watsonx`, you can set this value to the watsonx.ai model that is used. The default value for this attribute is `"ibm/granite-4-h-small"`, which represents IBM's Granite-4.0-H-Small model.
`ENABLE_AI`	Set this value to `true` to enable the AI assistant or to `false` to disable it. By default, the assistant is disabled.
`LLM_PROVIDER`	The large language model (LLM) provider that you want to use. You can specify one of the following values: `watsonx` `vllm` By default, this parameter’s value is set to `watsonx`. Note: If your chosen provider is `watsonx`, you must specify values for the `WATSONX_API_URL`, `WATSONX_API_PROJECT_ID`, and `WATSONX_API_USER` parameters. If your chosen provider is `vllm`, you must specify values for the `LLM_MODEL`, `EMBED_MODEL`, and `LLM_BASE_URL` parameters.
`WATSONX_API_URL`	If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, set this value to the URL of the on-premises or SaaS watsonx.ai instance, for example: `https://your-cp4d-cluster.example.com` (for an on-premises watsonx.ai instance). `https://us-south.ml.cloud.ibm.com` (for a SaaS watsonx.ai instance).
`WATSONX_API_PROJECT_ID`	If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, set this value to the ID of the watsonx.ai project that you want to use.
`WATSONX_API_USER`	Your Concert license entitles you to use an instance of watsonx.ai via IBM Cloud Pak for Data. If `ENABLE_AI` is `true`, your chosen provider is `watsonx`, and you want to connect to this instance, set this value to the username that IBM Cloud Pak for Data uses to authenticate to the watsonx.ai instance.
`WATSONX_API_MODEL_ID`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, you can set this value to the watsonx.ai model that is used. The default value for this attribute is `"ibm/granite-4-h-small"`, which represents IBM's Granite-4.0-H-Small model.
`WATSONX_API_VERSION`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, you can set this value to the IBM watsonx.ai version that is used. The default value, and only valid value, is "2024-03-14".
`WATSONX_API_INSTANCE_ID`	Optional: If `ENABLE_AI` is `true` and your chosen provider is `watsonx`, and the watsonx.ai instance is a dedicated instance, you can set this value to the instance ID.
`LLM_MODEL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the name of the vLLM-provided model that you want to use for generating workflows. Only IBM Granite and Mistral AI models are supported, and the following models are recommended: IBM’s Granite-4.1-30B model. To use this model, set this value to `“ibm-granite/granite-4.1-30b“`. Mistral AI’s Mistral Small 4 model. To use this model, set this value to `“mistralai/Mistral-Small-4“`.
`EMBED_MODEL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the name of the vLLM-provided text embedding model that you want to use. Embedding models use vector-based comparisons between embedded prompts, block descriptions, and documentation to retrieve the most relevant blocks and documentation extracts in response to prompts. Only IBM Granite Embedding models are supported, and the Granite-Embedding-125m-English model is recommended. To use this model, set this value to `“ibm-granite/granite-embedding-125m-english“`.
`LLM_BASE_URL`	If `ENABLE_AI` is `true` and your chosen provider is `vLLM`, set this value to the URL of the vLLM-provided model instance, for example: `https://ml-serving.example.com:8443`.