Skip to end of metadata
Go to start of metadata


BMC Atrium Discovery Technology Knowledge Update 2012-Feb-1 is a deliverable for BMC Atrium Discovery 8.2 and 8.3 series.

Release Compatibility

TKU 2012-Feb-1 is released in two streams:

  • Release compatible with BMC Atrium Discovery 8.2 series
  • Release compatible with BMC Atrium Discovery 8.3 series

Note

TKU February (TKU 2012-Feb-1) is not compatible with nor supported on versions of BMC Atrium Discovery before v8.2.0

Download

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

Contents

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 - Patterns that obtain detailed information about certain application servers
    • Network Device Integration Module with associated Network Device definition files (compatible with Atrium Discovery 8.2.01 and above) and Printer definition files (compatible with Atrium Discovery 8.3 and above)
    • System - Patterns that detect configuration issues and populate Discovery Conditions as well as patterns used by the CMDB sync system
  • 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 February In The Spotlight Page

Installation and Upgrade

  • Atrium Discovery 8.2.00 - Installation and upgrade instructions are provided here
  • Atrium Discovery 8.2.01 and later - Installation and upgrade instructions are provided here
  • Atrium Discovery 8.3.00 - 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 from the BMC Electronic Product Distribution Website. The filename is TKU_Command_File_Matrix-2012-02-1.xls

In this Release

New Pattern Modules

Vendor Product Category Platforms Instances Versioning Product Page
PostgreSQL PostgreSQL RDBMS - Extended Database Discovery Relational Database Management Systems UNIX, Windows N/A N/A

PostgreSQL RDBMS - Extended Database Discovery

Sybase ASE - Extended Database Discovery Relational Database Management System UNIX, Windows N/A N/A

Sybase ASE - Extended Database Discovery

Enhanced Pattern Modules

RFE ref. Product Enhancement SI Key Change Product Page
QM001724723 Microsoft SQL Server Pattern enhanced for SQL Server 2000, added support for obtaining listening IP address when it is part of a cluster N

Microsoft SQL Server

QM001737766 TIBCO Rendezvous Pattern updated with an additional package regular expression for obtaining version information via package query N

TIBCO Rendezvous

QM001737894 SAP Business Suite SAP Business Suite pattern enhanced for handling of SAP configurations when the related DB hostname used is a secondary DNS name. This enables the pattern to succeed in creating the communication relationship between the SAP Business Suite SI and the remote database server SI. Pattern additionally enhanced to add 'Business Information Warehouse' as a known suite type N

SAP Business Suite

QM001739548 N/A Update (based on customer feedback) of Software Product life cycle patterns for Microsoft SQL Server

Software Product Life Cycle Patterns

- Oracle (BEA) WebLogic Application Server Pattern that performs extended J2EE discovery of WebLogic Application server has been enhanced to add support for WebLogic 8.x extended J2EE discovery using configuration file parsing N

BEA WebLogic Application Server

Defects Resolved

The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2012-Feb-1

Case No Defect No Details Product Page
ISS03858864\\ ISS03895043 QM001726285 Problem: The creation of HostContainment relationship by VMware consolidation patterns between Virtual Machine SIs and virtual Host nodes can in turn remove other containment relationships which involve the same virtual Host nodes (e.g. members of Citrix farm which are also virtual hosts are not shown to be members of the Citrix farm) Solution: VMware consolidation patterns updated to create unique containment relationships with a specific type to allow other containment relationships to involve the same virtual Host nodes

VMware Virtual Machine software

ISS03890671 QM001735796 Problem: Trigger process for Microsoft Exchange Server pattern (mad.exe) can be related to Hewlett Packard Motive Chorus software Solution: Pattern updated with an additional check to ensure that Microsoft Exchange has been correctly identified on the host

Microsoft Exchange Server

ISS03891828 QM001736001 Problem: Oracle Database Server can exit with an ECA Engine error in cases where a database instance service name contains a special character (e.g. '+') Solution: Code fix. Pattern regex that extracts the server name updated to improve handling of special characters in service name

Oracle RDBMS

ISS03888942 QM001736615 Problem: The Apache Tomcat extended J2EE pattern may when discovering applications using configuration file approach (Atrium Discovery 8.3), create duplicate SoftwareComponent nodes representing deployed applications if the same application is discovered via two different methods but the results of the name obtained are subtly different Solution: Pattern updated to ensure that even if an application is discovered by both methods, the results obtained align

Apache Tomcat

ISS03869025 QM001739106 Problem: Oracle Coherence pattern trigger may fail to identify some instances of the product Solution: Pattern updated with an improved trigger to increase likelihood of identification of the product

Oracle Coherence

ISS03905525 QM001739211 Problem: SAP Application Server pattern has an incorrect package name in the list of package name regular expressions used in the package versioning approach Solution: Code fix. Incorrect package name removed from the list of package regular expressions

SAP Business Suite

ISS03846546 QM001739235 Problem: Progress OpenEdge Database extended discovery pattern can related DatabaseDetail nodes to more than one Progress Database Software Instance node Solution: Code fix. DatabaseDetail node key updated in the pattern to ensure uniqueness

Progress OpenEdge RDBMS - Database Detail Pattern

ISS03902585 QM001739616 Problem: The Ingres Data Access Server pattern does not create a product_version attribute even if version of the product has been obtained and the 'version' attribute of the SI is populated Solution: Pattern updated with code to set product_version attribute based on the value of the version SI attribute

Ingres Database

- #15462 Problem: SI key in the CentralManagementServer and ReportApplicationServer of the SAP BusinessObjects Enterprise pattern does not correctly model the product Solution: Pattern updated with improved SI key in the patterns within the module

SAP BusinessObjects Enterprise

- #15540 IBM Lotus Connections pattern updated with an improved trigger for the product

IBM Lotus Connections

- #15541 IBM Rational Asset Manager pattern updated with an improved trigger for the product

IBM Rational Asset Manager

- #15543 Problem: Relationship between Apache Derby SI and the related WebSphere Application Server SI cannot be reliably identified Solution: Pattern updated to remove the relationship creation code

Apache Derby RDBMS

- #15555 Problem: xpath.evaluate() used frequently without use of xpath.openDocument() in extended J2EE patterns, and this approach is inefficient Solution: Patterns updated to use xpath.openDocument() whenever this makes sense

Apache Tomcat
IBM WebSphere Application Server
Red Hat JBoss Application Server

- #15645 Problem: The pattern MicrosoftOperationsManager.tplpre will always create an SI of type Microsoft Operations Manager Agent. However, versions 2007 have a name of "Microsoft System Center Operations Manager" Solution: Pattern updated with code to change SI type based on version of the product

Microsoft System Center Operations Manager

  • No labels