25.3.01 enhancements

Review the deployment enhancements for BMC Helix Service Management on-premises 25.3.01 that will benefit your organization and understand changes that might impact your users.

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

Downloading and installing BMC Helix Service Management 25.3.01

Download from EPD	Downloading-the-installation-files
Fresh installation	Installing
Upgrade	Upgrading

25.3.01

Use updated support for technology stack

BMC Helix Service Management supports the following technology stacks:

Kubernetes version 1.33
OpenShift version 4.19
Nginx Ingress Controller version 1.12.4
Helm 3.18

For more information, see System-requirements.

(Controlled availability customers only) Deploy BMC Helix Service Management platform components

To optimize resource utilization and minimize your environmental footprint, deploy only the platform components of BMC Helix Service Management using the CORE deployment mode. This mode loads only the essential components and services into memory, allowing you to start with a lightweight setup and scale up based on your operational needs. Use the CORE mode to activate only the following components:

BMC Helix Innovation Suite, which includes AR System and Mid Tier
BMC Helix CMDB
Foundation data objects
(Optional) BMC HelixGPT and Clam AntiVirus

For more information, see Deploying BMC Helix Service Management in the CORE mode, Performing the BMC Helix Service Management installation, and Transitioning between deployment modes.

What else changed in this release

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

Update	Product behavior in versions earlier than 25.3.01	Product behavior in version 25.3.01
Upgrade process changes	Direct upgrade was supported for upgrading BMC Helix Service Management from an earlier version to the latest version. A step upgrade was not required for any earlier version.	You can perform a direct upgrade of BMC Helix Service Management from 23.3.x and later versions. However, upgrading from versions earlier to 23.3.x includes a step upgrade. For more information, see Upgrading BMC Helix Service Management to 25.3.01.
Parameters name changes in the HELIX_ONPREM_DEPLOYMENT pipeline	The HELIX_ONPREM_DEPLOYMENT pipeline parameter names in version earlier to 25.3.01 are as follows: CLUSTER CLUSTER_DOMAIN CUSTOMER_SIZE DEPLOYMENT_MODE	The following HELIX_ONPREM_DEPLOYMENT pipeline parameter names are renamed: CLUSTER renamed as CLUSTER_CONTEXT CLUSTER_DOMAIN renamed as APPLICATION_PARENT_DOMAIN CUSTOMER_SIZE renamed as ENVIRONMENT_SIZE DEPLOYMENT_MODE renamed as DEPLOYMENT_TYPE Additionally, the DEPLOYMENT_MODE parameter is included. Use this parameter to select the following deployment modes: CORE—Loads only essential platform components such as: BMC Helix Innovation Suite BMC Helix CMDB Foundation data objects Optionally, BMC HelixGPT and Clam AntiVirus FULL (Default)—Loads all available BMC Helix Service Management components and applications into memory. For more information, see Performing the BMC Helix Service Management installation.
Automatic installation of the yq utility package on Helm nodes during deployment preparation	The yq utility package was not required or installed as part of the deployment process.	The yq utility package is now automatically installed on all Helm nodes during deployment preparation. This utility is required for smooth Helm-based pipeline execution in both Standard and Air-gapped environments.