This documentation supports an earlier version of BMC Helix IT Service Management on-premises deployment.To view the documentation for the latest version, select 23.3.04 from the Product version picker.

21.3 Patches


Review the fixes and updates in this patch for BMC Helix Service Management deployment that might impact your users.

Several enhancements were delivered in version 21.3. To learn about these enhancements, see 21.3 enhancementsin the BMC Helix ITSM documentation.






Updates in 21.3.10

This patch contains the following updates:

Support for Kubernetes 1.25 and OpenShift 4.12

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

The supported versions of Kubernetes and OpenShift are as follows:

  • Kubernetes versions - 1.23 – 1.25

    Important

    If you are using BMC Helix Service Management in Kubernetes version 1.25, make sure that you use the baseline pod security standard  if you enable pod security standards in your namespace.

  • OpenShift versions - 4.10 – 4.12

For more information, see System-requirements.

Support for Ingress controller 1.7.0 and Helm 3.11

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

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

Orchestration platform

Ingress

Helm

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.

Migration of container images to the Alpine operating system

All the BMC Helix Innovation Suite and applications container images that are hosted on the BMC Docker Trusted Registry (DTR) have been migrated from CentOS to the Alpine operating system.

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)

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 21.3.10

Product behavior in version 21.3.10

Changes to the structure the bmc repository that contains the BMC Helix Service Management container images

The bmc/lp00x repository 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, 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:21310HF-202306221501 and containers.bmc.com/bmc/midtier:21310-RTM

Changes to Git repository parameter 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

These parameters are now managed through the HELIX_ONPREM_DEPLOYMENT pipeline code and are removed from the pipeline input to avoid parameter duplication.


Parameters added to the HELIX_ONPREM_DEPLOYMENT pipeline

NA

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
  • AR_DATETIME
  • AR_TIMEZONE

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

Updates in 21.3.06

This patch contains the following updates:

Support for Red Hat Enterprise Linux 8 and CentOS Core 8

You can set up BMC Deployment Engine on RHEL 8 and CentOS Core 8 operating systems.

The supported versions of RHEL and CentOS are as follows:

  • RHEL versions - 7.x – 8.x
  • CentOS versions - 7.x –8.x

For more information, see System-requirements and Setting-up-BMC-Deployment-Engine.

Improved deployment sizing guidelines

BMC provides improved sizing templates for the BMC Helix Service Management deployment sizes: Compact, Small, Medium, and Large. 

For information about the sizing guidelines, see Sizing-and-scalability-considerations.

For information about how to use the sizing templates, see Setting-up-BMC-Deployment-Engine and Installing-BMC-Helix-Platform-services.

Support for Azure Kubernetes Service platform

BMC Helix Service Management supports deployment on an Azure Kubernetes Service (AKS) cluster.

For more information, see System-requirements and Installing-BMC-Helix-Service-Management-in-an-Azure-Kubernetes-Service-cluster.

Support for Kubernetes and OpenShift

BMC Helix Service Management deployment supports Kubernetes versions 1.22, 1.23, and 1.24, and OpenShift versions 4.9, 4.10, and 4.11. 

The supported versions of Kubernetes and OpenShift are as follows:

  • Kubernetes versions - 1.18 – 1.24
  • OpenShift versions - 4.6 – 4.11

For more information, see System-requirements.


Support for self-signed and CA signed certificates

Use a custom self-signed or CA signed certificates to use HTTPS communication for Service Management applications.

For more information, see the CACERTS_FILE parameter in Performing-the-BMC-Helix-Service-Management-installation and Applying-security-certificates-to-your-applications.

Support for Nginx Ingress Controller

BMC Helix Service Management deployment supports  Nginx Ingress Controller version 1.2.0 in addition to support for version 0.32.

For more information, see System-requirements.

Automated setting up of BMC Deployment Engine

You can set up BMC Deployment Engine by using an automated script that simplifies the set up process. 

For more information, see Setting-up-BMC-Deployment-Engine.

Updates in 21.3.05

This patch contains the following updates:

Support for Amazon EKS, GKE and OKE platforms

BMC Helix Service Management supports deployment on the following Kubernetes clusters:

  • Amazon Elastic Kubernetes Service (EKS)
  • Google Kubernetes Engine (GKE)
  • Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE)

For more information, see System-requirements, Installing-BMC-Helix-Service-Management-in-an-Amazon-Elastic-Kubernetes-Service-cluster, and Installing-BMC-Helix-Service-Management-in-a-Google-Kubernetes-Engine-cluster.

Rollback deployment

When updating BMC Helix Service Management from the version 21.3.04 to 21.3.05, if any of the HELIX_PLATFORM_DEPLOY, HELIX_NONPLATFORM_DEPLOYor HELIX_SMARTAPPS_DEPLOY pipelines fail, you can rollback back to the last successful deployed version of the platform and applications by using the rollback option.

For more information, see Upgrading-BMC-Helix-Service-Management-to-21-3-10.

Updates to Fluent Bit deployment

In a fresh deployment of BMC Helix Service Management, Fluent Bit is deployed as a sidecar container in the BMC Helix Innovation Suite namespace. 

The following table lists the changes in the product deployment behavior:

Product

Behavior in versions earlier than 21.3.05

Behavior in version 21.3.05

Fluent Bit

  • Deployed as root container
  • Required cluster administrator privileges for deployment
  • Deployed as sidecar container with non-root privilege
  • Does not require cluster administrator privileges for deployment

For more information, see Performing-the-BMC-Helix-Service-Management-installation and Viewing-and-collecting-critical-logs-by-using-the-Kibana-dashboard.

Enhancements to Support Assistant tool

Use a custom role in your BMC Helix Innovation Suite namespace to install the Support Assistant tool.

For more information, see Performing the 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 21.3.05

Product behavior in version 21.3.05

Change in the HELIX_POST_DEPLOY_CONFIG parameter

HELIX_POST_DEPLOY_CONFIG parameter was used to apply force password change for the Demo user on first time login.

HELIX_POST_DEPLOY_CONFIG is a pipeline that is used to delete the Demo user.

Demo user is deleted when you select the HELIX_POST_DEPLOY_CONFIG option and run the HELIX_ONPREM_DEPLOYMENT pipeline post-installation of BMC Helix Service Management.

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

Updates in 21.3.04

This release delivers fixes, security improvements, and operational improvements for BMC Helix ITSM and BMC Helix Innovation Suite.

This patch contains the following updates:

Enhancements to Support Assistant tool

In a fresh deployment of BMC Helix Service Management, Support Assistant tool is deployed as a sidecar container in the BMC Helix Innovation Suite namespace. 

The following table lists the changes in the product deployment behavior:

Product

Behavior in versions earlier than 21.3.04

Behavior in version 21.3.04

Support Assistant tool

  • Deployed as root container
  • Required cluster administrator privileges for deployment
  • Deployed as non-root container 
  • Does not require cluster administrator privileges for deployment
  • Requires namespace level permissions for deployment

For more information, see Performing-the-BMC-Helix-Service-Management-installation and Viewing-and-collecting-logs-by-using-the-Support-Assistant-tool.

Support for deployment size templates

BMC Helix Service Management deployment supports four different sizing profiles: Compact, Small, Medium, and Large. 

For more information, see Sizing-and-scalability-considerations

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 21.3.04

Product behavior in version 21.3.04

Additional pipeline for deploying BMC Helix ITSM: Smart Reporting

BMC Helix ITSM: Smart Reporting was deployed using the HELIX_PLATFORM_DEPLOY pipeline.

BMC Helix ITSM: Smart Reporting is deployed using the HELIX_SMARTREPORTING_DEPLOY pipeline.

For information, see Performing the installation.

Updates in 21.3.02

This patch contains the following updates:

Support for BMC Helix ITSM Insights and BMC Helix Dashboards deployment

BMC Helix Service Management supports deployment of BMC Helix ITSM Insights and BMC Helix Dashboards products in your on-premises environment. The BMC Helix Service Management deployment pipeline provides an option to select BMC Helix ITSM Insights and BMC Helix Dashboards deployment and you can optionally deploy the products along with other ITSM applications. The option is available for fresh installation and upgrade of BMC Helix Service Management.

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

ITSM interops.png

Version mapping

The external version number that is displayed on the product pages is 21.30.02. BMC uses the same version 21.30.02 for internal purposes. Starting with BMC Helix Service Management 21.3, the external version number, displayed on the product page, and the version number used for internal purposes are the same.

BMC Helix Service Management product version is displayed on the following forms:

Form name

Screenshot

On the Platform tab of the Server Information form

Server Information form.png

On the SHARE:Application_Properties form

Version mapping.png

Downloading and installing the patch

Download from EPD

Patch installation

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*