BMC Atrium Discovery Technology Knowledge Update 2014-Apr-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0series.
The April 2014 TKU includes changes to the CMDB Sync mapping (introduced between TKU Jan 2014 and TKU Mar 2014)
BMC_ComputerSystemCIs mapped from partition Host nodes are updated and their PartitionIds are set.
FunctionalComponentnodes representing CAM Functional Components are mapped to
BMC_ComputerSystemCIs mapped from HostContainer nodes are updated and their TokenIds are set.
BMC_ApplicationServiceCIs are updated and their TokenIds are set.
TKU 2014-Apr-1 is released in three streams:
Customers can access this TKU release from the BMC Electronic Product Distribution Website. If you are a customer or partner and do not already have a login please contact your BMC account manager.
Check out this demo if you are unsure how to download from BMC EPD site
The release comprises components packaged as two entities:
A matrix covering ALL commands executed and ALL files retrieved by the patterns is available to our customers from the BMC Electronic Product Distribution Website. The filename is TKU_Command_File_Matrix-2014-04-1.xls
|BMC||Portal||Performance Management Software||Windows||Y||Y|
|IBM||Informix MaxConnect||Data Integration and Access Software||UNIX||Y||Y|
|IBM||WebSphere Enterprise Service Bus||Enterprise Service Bus and Connectivity Middleware||UNIX/Windows||Y||Y|
|MariaDB||MariaDB Server||Relational Database Management Systems||UNIX/Windows||Y||Y|
|Microsoft||Office Web Apps Server||Authoring and Publishing Software||Windows||Y||Y|
|Percona||Percona Server||Relational Database Management Systems||UNIX/Windows||Y||Y|
|RFE ref.||Product||Enhancement||SI Key Change||Product Page|
|QM001817740||BMC Performance Manager Portal||Product identification further enhanced through an additional pattern which uses information obtained from the new BMC Portal product pattern.||N|
|QM001820826||HP Business Process Monitor||Pattern updated with additional registry path and package name for use in versioning||N|
|QM001822093||IBM InfoSphere DataStage||File versioning method improved||N|
|QM001822455||Oracle Real Application Clusters|
Model of Oracle Real Application Clusters enhanced based on customer feedback. This has necessitated SI key change in Oracle Real Application Clusters pattern.
|QM001822814||Attachmate Reflection for Secure IT||SSHServer pattern enhanced through improvement of package versioning and addition of file versioning on the Windows platform||N|
|QM001823340 / QM001823695||Software Support Details||Support Details for various Quest products as well as Oracle WebLogic Server updated||N/A|
|QM001823477||Red Hat KVM||Patterns updated to improve identification of Red Hat KVM deployments||N|
|QM001823551||Apache Derby RDBMS||Pattern trigger improved to decrease the chance of false positives||N|
|QM001823559||Symantec Backup Exec||Version mapping table in the pattern updated to add support for correctly setting the marketing version of latest releases||N|
|QM001823726||IBM Business Process Manager||Pattern updated to add support for both older version of the product (IBM WebSphere Lombardi Edition Process Server) and the current versions of the product. Model slightly updated.||Y|
|QM001823904||Apache Tomcat||Parsing of JDBC connection information when the JDBC resource is Oracle RDBMS improved (Apache Tomcat extended discovery)||N|
|QM001824036||Sterling Commerce Connect Direct||Server pattern enhanced on Windows platform through addition of a method to obtain the server node name and therefore make the model more accurate.||Y|
|QM001824086||SAP NetWeaver Enterprise Portal||Product discovery improved through enhancement to false positive checking||N|
|QM001824257||OS Support Details||OS Support Details for VMware ESXi updated||N/A|
|QM001824451||IBM WebSphere Application Server \\/ \\IBM WebSphere Portal Server||The order in which server, cell and node name are extracted from process arguments reversed based on customer feedback||N|
|#TKU-1956||Oracle Data Integrator||The Oracle Data Integrator Runtime Agent pattern enhanced with code to create a relationship from the Runtime Agent SI to the related database server SI||N|
|#TKU-2196||BMC CONTROL-M Enterprise Manager||BMC CONTROL-M Enterprise Manager Server and Configuration Agent pattern use an improved method to obtain the installation directory path||N|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Apr-1
|Defect No||Details||Product Page|
|QM001815276||Problem: BMC Atrium Discovery pattern fails to correctly extract information in a scanner / consolidator setup. Solution: Code fix. Certain information will only be available with BMC Atrium Discovery 9.0 SP3|
|QM001822694||Problem: Build number may contain end of line characters Solution: Code fix. Improved parsing of version information|
|QM001822936||Problem: Sybase ASE Database Server pattern can incorrectly extract the install path, preventing extended Sybase ASE discovery pattern from working Solution: Code fix, improved installation path extraction.|
|QM001823211 / QM001823273||Problem: Parsing of configuration files by the Apache Web Server extended discovery pattern can fail leading to information about websites not being collected Solution: Code fix - improved parsing of configuration files|
|QM001823583||Problem: Pattern in the Oracle VM VirtualBox module that creates a relationship from the SI to the virtual host can exit with an ECA engine error. Solution: Code fix.|
Problem: Pattern that creates an Aggregated Software Instance in the BMC TM ART module has an incorrect key leading to it collecting SIs accross hosts
Solution: SI key updated to resolve the issue.
|QM001823880||Problem: BMC_MFSoftwareServer/BMC_SoftwareServer.ManufacturerName is not set in case of Mainframe. ManufacturerName is important for normalization in CMDB. The publisher information seems to be consistently and correctly set in DiscoveredSoftware.vendor and the mainframe pattern sets this value to SoftwareInstance.publisher. The syncmapping pattern should map SoftwareInstance.publisher to BMC_MFSoftwareServer/BMC_SoftwareServer.ManufacturerName. Solution: Sync mapping updated|
|QM001824101||Problem: IBM WebSphere Process Server can incorrectly identify the product as present on hosts where it is not installed. Solution: Code fix - false positive checking improved.|
|QM001824281||Problem: Oracle Clusterware can include end of line character in the cluster ID information due to incorrect parsing of the data Solution: Code fix. Parsing of cluster ID improved.|
|QM001824057||Problem: BladeLogic pattern was unable to create SI's for all of customer's BladeLogic Servers Solution: Code fix. Checked condition was changed to allow new kind of BladeLogic setup.|
|#TKU-2185||The order in which the containment relationship is created was corrected.|
|#TKU-2189||Problem: Microsoft SQL Server pattern can exit with an ECA egine error when extracting port information from the Windows registry Solution: Code fix.|
|#TKU-2190||Problem: IBM WebSphere ILOG JRules BRMS patterns can in certain cases exit with an ECA engine error. Solution: Code fix.|
|#TKU-2191||Problem: Oracle Hyperion Financial Reporting pattern can exit with an ECA engine error in certain circumstances. Solution: Code fix.|
|#TKU-2192||Problem: Adobe JRun pattern can in certain cases extract an incorrect version using path versioning method Solution: Improved path versioning regular expression.|