Page tree

Skip to end of metadata
Go to start of metadata

BMC Atrium Discovery Technology Knowledge Update 2010-Jun-1 is a deliverable for the Tideway Foundation platform version 7.3 and later as well as BMC Atrium Discovery version 8.0 and 8.1.

Release Compatibility

TKU 2010-Jun-1 is released in two streams:

  • Release compatible with Tideway Foundation 7.3 and BMC Atrium Discovery 8.0
  • Release compatible with BMC Atrium Discovery 8.1


TKU June (TKU 2010-Jun-1) is not compatible with nor supported on versions of Tideway Foundation before v7.3


Customers can access this TKU release from the BMC Electronic Product Distribution Website. If you're 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 of four components packaged as two licensable entities:

  • BMC Atrium Discovery Technology Knowledge Update
    • Core - Patterns that model various software products
    • Database detail - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases
  • BMC Atrium Discovery Extended Data Pack
    • Product Lifecycle - Patterns that populate Atrium Discovery with information about End-of-Life, End-of-Support, and End-of-Extended-Support for versions of certain host Operating Systems as well as versions of certain software products
    • Hardware Reference Data - Patterns and data import CSV file that populate Atrium Discovery with power and heat consumption figures for various hosts.

To see some of the highlights of this release visit the June In The Spotlight Page

Installation and Upgrade

  • Foundation 7.3 and Atrium Discovery 8.0 - Installation and upgrade instructions are provided here
  • Atrium Discovery 8.1 - Installation and upgrade instructions are provided here

A matrix covering ALL commands executed and ALL files retrieved by the patterns is available to our customers as part of the TKU download

In this Release

New Software Instance Patterns

Vendor Product Category Platforms Instances Versioning Module
BMC Transaction Management Application Response Time (TM ART) Performance Management Software Windows Y Y


CA Audit Data Access, Analysis, and Delivery Software Windows Y Y


CA DLP Data Protection and Recovery Software Windows Y Y


IBM Cognos TM1 Executive Viewer Data Access, Analysis, and Delivery Software Windows Y Y


Oracle Automatic Storage Management (ASM) Storage Management Software UNIX Y Y


Quest PerformaSure Automated Software Quality Tools UNIX/Windows Y Y


Quest Shareplex for Oracle Database Development and Management Tools UNIX Y Y


Quest Recovery Manager for SharePoint Data Protection and Recovery Software Windows Y Y


SAP Business Explorer BI End User, Query, and Reporting Analysis Windows Y Y


Sterling Commerce Control Center Data Integration and Access Software Windows Y Y


Enhanced Software Instance Patterns

Vendor Product Enhancement SI Key Change Pattern Module
BMC PATROL Agent The PatrolAgent platform has been enhanced to try to obtain product version by looking at the process path for any child processes of the trigger process, and also to use a user-configurable list of default installation paths N


Oracle Real Application Clusters (RAC) The RealApplicationClusters pattern was extensively re-written to enhance and improve the accuracy of the Oracle RAC model based on customer feedback Y


SAP AG SAP Business Suite The approach taken within the SAP Suite pattern to obtain the system type and version was re-written based on new information available from internal testing and customer feedback. Additionally, another method of versioning SAP Application server - indirectly, based on the version information obtained by the SAP Suite pattern has been implemented Y


Bugs Fixed

The following bugs have been fixed in BMC Atrium Discovery Technology Knowledge Update 2010-Jun-1

Case No Defect No Details Pattern Module
N/A 13114 Problem: The pattern for BMC CONTROL-M/CM for Advanced File Transfer could in certain circumstances cause significant Atrium Discovery slowdown as well as an impact on the scanned host due to the method that was used to try and obtain the path to the binary (for versioning purposes) Solution: The pattern has been simplified and will no longer attempt to execute commands to obtain the path to the binary. Although this may decrease the detection rate, it was deemed preferable to the potential impact it can have on both Atrium Discovery and scanned hosts


ISS03612654 / ISS03612654 QM001663190 / 13149

Problem: Changes introduced in TKU March 2010 to improve success rate of obtaining the path to the Oracle RDBMS installation have unfortunately made the SI key less stable. The installation path (ora_home) can change between scans (not constantly but once) which can lead to duplicate Software Instances being created.

Solution: A number of improvements have been applied to the Oracle RDBMS and Oracle TNS Listener patterns:

  • installation path is no longer part of the Oracle RDBMS SI key as it is unlikely to be needed
  • Parsing of oratab file is again made the primary method of obtaining the path to the Oracle RDBMS installation
  • Linking between Oracle RDBMS and TNS Listener was made stricter to prevent incorrect TNS Listener SI being linked to the Oracle RDBMS SI and therefore incorrect installation path being used by the Oracle RDBMS SI


ISS03603783 13166 Problem: SAP Suite pattern uses incorrect parameter for the Oracle SID within the SQL query it generates when the backend database is Oracle Solution: The code in the pattern was updated with correct parameters.


N/A 13198 Problem: Patterns in the BMC BladeLogic Server Automation Suite use registry query as the primary versioning method even though active versioning is also implemented. If active versioning is possible, this method should generally be used first as it is likely to return the most accurate results. Solution: Patterns updated to use active versioning as the primary versioning approach


ISS03589649 QM001655092 / 13213 Problem: SAP Suite pattern can fail to recognize the backend database type for certain types of SAP installation. Solution: Code in SAP Suite pattern improved by adding additional parsing of configuration files to determine the backend database type


ISS03607627 QM001660077 / 13224 Problem: IBM InfoSphere Replication Server pattern can create false positives (incorrectly finding the product) in certain cases where permissions on the host prevent certain active commands which are needed to confirm the existence of the product to run. Solution: Pattern improved to handle the scenario described above


ISS03612034 QM001660644 / 13225 Problem: Symantec VERITAS Cluster Server pattern License Detail node has an attribute whose name is incorrect - 'licenses_key' attribute should be named 'license_key' Solution: Pattern code updated to resolve this issue


N/A 13229 Problem: Patterns in Oracle Essbase module have an incomplete SI key, missing the host node key attribute. This could potentially lead to an SI being linked to multiple host nodes. Solution: Pattern code update to improve the SI key of each pattern.


N/A 13234 Problem: Certain patterns that use Apache Tomcat process as their trigger can be made more efficient by the trigger regular expression being more specific in expecting catalina_home (or another specific installation directory path) path to be present as part of the Tomcat process. The reason for this is that these patterns need to be able to extract the catalina_home path (i.e. the installation path) in order to confirm existence of the product they identify Solution: Trigger for these patterns made more selective.


ISS03611031 QM001660894 / 13235 Problem: Depending on the system type encountered, the SAP Suite pattern is not correctly parsing the SAP system type as well as its version Solution: Parsing of the database query output and subsequent algorithm to assign system type and version information was completely re-written.


ISS03614695 / ISS03617072 QM001661002 / QM001661579 / 13236 Problem: Certain version of MS SQL Server 2005 and 2008 not mapped to the appropriate product (marketing) version Solution: Version mapping table updated.


N/A 13243 Problem: In some patterns that identify database products, the listening port information may be stored on the SI either as integer or string. Since the Software Instance produced by these patterns are used by other patterns, this attribute needs to be stored consistently Solution: Code updated to ensure that the port attribute is always stored as a string.


N/A 13244 Problem: IBM FileNet IDM Desktop pattern ails to identify product on hosts where there isn't at least part of the path (containing 'FileNet') in the trigger process. This approach is proving too restrictive. Solution: Pattern updated to make the trigger less restrictive but additional checks put in place to confirm that the product is actually installed on the host where the pattern triggers


N/A 13247 Problem: Oracle Database Lite pattern SI has an attribute with non-standard name. The attribute is secure_port and should be ssl_port Solution: Pattern updated and the SI attribute name changed accordingly.


ISS03613116 QM001661427 / 13253 Problem: The main Solaris Zone pattern can continue even if it has not obtained a handle to the underlying Host node. This will then lead to a 'None' being passed to the search service which can have an impact on the performance of Atrium Discovery. Solution: Pattern updated with code to ensure that the execution will only continue if the handle to the Host node has been obtained.


ISS03616903 QM001661878 / 13254 Problem: On Windows platform, the BMC Performance Perceiver pattern may stop even though it should not, if it does not obtain the installation path from the registry. The cause of this behaviour is that in certain cases the pattern tries to parse out the installation path of the product from the wrong part of the trigger process Solution: Code fix applied in the pattern to resolve this issue. Additionally, the trigger on UNIX platforms has been made a bit more specific to ensure that the pattern triggers only if it will be able to determine the installation path from the trigger process


ISS03612890 QM001661368 / 13256 Problem: The regular expression used to parse the licensed CPU count from the license command output in Symantec VERITAS Volume Manager, File System, Storage Foundation, Storage Foundation for Windows and Volume Replicator patterns is too restrictive causing the failure of the pattern to collect the licensed CPU count Solution: Code fix applied to resolve the issue and verified against multiple data sources


ISS03618601 QM001661993 / 13258 Problem: BMC Performance Assurance Agent PerformanceAssurancePerform pattern will attempt registry queries to obtain port information even on UNIX hosts as it does not check the OS type of the host before performing this discovery call. Solution: Code fix in the pattern to resolve this issue


N/A 13279 Problem: McAfee VisrusScan pattern can in certain circumstances set to 'None' the version and product_version attributes of the SI. The standard behaviour is for these attributes to be set to empty string if the version cannot be obtained Solution: Code fix in the pattern to resolve this issue. If version is not obtained, version and product_version attributes are set to empty string


N/A 13280 Problem: Package versioning approach in Microsoft Office Communicator pattern will fail to obtain the version of the product if the version installed is 2007 R2. Solution: Support added in the pattern through an additional regular expression to enable package versioning of Microsoft Office Communicator 2007 R2


N/A 13281 Problem: The regular expression for instance and copy name extraction in the IBM DB2 RDBMS pattern may fail to extract the information Solution: Code fix in the pattern to resolve this issue.


N/A 13282 Problem: The logic used in the IBM DB2 pattern as to when to collect the edition and license information can lead to this information not being collected. Solution: Removed dependency between edition and licensing detail. A licensing detail node is now created for each and every license (per installation directory) returned by the db2licm -l command


N/A 13298 Problem: In IBM Tivoli Storage Manager pattern, the regular expression to extract the installation root can match even if this path is not absolute. Furthermore, the SI key does not need to have the full trigger process but should use the installation root instead. Solution: Code fix in the pattern to resolve these issues. SI key has been changed for both IBM Tivoli Storage Manager Server and Client patterns.


  • No labels