25.4.00 enhancements and patches

Use updated support for technology stack

BMC Helix ITOM deployment supports the following technology stacks:

• Kubernetes 1.34
• Nginx Ingress Controller version 1.14.0, 1.13.x

For more information, see System requirements.

Deploy essential infrastructure services automatically

The deployment manager configures the necessary infrastructure services automatically for the products specified in the deployment.config file. This automation efficiently streamlines setup and optimizes resource sizing based on deployment requirements.

The manual configuration of the following infrastructure service parameters is not required:

• _PTPOSTGRESS
• _KAFKA
• _REDISCLUSTER
• _RSSO
• _VICTORIAMETRICS
• _ELASTICSEARCH  
• _MINIO 

Download container image list for selected BMC Helix ITOM products

Select the BMC Helix ITOM products you want to deploy and download a text file that lists only the required container images, excluding unnecessary image loading and reducing storage usage for unselected services.

For more information, see Setting up a Harbor registry in a local network and synchronizing it with BMC DTR and Setting up a Harbor registry in an air-gapped environment and synchronizing it with BMC DTR.

Deploy BMC Helix Intelligent Integrations services with BMC Helix ITOM

Deploy BMC Helix Intelligent Integrations services by using the SWP_INTELLIGENT_INTEGRATIONS parameter in the deployment.config file. This option deploys a limited set of services that offer the following capabilities:

• Assign the II Admin role to allow users to manage BMC Helix Intelligent Integrations connectors and configurations.
• Improve the reliability of BMC Helix Intelligent Integrations gateway deployments by implementing high-availability configurations with a gateway proxy.

For more information, see Deploy BMC Helix IT Operations Management.

Activate the BMC Helix ITOM account without email verification

Administrators can activate the BMC Helix ITOM account even when the Simple Mail Transfer Protocol (SMTP) service is not configured. The first user is automatically created with a default password, eliminating the dependency on email-based activation during tenant onboarding.

For more information, see Performing the post deployment procedures.

Use improved self-monitoring in BMC Helix ITOM ​​​​​​

The automation of the following self-monitoring tasks in your BMC Helix ITOM environment accelerates setup and reduces configuration errors:

• Importing monitoring and alarm policies, logs, dashboards, service models, and blueprints
• Configuring alarm policies

Automating self-monitoring reduces manual work and setup time. This also streamlines the process by minimizing configuration errors.

For more information, see Setting up and configure the monitoring solution.

Ensure service availability during disruptions by using Pod Disruption Budget (PDB)

Pod Disruption Budgets are created automatically for BMC Helix ITOM components. PDBs helps maintain high availability by limiting the number of pods disrupted simultaneously during planned maintenance or scaling operations.

Update domain URL after deployment

You can update the domain URL after completing the deployment to align with new organizational domains, certificates, or DNS configurations. This enhancement ensures that all BMC Helix components use the updated domain for authentication, service mapping, and secure access.

For more information, see Changing the domain URL post-deployment.

What else changed in this release