22.1 enhancements and patches

Review the BMC Helix Service Management deployment 22.1 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version	Fixed issues	Updates and enhancements
22.1.06	Known-and-corrected-issues	22.1.06 enhancements

Downloading and installing the patch

Download from EPD	Downloading-the-installation-files
Patch installation	Upgrading-BMC-Helix-Service-Management-to-22-1-06

22.1.06

Disaster recovery for BMC Helix Service Management

Configure disaster recovery to set up BMC Helix Service Management and replicate data onto the secondary site.
When a disaster occurs, you can failover to the secondary site and continue your operations with minimal or no impact.

Disaster recovery for BMC Helix Service Management 22.1.06 is supported only with the BMC Helix Platform Common Services 23.4.00 version.

For more information, see Disaster-recovery-deployment.

Consent to use Gainsight PX for data collection

BMC uses Gainsight PX to collect product telemetry data and to display the self-help widget that provides access to a product tour, interactive guides, instructions for setting up and going live, and more.

Gainsight PX provides insights into product usage, users’ activities within the application, product performance, gaining web statistics, and optimizing the product capabilities. The data helps to gain insights on search behavior to assist with the product and marketing research. For more information, see Enabling-self-help-and-product-telemetry-through-Gainsight-PX.

Updated support for Kubernetes and OpenShift

BMC Helix Service Management deployment supports Kubernetes version 1.25, 1.26, and 1.27, and OpenShift version 4.12.

The supported versions of Kubernetes and OpenShift are as follows:

Kubernetes versions - 1.23 – 1.27
Important
If you are using BMC Helix Service Management in Kubernetes version 1.25, make sure that you use the baseline pod security standard for the namespace where it is being deployed.
OpenShift versions - 4.10 – 4.12

For more information, see System-requirements.

Updated support for Ingress and Helm

BMC Helix Service Management deployment supports Ingress controller versions 1.6.4, 1.7.0, and 1.9.3, and Helm versions 3.11, 3.12, and 3.13.

Supported Ingress and Helm versions with the orchestration platforms are as follows:

Orchestration platform	Ingress	Helm
Kubernetes 1.27	1.9.3	3.13
Kubernetes 1.26	1.7.0	3.12
Kubernetes 1.25	1.7.0	3.11
Kubernetes 1.24	1.7.0
Kubernetes 1.23	1.6.4
OpenShift 4.12	1.7.0
OpenShift 4.11	1.7.0
OpenShift 4.10	1.6.4

For more information, see System-requirements.

Additional products available for on-premises installation

The following products are available in BMC Helix Service Management, and you can install them in your on-premises environment:

BMC Helix Portfolio Management (HPM)
BMC Helix Customer Service Management (CSM)
Drift Management

For more information, see Performing-the-BMC-Helix-Service-Management-installation.

What else changed in this release

The following table lists the changes in the product behavior in this patch:

Update	Product behavior in versions earlier than 22.1.06	Product behavior in version 22.1.06
The structure of the bmc repository that contains the BMC Helix Service Management container images is changed	The repository bmc/lp00x contained the BMC Helix Service Management container images. For example, containers.bmc.com/bmc/ lp00x:ARS-213006HF-202211181051-21306-HF7	Each component has a separate repository such as ars, midtier, cmdb, and virtualchat. These repositories contain the images for the respective component, such as the AR System images are located in the ars repository, and the Mid Tier images are located in the midtier repository. For example, containers.bmc.com/bmc/ars:221006HF-202306221501 and containers.bmc.com/bmc/midtier:22106-RTM
Git repository parameter changes in the HELIX_ONPREM_DEPLOYMENT pipeline	While building the HELIX_ONPREM_DEPLOYMENT pipeline, to specify the Git repositories location, you had to provide values for parameters such as DEVOPS_REPO, CUSTOMER_CONFIGS, PLAYBOOKS_REPO, HELM_REPO, and SMARTAPPS_HELM_REPO.	While building the HELIX_ONPREM_DEPLOYMENT pipeline, you only have to specify the location of the directory that contains all the Git repositories in the GIT_REPO_DIR parameter.
Parameters removed from the HELIX_ONPREM_DEPLOYMENT pipeline	While building the HELIX_ONPREM_DEPLOYMENT pipeline, you had to provide values for the following parameters: FTS_ELASTICSEARCH_USERNAME HELIX_PLATFORM_CLUSTER HELIX_PLATFORM_KUBECONFIG_CREDENTIAL ITSM_USER ITSM_Password	The HELIX_ONPREM_DEPLOYMENT pipeline does not contain the following parameters: FTS_ELASTICSEARCH_USERNAME HELIX_PLATFORM_CLUSTER HELIX_PLATFORM_KUBECONFIG_CREDENTIAL ITSM_USER ITSM_Password These parameters are managed through the pipeline now and are removed to avoid parameter duplication.
New parameters in the HELIX_ONPREM_DEPLOYMENT pipeline	While building the HELIX_ONPREM_DEPLOYMENT pipeline, the following parameters were not available: CACERTS_SSL_TRUSTSTORE_PASSWORD HELIX_SMARTAPPS_CSM HELIX_SMARTAPPS_FAS HELIX_DRIFTMANAGEMENTPLUGIN SIDECAR_FLUENT_DETAIL_LOG HELIX_FULL_STACK_UPGRADE HELIX_RESTART DB_JDBC_URL LOGS_ELASTICSEARCH_TLS LOGS_ELASTICSEARCH_PASSWORD ENABLE_PLATFORM_INT_NORMALIZATION MIDTIERCACHEBUILDER_TRIGGER_PRELOAD MIDTIERCACHEBUILDER_SCHEDULE BWF_DEPLOY_SAMPLE_CONTENT_PACK	While building the HELIX_ONPREM_DEPLOYMENT pipeline, you have to specify the values for following parameters: CACERTS_SSL_TRUSTSTORE_PASSWORD HELIX_SMARTAPPS_CSM HELIX_SMARTAPPS_FAS HELIX_DRIFTMANAGEMENTPLUGIN SIDECAR_FLUENT_DETAIL_LOG HELIX_FULL_STACK_UPGRADE HELIX_RESTART DB_JDBC_URL LOGS_ELASTICSEARCH_TLS LOGS_ELASTICSEARCH_PASSWORD ENABLE_PLATFORM_INT_NORMALIZATION MIDTIERCACHEBUILDER_TRIGGER_PRELOAD MIDTIERCACHEBUILDER_SCHEDULE BWF_DEPLOY_SAMPLE_CONTENT_PACK For more information about these parameters, see Performing-the-BMC-Helix-Service-Management-installation.