Technology Knowledge Update TKU 2025-May-1
BMC Discovery Technology Knowledge Update 2025-May-1 provides information about new scanning capabilities in the 22.2, 23.1, 23.3, 24.1, 24.2, and 24.3 versions of BMC Discovery.
Release compatibility
TKU 2025-May-1 is compatible with the following versions of BMC Discovery: 22.2, 23.1, 23.3, 24.1, 24.2, and 24.3.
Download
Customers can access this TKU release from theBMC Electronic Product Distribution Website. If you are a customer or partner without a login, contact your BMC account manager.
Learn how to download from the BMC EPD site from this guideline.
Release contents
The release comprises components packaged as the following entities:
- BMC Discovery Technology Knowledge Update
- Core - Patterns that model various software products.
- Extended Database discovery - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases.
- Middleware discovery - Patterns that obtain detailed information about certain J2EE Application Servers and Web servers.
- Network Device Integration Module with associated Network Device definition files, Printer definition files, and SNMP managed devices definition files.
System - Patterns that detect configuration issues and populate Discovery Conditions BMC Discovery 22.2,BMC Discovery 23.1,BMC Discovery 23.3,BMC Discovery 24.1,BMC Discovery 24.2,BMC Discovery 24.3 and patterns used by the BMC CMDB sync system.
- BMC Discovery Extended Data Pack 2025-May-1
- Hardware Reference Data - Patterns and data import CSV file that populates BMC Discovery with power and heat consumption figures for various hosts.
- National Vulnerability Database - A pattern that populates BMC Discovery with information about the CPE ID of each product.
- Product Lifecycle - Patterns that populate BMC Discovery with information about End-of-Life, End-of-Support, and End-of-Extended-Support for versions of specific host Operating Systems and interpretations of certain software products.
- BMC Discovery for Storage is a separately licensable product.
- Storage Systems - Patterns that model many Storage Systems.
- Storage System Release Notes provides the latest Storage updates and improvements to existing Storage patterns.
- BMC Discovery for ServiceNow is a separately licensable product.
ServiceNow CMDB sync mapping patterns. The documentation ishere.
Command/File Matrix
The Command/File Matrix file (covering all commands executed and files retrieved by the patterns) for TKU 2025-May-1 is available here.
ServiceNow sync mapping pattern updates
The following improvements to ServiceNow sync are introduced within the scope of this release.
Defect ref. | Description | Notes |
---|---|---|
DRUD1-42396 | Resolved an issue with the missing synchronization of Cloud Database nodes to ServiceNow CMDB. HEADS-UP: Starting from TKU May 2025, to ensure seamless synchronization, it is mandatory to make sure the following classes exist and are configured on your ServiceNow instance:
| For more details, see the documentationhere. |
DRUD1-41064 | Added the category attribute (AdminCollection or CloudResource type) to the cmdb_ci_resource_group class. | New feature. |
DRUD1-48298 | Added support for the Deployment node sync to ServiceNow CMDB. | NA |
DRUD1-49612 | Updated ServiceNow.CloudRegion_cmdb_ci_logical_datacenter to synchronize GCP Regions to cmdb_ci_google_datacenter, and OCI Regions to cmdb_ci_oci_datacenter. | NA |
DRDC1-24235 | Updated ServiceNow.Host_Processor.Host_Processor to properly sync CPU data from BMC Discovery to ServiceNow CMDB. | NA |
DRUD1-48101 | Updated the pattern to properly synchronize Storage Pools and Storage Volumes to ServiceNow CMDB when they are related to StorageSystemGroup. | NA |
DRDC1-22537 | Fixed an issue with ServiceNow_StoragePool_cmdb_ci_storage_pool. | NA |
Outpost updates
We have no updates to report at this time.
Products
The following new products are introduced within the scope of this release.
Vendor | Product | Category | Platform | Instances | Versioning | Product page | RFE ref. |
Informatica | Ultra Messaging | Event-Driven Middleware | UNIX, Windows | Y | N | Informatica Ultra Messaging | DRDC1-24800 |
Swift | Alliance | Event-Driven Middleware | UNIX, Windows | Y | Y | Swift Alliance | DRDC1-25789 |
RFEs
The following RFEs are introduced within the scope of this release.
RFE ref. | Enhancement | Product page | SI key change |
DRDC1-26031 DRDC1-25940 DRDC1-26112 DRDC1-25868 DRDC1-26245 DRDC1-25430 DRDC1-25920 DRDC1-26065 DRDC1-26026 DRDC1-26131 DRDC1-25876 DRDC1-26192 DRDC1-25195 | Updated versioning. | N | |
DRDC1-25497 | Update the pattern to use the Cloudera Cloud Data Platform name when modeling SIs. | Cloudera CDH | N |
DRDC1-26166 | Improved OpenShift CPU value conversion. | Kubernetes functions | N |
DRDC1-26184 | Updated the pattern to consistently model serial numbers for Exadata container nodes. | Oracle Engineered Systems | N |
DRDC1-25867 | Updated the pattern to attempt a full path in commands. | Pivotal RabbitMQ | N |
DRDC1-25164 | Updated the type for the pattern. | Red Hat JBoss Application Server | N |
DRDC1-25870 | Added a false-positive condition to prevent the pattern from being erroneously triggered by the SAP Digital Discovery Assessment process. | SAP HANA | N |
DRDC1-26182 | Added support for custom attributes for vCenter Cluster. | VMware vCenter Server | N |
DRDC1-25755 | Added the connection_state attribute for ESXi hosts scanned through vCenter. | VMware vCenter Server | N |
Defects resolved
The following defects are fixed within the scope of this release.
Defect ref. | Details | Product page | SI key change |
DRDC1-25784 | Problem: Some patterns do not use whichPackage as a common function to obtain the package for a given executable path. Solution: Updated the patterns to use whichPackage. | N | |
DRDC1-25805 | Problem: The patterns use inconsistent attribute names for SoftwareContainer nodes. Solution: Updated the container patterns to set container_id, image, and image_id SoftwareContainer attributes. | Applicable to all the container patterns. | N |
DRDC1-25849 | Problem: Incorrect ageing. Solution: Code fix. | BMC TrueSight Automation Console | N |
DRDC1-25802 | Problem: The pattern is no longer triggered by Detail nodes due to their change to ContainerImage nodes. Solution: Updated the pattern to get triggered by ContainerImage nodes. | Duo Security | N |
DRDC1-26258 | Problem: BMC Discovery creates MongoDB databases with incorrect names. Solution: Code fix. | MongoDB | N |
DRDC1-26246 | Problem: An ECA error. Solution: Code fix. | Oracle RDBMS | N |
DRDC1-26222 | Problem: Incorrect versioning for the Windows server. Solution: Code fix. | Orient Technologies Ltd OrientDB | N |
DRDC1-25778 | Problem: The podman ps command returns an empty list irrespective of running Podman containers. Solution: Code fix. | Podman | N |
DRDC1-25756 | Problem: The pattern does not work in a container unless the binary has a full path. Solution: Code fix. | PostgreSQL RDBMS | N |
DRDC1-25816 | Problem: The pattern sometimes does not get bind_address or port. Solution: Code fix. | Sybase Adaptive Server Enterprise | N |