23.3 enhancements and patches


Review the  BMC Helix CMDB  23.3 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version

SaaS

On premises

Fixed issues

Updates and enhancements

23.3.04

✅️

✅️

23.3.03

✅️

✅️ 1

23.3.02

✅️


None

23.3.01

✅️

✅️

23.3

✅️


1.The BMC Helix Service Management 23.3.03 on-premises release, which was generally available on October 1, has now transitioned to a controlled availability release. 

BMC applies upgrades as described in   BMC Helix Upgrade policy.


(On premises only) Downloading and installing the patch

Downloading from EPD

See Downloading the installation files  in BMC Helix Service Management documentation.

Patch installation

See Upgrading BMC Helix IT Service Management to 23.3.04  in BMC Helix Service Management documentation.


23.3.04



(Controlled availability) Quickly create service models by using blueprint templates

Leverage BMC Helix Service Modeling to quickly create service models by using predefined blueprint templates. Seamlessly integrate topology data from multiple sources to easily build comprehensive, dynamic service models. For more information, see Creating-service-models-by-using-blueprints.

Service modeling_enh.jpg


23304_enh_re.jpg

Improve reconciliation job performance when processing a large number of CIs

Use the RE ID Service to improve the speed and efficiency of large reconciliation jobs by processing the identification activity on a separate pod. For more information, see Reconciling-a-large-number-of-CIs .

Additionally, the RE ID Service filters duplicate CIs from the source dataset before running the identification a ctivity, making the overall process more efficient. For more information, see Identification-activities-to-match-instances-across-datasets


Run Atrium Integrator Spoon on Pentaho 9.x

Pentaho is upgraded from 6.x to 9.x. Upgrade your Atrium Integrator Spoon client to run on Pentaho 9.x. For more information about upgrading the Spoon client, see Using-the-Atrium-Integrator-Spoon-client .

enh_pentaho upgrade.jpg


CDM_enh_attributes.jpg

New classes and attributes added to the Common Data Model

The BMC Helix CMDB Common Data Model is updated with new classes and attributes under the BMC_BaseElement class and new attributes under the BMC_BaseRelationship class. These classes and attributes support the impact analysis and incident creation processes in BMC Helix NetOps. For more information, see Summary-of-changes-to-the-Common-Data-Model.



Use updated support for technology stack

BMC Helix Service Management deployment supports the following technology stacks:

  • Kubernetes version 1.30
  • OpenShift version 4.16
  • Nginx Ingress Controller versions 1.11.1 and 1.11.2
  • Helm versions 3.15 and 3.16

For more information, see System requirements in BMC Helix Service Management documentation.



What else changed in this release

The following table lists the changes in the product behavior:

Update

Product behavior in versions earlier than 23.3.04

Product behavior in version 23.3.04

Update to BMC_OperatingSystem class.

The options available in the OS_Type list in the BMC_OperatingSystem class are version-specific for Windows. Hence, it is difficult to map a Windows operating system to an OS_Type that is unavailable in the list.

A generic option Windows is available in the OS_Type list of options. To specify a required version of the Windows operating system, use the following attributes:

  • VersionNumber
  • MarketVersion

This update is available with TKU for December 2024 and later. For information about the latest TKU, see Technology Knowledge Updates (TKU) - Schedule and Roadmap

23.3.03



What changed in this release

The following table lists the changes in the product behavior:

Update

Product behavior in versions earlier than 23.3.03

Product behavior in version 23.3.03

Standard reconciliation identification rule

The standard reconciliation identification rule provided out-of-the-box for the BMC_AdminDomain class uses the TokenId and Name attributes in the qualification criteria.

The standard reconciliation identification rule provided out-of-the-box for the BMC_AdminDomain class uses only the TokenId attribute in the qualification criteria. This update is implemented because the values in the Name attribute might not have unique values required for identification.

For more information about identification rules, see Configuring-reconciliation-identification-rules.

Reconciliation

The reconciliation process is deployed and run in the fts admin pod with other CMDB components and processes.

The reconciliation process is deployed and run in a separate container to improve the overall performance of reconciliation processes. The following changes occur as a result of this update:

  • A reconciliation job directly polls the Application Pending form and starts the job.
    In CMDB Portal, the reconciliation job is listed in the Queued jobs table until the job starts.
    For more information about reconciliation jobs, see Monitoring-a-reconciliation-job.
  • A CCS updater utility runs when a reconciliation process is started. This utility looks for modifications made to the CCS parameters for reconciliation and implements those modifications to run the reconciliation process. 
    The logs for this utility are located at /opt/bmc/ARSystem/db/re_monitor.log.
  • Reconciliation logs are located at /opt/bmc/ARSystem/db.
    For information about logs, see Working-with-logs.

Change in the deployment method of the plug-in server for optimizing system performance.

The plug-in server processes for different applications run in a single container.

The  plug-in server processes for the following CMDB components run on independent pods, providing an optimized system performance:

  • Impact Simulator (AIS)
  • Normalization (NE)

You can selectively restart only the plug-in server without affecting the other services.

For more information about the plug-in server instance settings, see Setting plugin server configuration options

Impact Simulator configuration

When you run an impact simulation, the simulation results and the CI information are stored in the main memory.

Store the impact simulation results and CI information in the database by using a CCS parameter. This information is accessible across all the pods.

For more information, see Impact-Simulator-configuration-settings


23.3.01


High availability of CMDB Portal

Even when the platform-fts-0 pod that handles all administrative requests is down, you can still access CMDB Portal with limited functionality. For more information, see Accessing and navigating the CMDB Portal .

23301_enh image.png


23.3



233_enh.png

Attributes to store end-of-product-support information

Store and view the end-of-support dates for the hardware and software products in your environment. The following attributes are added under the BMC_BaseElement class in the Common Data Model:

  • EndOfExtendedSupport 
  • EndOfLife 
  • EndOfSecuritySupport 
  • EndOfSupport

The information for these attributes is populated by BMC Discovery. For more information, see Summary-of-changes-to-the-Common-Data-Model.



What else changed in this release

The following table lists the changes in the product behavior:

Update

Product behavior in versions earlier than 23.3

Product behavior in version 23.3

UI enhancements in CMDB Explorer

  • The user interface for CMDB Explorer partially occupies the screen space.
  • The Show CI details tab is displayed in CMDB Explorer. 
  • In CMDB Explorer, recentre icon.pngis the Reset view to fit screen icon to re-center the explorer view.
  • The user interface for CMDB Explorer fully occupies the screen space and provides a better view of the CI graph in CMDB Explorer.
  • The Show CI details option is available when you right-click a CI or a relationship in the CMDB Explorer view. 
  • In the CMDB Explorer, recentre new icon.pngis the Reset view to fit screen icon to re-center the explorer view.

UI changes in CMDB Portal

You can access the flash-based Atrium Core Console and Atrium Integrator from CMDB Portal > Atrium Core as shown in the following image:

Atrium Core tab.jpg

You cannot access the flash-based UI components. You can access only the following CMDB components:

233_Atrium core tab.png 

For more details, see User-interface-overview.

 

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