Page tree

Configipedia maintenance


The Configipedia documentation space will be undergoing maintenance and will be unavailable on the weekend of 27/28 February 2021.

Skip to end of metadata
Go to start of metadata

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

Release Compatibility

TKU 2010-Aug-1 is released in three streams:

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


TKU August (TKU 2010-Aug-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 components packaged as two licensable entities:

  • BMC Atrium Discovery Technology Knowledge Update
    • Core - Patterns that model various software products
    • Deep Database discovery - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases
    • Deep J2EE discovery (Atrium Discovery 8.2 and above) - Patterns that obtain detailed information about certain application servers
  • 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 August 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
  • Atrium Discover 8.2 - 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
Autonomy Interwoven TeamSite Website Design and Development Tools UNIX, Windows Y Y


Autonomy Interwoven Universal Search Content Management UNIX, Windows Y Y


IBM FileNet Capture Professional Content Management Windows Y Y


IBM InfoSphere Enterprise Records Content Management Windows Y Y


IBM Tivoli Application Dependency Discovery Manager Change and Configuration Software UNIX, Windows Y Y


Oracle Business Intelligence End-User Query, Reporting, and Analysis UNIX, Windows Y Y


Red Hat Directory Server Data Integration and Access Software UNIX Y Y


Red Hat Cluster Suite Clustering and Availability Software UNIX Y Y


Software AG webMethods Integration Server Data Integration and Access Software UNIX, Windows Y Y


Software AG webMethods Broker Message-Oriented Middleware UNIX, Windows Y Y


Symantec Deployment Solution Change and Configuration Software Windows Y Y


New Software Instance Patterns - Atrium Discovery 8.2 only

Vendor Product Category Platforms Instances Versioning Module
Apache Tomcat Application Server Deep Discovery UNIX, Windows N N


IBM Mainframe Bulk Software Discovery

z /OS



Oracle (BEA) WebLogic Application Server Deep Discovery UNIX, Windows N N


VMware ESXi Virtual Machine Software UNIX Y Y


Enhanced Software Instance Patterns

Vendor Product Enhancement SI Key Change Pattern Module
IBM Tivoli Key Lifecycle Manager Pattern for the UNIX version of IBM Tivoli Key Lifecycle Manager was added to the pattern module. N


Informatica PowerCenter Model for the Informatica PowerCenter Server was changed to improve the accuracy of reporting of number of instances running. The model now creates an SI per running installation (i.e. per each detected installation directory) Y


Sterling Commerce Control Center The trigger condition in the Engine and Console patterns has been made slightly less specific based on customer feedback. An additional trigger process format has also been added for the Windows platform N


Oracle Database In the TNS Listener pattern we improved the way eBusiness instances are handled by the TNS Listener pattern, instance names of APPS_X and X are now treated as separate instances Additionally some changes were made to the internal logic of the Oracle Database Server pattern where the Oracle Database Software Instance obtains the ora_home variable from a related TNS Listener Software Instance N


Symantec Management Platform The Agent pattern was enhanced by adding another method to obtain the installation path. N


Symantec VERITAS NetBackup The license expiry date stored within the Licensing Detail node created by the Server pattern is now stored following the convention used in other patterns (YYYY/MM/DD) N


Symantec VERITAS SANPoint Control The pattern was enhanced by addition of ability to version the product on the AIX platform. N


Bugs Fixed

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

Case No Defect No Details Pattern Module
N/A 13321 Problem: Customer has reported that parsing of edition from the nodelock file sometimes fails. In addition to this, the command executed to obtain license information may sometimes reside in a different path. Solution: Improved regular expression to get edition from nodelock file; 'db2licm -l' is now additionally executed at <user_homedir>/sqllib/adm


N/A 13350 Symantec VERITAS Storage Foundation pattern had code which creates second order SI updated to use model.setContainment() calls as per best practice guidelines.


N/A 13405 Problem: In certain rare conditions search that tries to reference a node or relationship created by the pattern if there is no asynchronous function which causes the changes to be written to the datastore can fail with OBJECT_NOT_EXIST ECA Engine error. A number of patterns are affected. Solution: Search call re-worked to initially locate the node by its key prior to using it.


N/A 13407 Problem: Certain patterns have been coded to execute 'reg query' command on Windows platform using 'cmd /c' which fails when remcom is used to execute this command. Solution: The patterns have been updated to no longer use 'cmd /c' for 'reg query' command as in fact this is not required.


ISS03627934 QM001668546 / 13432 Problem: On appliances running under a heavy load, IBM Tivoli IntelliWatch pattern can fail as a nodeset which is being tested can become unavailable (no longer cached). Solution: Code re-worked to copy the nodeset to a local variable.


ISS03640978 QM001668732 / 13434 Problem: Adobe ColdFusion pattern can fail to identify Adobe ColdFusion 7 depending on the options used to start the product. Solution: Pattern updated with additional trigger conditions based on customer feedback


ISS03643044 QM001669111 / 13439 Problem: Active versioning approach in Oracle Clusterware pattern requires in most cases elevated privileges, but no option to use these has been provided in the pattern Solution: Pattern updated to include configuration option to enable running the command with elevated privileges


ISS03643042 QM001669118 / 13440 Problem: Oracle RAC pattern fails to parse the 'permission denied' message when attempting to run a command on a host and does not re-attempt to run this command with elevated privileges even when this option has been enabled. Solution: Code fix - parsing of the command output improved.


ISS03643051 QM001669145 / 13446 Problem: When parsing the 'readme.txt' file, ApplicationServerOC4J pattern in Oracle Application Server module fails to parse it correctly on hosts running Oracle Application Server Solution: Additional parsing code added to account for the change of the format of the file.


N/A 13459 Problem: The value with which the Citrix Xen Server pattern populates xen-label attribute in the SI contains end-of-line characters. Solution: Pattern updated to ensure that the value being populated does not contain these special characters.


ISS03643077 QM001669163 / 13465 Red Hat GFS pattern fails to parse the 'permission denied' message when attempting to run a command on a host and does not re-attempt to run this command with elevated privileges even when this option has been enabled. Solution: Code fix - parsing of the command output improved.


ISS03643211 QM001669218 / 13467 Problem: The BMC Performance Assurance Agent and BMC Performance Assurance Collector patterns fail to extract install_root from the triggering process arguments, which can then lead to failure to obtain the product version. Solution: Code fix. One of the regular expressions used has been enhanced in each pattern to improve the success rate of obtaining the install root.


N/A 13470 Problem: BMC Event Manager pattern can exit with an ECA Engine error if it fails to parse the configuration path containing version information. Solution: The reason for this is that the result of xpath.evaluate() was not being tested. Pattern updated with code to test the result of parsing the file.


N/A 13473 Problem: Sun Java System Webserver pattern can exit with an ECA Engine error due to not checking if a parent process node was obtained prior to comparing its attribute to a local variable. Solution: Code fix. Pattern updated to test for existence of the node.


N/A 13487 Problem: BMC Remedy AR Server pattern does not include the server name as part of the 'name' SI attribute. Solution: Pattern updated to follow the best practice guidelines and include the server name within the 'name' SI attribute


ISS03645248 QM001670895 / 13515 Problem: SI 'type' attribute in the Microsoft Communications Server Components pattern can be left unset in the case where information about the type of the component cannot be obtained from the trigger process arguments. Solution: Code fix. Pattern will now set a default type 'Microsoft Office Communications Server Component' if the exact type of the component has not been obtained.


  • No labels