BMC Atrium Discovery Technology Knowledge Update 2014-Mar-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
The March 2014 TKU includes changes to the CMDB Sync mapping
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-Mar-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-03-1.xls
|IBM||Cognos Data Manager||End-User Query, Reporting, and Analysis||UNIX/Windows||Y||Y|
|Oracle||Hyperion Data Relationship Management||Financial Performance and Strategy Management Applications||Windows||Y||Y|
|Oracle||Hyperion Financial Data Quality Management||Financial Performance and Strategy Management Applications||Windows||Y||Y|
|Oracle||Hyperion Foundation Services||Financial Performance and Strategy Management Applications||Windows||Y||Y|
|Oracle||Hyperion Planning||Financial Performance and Strategy Management Applications||Windows||Y||Y|
|RFE ref.||Product||Enhancement||SI Key Change||Product Page|
|QM001784791 / QM001795372||Hardware Reference Data mapping|
The pattern that performs mapping between Host nodes and HRD nodes enhanced to create relationships based on both exact matches of key attributes as well as best matches where this approach can be taken.
|QM001812883||Oracle Hyperion Financial Reporting / Oracle Essbase||Patterns for Oracle Hyperion Financial Reporting and Oracle Essbase improved with addition of path versioning approach. Oracle Hyperion Reporting & Analysis Framework Agent pattern added to the Oracle Hyperion Financial Reporting pattern module.||N|
|QM001817382||BMC Transaction Management Application Response Time"||BMC TMART Central Application Server pattern enhanced to add support for creating relationships to related Oracle database installation when it is running as part of Oracle RAC||N|
|QM001818665||Java Virtual Machine||Java Virtual Machine pattern updated with a simplified versioning command (when executed on Solaris or Linux)||N|
|QM001819697 / QM001821989||Symantec VERITAS NetBackup||Performance of the code that creates relationships between the Symantec VERITAS NetBackup Client SI and Symantec VERITAS NetBackup Server SI significantly improved. Furthermore, an additional trigger condition added to the Symantec VERITAS NetBackup Client to improved identification of the product.||N|
|QM001819862||IBM InfoSphere Guardium S-TAP Agent||IBM InfoSphere Guardium S-TAP Agent pattern enhanced through addition of active versioning method and further package regular expression to the package versioning method.||N|
|QM001819868||Oracle Business Process Management|
Pattern significantly enhanced to add support for discovery of the product when running as an Apache Tomcat application. File versioning approach added (when running within Apache Tomcat). The ehancements have necessitated an SI key change.
|QM001820008||Oracle WebLogic Server - extended discovery||Extended discovery of Oracle WebLogic Server has been enhanced through addition of a method to identify related Oracle databases using tns alias information.||N/A|
|QM001820069||McAfee VirusScan||Pattern enhanced through addition of registry versioning which is now the primary version method (attempted before package versioning).||N|
|QM001820316||IBM DB2 RDBMS||Extended IBM DB2 discovery pattern updated with a configuration option to control whether the list of schemas is obtained or not (enabled by default).||N|
|QM001820592||Microsoft Lync Server||The pattern module was enhanced through addition of a pattern to identify and model Microsoft Lync Persistent Chat Server||N|
|QM001820768||Symantec VERITAS Cluster Server||Symantec VERITAS Cluster Server updated to use a different trigger process in order to improve identification of the product.||N|
|QM001820821||Xen Source Xen Domain Virtualization Software / Oracle VM||Patterns updated to add an option (user configurable) to execute the 'virsh' command using privilege escalation if the same command fails to obtain the data without privilege escalation.||N|
|QM001821049||Citrix XenServer||Citrix XenServer pattern updated to correctly handle creation of relationships between the virtual hosts and the physical host when there are a number of physical hosts in a cluster.||N|
|QM001821996||Oracle Database Server||The pattern now compares results of file versioning and path versioning approach and if different uses the result that is likely to give more accurate version information||N|
|#TKU-2049 / #TKU-2050||Microsoft Exchange Server||Microsoft Exchange Server pattern updated with a further method to obtain edition information on modern versions of the product. Microsoft Exchange Server Database Availability Groups pattern now also obtains information about cluster resources and stores these as Detail nodes on the SI.||N|
|#TKU-2144||BEA AquaLogic Enterprise Security||Pattern updated to store discovered license information as a Detail node instead of attributes on the SI||N|
|#TKU-2145||BEA MessageQ||Pattern updated to store discovered license information as a Detail node instead of attributes on the SI||N|
|#TKU-2148||BEA WebLogic Integration||Pattern updated to store discovered license information as a Detail node instead of attributes on the SI||N|
|#TKU-2149||BEA WebLogic Real Time||N|
|#TKU-2150||Borland SilkTest||Patterns updated to store discovered license information as a Detail node instead of attributes on the SI||N|
|US172926||IBM Cognos Business Intelligence||File versioning slightly improved.||N|
|-||Apache Hadoop||Package versioning updated, added a user configurable list of paths to locate configuration information (in case it cannot be located relative to the trigger process). Finally, a pattern added to model the Apache Hadoop Core HDFS Cluster.||N|
|-||IBM InfoSphere Federation Server|
Pattern trigger updated to add support for older versions of the product. SI type is set based on the version of the product. SI key updated to improve the way the product is modelled.
|-||IBM DB2 Connect||In the pattern, the db2licm command can now be run with elevated privileges on UNIX/Linux platforms (if configured by the user) to enable active versioning where the ADDM login user does not have login permissions to run this command. Pattern also enhanced with improved registy versioning (Windows platform)||N|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Mar-1
|Defect No||Details||Product Page|
|QM001816716||Problem: Sybase ASE pattern fails to parse correctly complex Sybase ASE interface files leading to incorrect data being set on the SI. This in turn causes an error in the Sybase ASE extended database discovery pattern. Solution: Code fix. Parsing of the complex interfaces file corrected.|
Problem: In certain cases, hosts in the same Solaris Cluster can have a different publisher set as part of the SI type due to failure to obtain version information on one of the hosts (environmental issue). As the SI and Cluster node keys are based on the SI type value, this can lead to duplicate Cluster nodes being created containing the Solaris Cluster SIs which have the matching publisher in the SI type.
Solution: SI and Cluster node key changed to no longer include the publisher information.
|QM001817637 / QM001818359||Problem: IBM InfoSphere Replication Server is either in some cases not detected on hosts where it is installed or in some cases is incorrectly detected even though it is not installed. Solution: IBM InfoSphere Replication Server pattern significantly change and now relies on a more reliable method to detect the presence of the product - output of IBM DB2 'db2licm' command (executed by the IBM DB2 RDBMS pattern). In IBM DB2 RDBMS pattern the db2licm command can now be run with elevated privileges on UNIX/Linux platforms (if configured by the user) to enable discovery of licensable options / products in environments where the ADDM login user does not have login permissions to run this command|
|QM001818651||Problem: Microsoft SQL Server extended database discovery pattern can fail to correctly handle error output of the 'osql' command leading to creation of invalid DatabaseDetail nodes Solution: Code fix. Handling of 'osql' command output improved.|
|QM001818939||Problem: Symantec VERITAS Cluster Server pattern can in certain cases create duplicate Cluster nodes as the pattern assumes that the internal identifiers that are used in the key are obtained in the same order from all the hosts that belong to the cluster. This is not necessarily the case Solution: Code fix. Internal identifiers are sorted in alphabetical order before being used in the key.|
|QM001819126||Problem: Scanning of hosts running Apache Tomcat application server hosting a large number of applications can cause peformance issues due to parsing of large log files to determine the running state of the applications. Solution: Code fix. Removed code that determines the running state of applications as it can be only determined by parsing very large log files which in turn causes performance issues.|
|QM001819908 / QM001820927||Problem: Publisher and category metadata is missing from VMwareESXiVM and vSphereVM patterns - this can cause issues on sync to the Atrium CMDB (at normalization stage) Solution: Missing information added.|
|QM001820187||Problem: Microsoft SQL Server extended database discovery pattern can fail with an ECA engine error in certain cases while trying to report database size information Solution: Code fix.|
|QM001820188||Problem: CMDB sync pattern that map OS information to CMDB from MFPart nodes generates a failure if OS type is not "z/OS" or "z/VM OS". Solution: The pattern is fixed.|
|QM001820547||Problem: CMDB sync patterns that map some Atrium Discovery node attributes to Atrium CMDB CI sometimes does not set unique enough values for ADDM RE Identification Rules to identify these. This regularly ends up in Duplicated CIs problems for BMC_ComputerSystem CIs mapped from partition Host nodes. Solution: PartitionId (introduced within CMDB 8.1) is now populated for these BMC_ComputerSystem CIs with unique enough values.|
Problem: The SI type for IBM Cognos TM1 Client can switch between two possible values due to the SI key not being unique.
Solution: Code fix. SI key changed to ensure uniqueness
|#TKU-2112||Problem: The various components in the BMC CONTROL-M Business Process Integration Suite currently set product_version to 2 levels but should for this product set it to 3. Solution: Code fix.|
|#TKU-2115||Problem: BMC Impact Manager pattern package versioning may obtain incorrect version from a similarly named (but not correct) package Solution: Code fix.|
|#TKU-2130||Problem: BMC Performance Perceiver pattern currently sets product_version to 2 levels but should for this product set it to 3. Solution:|
|#TKU-2151||Problem: Inconsistent approach in how edition is found between UNIX and Windows platforms in Adobe ColdFusion pattern. Solution: Code fix|
Problem: MS SQL Server pattern needs '$' character removed from servername when performing WMI Query
Solution: Code fix.