Technology Knowledge Update 2011-Aug-1
BMC Atrium Discovery Technology Knowledge Update 2011-Aug-1 is a deliverable for BMC Atrium Discovery 8.1 and 8.2 series.
Release Compatibility
TKU 2011-Aug-1 is released in three streams:
- Release compatible with BMC Atrium Discovery 8.1 series
- Release compatible with BMC Atrium Discovery 8.2 series
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 (Atrium Discovery 8.2 and above) - 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)
- 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
- Atrium Discovery 8.1 - Installation and upgrade instructions are provided here
- 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
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-2011-08-1.xls
In this Release
New Pattern Modules
Vendor | Product | Category | Platforms | Instances | Versioning | Product Page |
|---|---|---|---|---|---|---|
HP | Connect-It | Data Integration and Access Software | Windows | Y | Y | |
IBM | InfoSphere Master Data Management Server | Data Integration and Access Software | UNIX | Y | Y | |
IBM | Optim Performance Manager | Database Development and Management Tools | UNIX, Windows | Y | Y | |
IBM | Rational Requirements Composer | Project and Portfolio Management | UNIX, Windows | Y | Y | |
InterSect Alliance | Snare Agent | Event Automation Tools | UNIX, Windows | Y | Y | |
Oracle | Enterprise Service Bus | Messaging Applications | UNIX, Windows | Y | Y | |
Quest | Journal | Enterprise Resource Management Applications | Windows | Y | Y | |
Quest | Reporter | Enterprise Resource Management Applications | Windows | Y | Y | |
Quest | Reporting Console | Enterprise Resource Management Applications | Windows | Y | Y | |
Quest | SQL Optimizer for DB2 LUW | Database Development and Management Tools | Windows | Y | Y | |
Quest | SQL Optimizer for Oracle | Database Development and Management Tools | Windows | Y | Y | |
Quest | SQL Optimizer for SQL Server | Database Development and Management Tools | Windows | Y | Y | |
Quest | SQL Optimizer for Sybase ASE | Database Development and Management Tools | Windows | Y | Y |
Enhancements
RFE ref. | Product | Enhancement | SI Key Change | Product Page |
|---|---|---|---|---|
QM001656533 | IBM WebSphere MQ Message Broker\\IBM WebSphere MQ | IBM WebSphere MQ Message Broker and IBM WebSphere MQ patterns update with code to improve the model for IBM WebSphere MQ Message Broker and to create a communication relationship between the related Software Instances of the two products | Y | |
QM001705642 | Oracle Database Server | Oracle Database Server extended discovery pattern has been updated to also support obtaining database details when credentials use service name and not SID | N | |
QM001712121 | Java Virtual Machine | Pattern enhanced to obtain information on whether the installation of Java VM that is running is part of a JDK or JRE. This information is stored as an attribute. Furthermore, path versioning has been enhanced further with additional regular expressions. | N | |
- | Actuate BIRT Spreadsheet Designer | Actuate Formula One e.Spreadsheet Designer pattern updated to account for the change in the name of the product. The pattern now sets the SI key type based on the version of the product. | Y | |
- | HP Mercury SiteScope | In the HP SiteScope pattern module, the ApplicationServer pattern has been enhanced with addition of file versioning and additional package and registry information to support the other versioning methods. The pattern now also creates Detail nodes to represent the installed monitors. The HP SiteScope Service pattern has been disabled as it doesn't actually create an SI for a major component of the product. Finally, a pattern discovering HP Mercury SiteScope Failover Manager has been added to the pattern module | N | |
- | Microsoft Project Server | Microsoft Project Server pattern module has been enhanced by adding functionality to version MS Project Server 2010. Furthermore, the data model of the product has been improved for all versions of MS Project Server | Y | |
- | Red Hat KVM | Pattern module has been enhanced through addition of patterns to link the Red Hat KVM Software Instance with hosted Red Hat KVM virtual machines where the guest OS is Microsoft Windows | N | |
- | OS Support Details | Support lifecycle information updated for Microsoft Windows 2008, 2008 R2, 7 and AIX 5.3 | N/A |
Bugs Fixed
The following bugs have been fixed in this release
Case No | Defect No | Details | Product Page |
|---|---|---|---|
ISS03762429\\ISS03824514 | QM001707009 | Pattern metadata describing product categories in IBM Cognos PowerPlay, IBM InfoSphere Data Event Publisher and IBM Tivoli Common Reporting pattern modules has been corrected to be consistent with other product patterns for products in the same product category (End User, Query, and Reporting Analysis) | |
ISS03824521 | QM001707009 | Problem: (Oracle) BEA WebLogic Application Server pattern incorrectly creates a new SI in cases where an existing application server instance has been re-started with changes in the command-line arguments Solution: Algorithm to set the SI key has been rewritten which should prevent the duplicate SIs being created. This has led to a change of SI key, so initial scans may show duplicate Software Instances of WebLogic application server until the old SIs are aged out by the system | |
ISS03810203 | QM001713955 | Problem: Quest Toad pattern could exit with an ECA Engine error when performing registry versioning Solution: Code fix. Registry versioning made more robust | |
ISS03796098 | QM001714318 | Problem: SAP Suite pattern missing code to manage obsolete second order SIs Solution: Code fix. Pattern updated with code to manage any 2nd order SIs which are no longer being updated | |
ISS03807228 | QM001715157 | Problem: End of Support dates for Red Hat ES Linux v4 and 5 are incorrect Solution: Pattern updated with dates obtained from Red Hat product lifecycle website | |
ISS03813442 | #14890 | Problem: Current Sybase jConnect and Sybase Java SDK patterns produce a very similar model which leads to duplicate SIs being created Solution: Sybase Java SDK pattern disabled as not required | N/A |
ISS03814680 | QM001717147 | Problem: BMC Remedy AR Server pattern parses incorrectly the information about the related Microsoft SQL Server, for discovered Remedy AR system which use Microsoft SQL Server as the database Solution: Pattern updated with a new parsing algorithm to determine the correct database host | |
- | #14777 | Problem: Code that searches for related software in the Server, ConfigurationAgent and AgentListener patterns of the BMC CONTROL/M pattern module is incorrectly executed even when an instance-based SI is not created Solution: Code fix. Patterns updated to ensure the code is only executed when instance-based SI is created | |
- | #14840 | Problem: With certain Remedy configurations, the BMC Remedy AR Server pattern parses incorrectly the information about the related Oracle Database Server Solution: Pattern updated with a new parsing algorithm to determine the correct database host | |
- | #14843 | Problem: In IBM Informix Dynamic Server pattern, the install_root variable is populated (and its value then subsequently used) even if the installation path is not absolute Solution: Pattern updated to ensure that this information is populated (and value used in versioning) only when the installation path obtained is absolute | |
- | #14861 | Problem: IBM Rational Build Forge Agent pattern, and Symantec VERITAS NetBackup NetBackupClient pattern (if configured by user to try to detect all instances of the NetBackup client) can trigger and create SI nodes on ESXi hosts (Atrium Discovery 8.2 and above). Solution: Code fix. Patterns updated to check the host class Atrium Discovery is in the process of discovering in more detail prior to continuing to execute. | |
- | #14892 | Problem: BMC Transaction Management Application Response Time CentralApplicationServer pattern assumes that version obtained will always have at least major and minor components and if it does not, exits with an ECA engine error Solution: Code fix. Pattern made more robust in dealing with variations in the data obtained from scanned hosts | |
- | #14914\\#14915 | Problem: In certain pattern modules, the code in some of their patterns used to create SI keys is incorrectly implemented, which can lead to a lower number of software instances of this product being detected Solution: Code fix. Patterns updated with corrected code. In all cases SI key has changed slightly which will lead to creation of new Software Instances and ageing of old SIs | |
- | 14972 | Problem: The current Apache Tomcat pattern matches on the Tomcat component within Sun Java Web Console which is a Sun-specific embedded release uses a different version numbering scheme. Solution: As this embedded version of Apache Tomcat is sufficiently different to standalone Apache Tomcat Server, the Apache Tomcat server has been updated to filter out instances of Sun Java Web Console |