BMC Atrium Discovery Technology Knowledge Update 2010-Feb-2 is a deliverable for the Tideway Foundation platform version 7.2 and later as well as BMC Atrium Discovery version 8.0 and 8.1.
| Note: TKU 2010-Feb-2 is a re-release of Technology Knowledge Update February 2010 which fixes two serious issues (Defect no. 12957, 12982) identified in the original release of Technology Knowledge Update February 2010 (TKU 2010-Feb-1). |
| Note: If you have already installed the previous version of the Technology Knowledge Update for February 2010, it is recommended that you install this latest version of the Technology Knowledge Update release and then remove the previous version from the appliance |
Release Compatibility
TKU 2010-Feb-2 is released in three streams:
- Release compatible with Tideway Foundation 7.2 (subset - does not contain patterns which require TWF 7.3)
- Release compatible with Tideway Foundation 7.3 and BMC Atrium Discovery 8.0
- Release compatible with BMC Atrium Discovery 8.1
| Note: TKU February (TKU 2010-Feb-2) is not compatible with nor supported on versions of Tideway Foundation before v7.2 |
Download
Customers can access this TKU release from either the BMC Electronic Product Distribution Website or the Tideway Downloads site (Download Area->latesttku). 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
Contents
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 February In The Spotlight Page
Installation and Upgrade
- Foundation 7.2/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
Technology Knowledge Update
New Software Instance Patterns
| Vendor | Product | Category | Platforms | Instances | Versioning | Module |
|---|---|---|---|---|---|---|
| BMC | Impact Manager | Event Automation Tools | UNIX, Windows | Y | Y | BMC.ImpactManager |
| BMC | Performance Assurance Console | Performance Management Software | UNIX, Windows | Y | Y | BMC.PerformanceAssuranceConsole |
| BMC | Performance Perceiver | Performance Management Software | UNIX, Windows | Y | Y | BMC.PerformancePerceiver |
| BMC | Atrium Discovery and Dependency Mapping (Legacy) | Change and Configuration Software | Windows | Y | Y | BMC.ADDM |
| BMC | Event Manager | Event Automation Tools | UNIX, Windows | Y | Y | BMC.EventManager |
| BMC | Performance Assurance Agents | Performance Management Software | UNIX, Windows | Y | Y | BMC.PatrolPAPerform |
Enhanced Software Instance Patterns
| Vendor | Product | Enhancement | SI Key Change | Pattern Module |
|---|---|---|---|---|
| Apache Foundation | Apache Tomcat | Apache Tomcat pattern compatible with ADDM 8.1 now also adds a new method of obtaining CATALINA_BASE and CATALINA_HOME on Windows by querying the registry. All versions of Apache Tomcat pattern module also have improved the SI key generation. Long part of the key is hashed to prevent very long keys. In addition to this, if CATALINA_BASE or CATALINA_HOME are known, they are used for creation of the SI key | Y | ApacheFoundation.Tomcat |
| BMC | Atrium Discovery and Dependency Mapping (Tideway Foundation) | Pattern module updated with additional patterns that identify newly added components of the product. Additionally, the SI type changes depending on the version of the product obtained. | Y | Tideway.Foundation |
| BMC | BladeLogic Client Automation | Pattern enhanced to enable better support for identification and versioning on Windows | N | BMC.BladeLogic.ClientAutomation |
| BMC | Performance Analyzer for Servers | Pattern enhanced to improve the way the product is modelled, update the trigger and update the order of the methods used to version the product. | Y | BMC.PerformanceAnalysisForServers |
| BMC | Performance Manager | Pattern updated to enable a greater number of editions to be recognized | N | BMC.PerformanceManager |
| BMC | ProactiveNet Analytics | Pattern module enhanced significantly. Patterns now support identification and versioning on UNIX platforms and not just Windows. In addition to this, active versioning added on Windows. Server pattern now also attempts to obtain license information if available and then stores it on a Detail Node linked to the SI | N | BMC.ProactiveNetAnalytics |
| BMC | Remedy AR System | Patterns underwent a major rewrite, and support was added for deployed Applications, multiple Servers, and reliable relationships | Y | BMC.RemedyARSystem |
| IBM | DB2 RDBMS | Pattern enhanced to obtain edition information as well as license information. If license information is obtained, it is stored as a Detail Node linked to the DB2 RDBMS SI | Y | IBM.DB2.RDBMS |
| Microsoft | Internet Information Services | Microsoft IIS SI model improved - web sites and web applications are modelled as Detail Nodes linked to the SI. Furthermore, support for identification of IIS 7 added | N | Microsoft.IIS |
| Microsoft | System Center Virtual Machine Manager | Pattern module enhanced significantly. Separate pattern for System Center VMM Agent added. Furthermore, the System Center VMM Server pattern now attempts to identify and create relationships to Microsoft Hyper-V instances managed by the VMM Server. This is achieved by running SQL queries (via JDBC connection) against the Microsoft SQL Server storing the System Center VMM configuration | Y | Microsoft.SystemCenterVirtualMachineManager |
| Microsoft | Cluster Server | Pattern enhanced to use WMI query as a primary method to obtain cluster name | N | Microsoft.MSCluster |
| Symantec | VERITAS Cluster Server | The regular expressions used for License Detail processing were enhanced | N | Symantec.VERITAS.ClusterServer |
| VMware | Virtual Center | VirtualCenterServer pattern enhanced to obtain information about listening ports. List of packages to be searched for during versioning increased. Registry versioning is now used as the primary method in the VirtualCenterServer pattern | N | VMware.VirtualCenter |
Bugs Fixed
The following bugs have been fixed in BMC Atrium Discovery Technology Knowledge Update 2010-Feb-2
| Case No | Defect No | Details | Pattern Module |
|---|---|---|---|
| 22527 | 12529 | Problem: Solaris Zone Container pattern assumes a single IP is always configured per zone. This is not necessarily the case, and in those cases the pattern takes the first IP addressed obtained and ignores the rest.
Solution: Pattern updated to handle multiple IP addresses. The information stored in comma-separated string 'zone_ip_addr' attribute as well as 'zone_ip_addr_list' list attribute on the SI | Sun.Virtualization.Zones |
| 22482 | 12536 | Problem: Microsoft IIS pattern did not identify websites hosted by IIS 7 as it does not fully support modelling of IIS 7
Solution: Pattern module updated and IIS 7 support added | Microsoft.IIS |
| N/A | 12810 | Problem: Microsoft System Center Virtual Machine Manager Server pattern contained registry queries to obtain information about related VMM Agents and SQL Server containing configuration which were only compatible with VMM version 2007.
Solution: Additional registry queries added that now support System Center VMM 2008 and 2008 R2 | Microsoft.SystemCenterVirtualMachineManager |
| 23342 | 12822 | Problem: Microsoft IIS pattern could fail to create a complete list of websites running on IIS if some of those websites had names which partially matched (e.g. ACME and ACME-ANOTHER)
Solution: Microsoft IIS pattern improved to prevent websites not being included | Microsoft.IIS |
| N/A | 12850 | Problem: In Remedy AR System pattern module, the command 'echo $BMC_AR_SYSTEM_HOME' in BMC.RemedyARSystem Server pattern may return unexpected results on some shells Solution: The command was be re-written as: 'env | grep 'BMC_AR_SYSTEM_HOME' | BMC.RemedyARSystem |
| N/A | 12852 | Problem: In Remedy Atrium CMDB pattern module, the command 'echo $ATRIUMCORE_HOME' may return unexpected results on some shells
Solution: The command was rewritten as: env | grep 'ATRIUMCORE_HOME' | BMC.AtriumCMDB |
| N/A | 12881 | Problem: Extended Microsoft SQL Server pattern was recently updated to include a more reliable SQL query of obtaining the list of databases managed by the server. Unfortunately that enhancement introduced a bug in the pattern which would lead to a failure to store the list of databases.
Solution: SQL query modified slightly to return the data in the format expected by the pattern | Microsoft SQL Server - Database Detail Pattern |
| N/A | 12882 | Problem: PerformancePointPlanninServer pattern in Microsoft PerformancePoint Server pattern module can exit with an ECA Engine error if configuration data is not obtained via xpath
Solution: Error handling code related to xpath queries in the pattern has been improved | Microsoft.PerformancePointServer |
| 22941 | 12893 | Problem: IBM DB2 RDBMS pattern does not detect editions of the product
Solution: Pattern enhanced to attempt to obtain edition information | IBM.DB2.RDBMS |
| 23484 | 12900 | Problem: PrismTech JacORB pattern creates an SI whose SI key length can exceed 250 characters which will prevent export to Atrium CMDB and potentially to other destination systems (e.g. databases)
Solution: SI key modified so that most of the key string has an MD5 hash applied to it which keeps the key length short | PrismTech.Xtradyne.JacORB |
| 23484 | 12901 | Problem: Informatica PowerCenter pattern creates an SI whose SI key length can exceed 250 characters which will prevent export to Atrium CMDB and potentially to other destination systems (e.g. databases)
Solution: SI key modified so that most of the key string has an MD5 hash applied to it which keeps the key length short | Informatica.PowerCenter |
| 23542 | 12914 | Problem: In certain cases where IBM WebSphere Application server pattern uses package query versioning method to obtain the version, it was failing to do so as it was missing one of the possible package names.
Solution: An additional package name added to the list of packages to check when performing package query versioning. | IBM.WebSphereApplicationServer |
| 23542 | 12945 | Problem: When attempting to obtain the edition of the product, the IBM WebSphere Application Server pattern compares the filenames from its 'known' list of editions with the filenames in a specific location relative to the trigger process. If the filenames do not match, then the edition is not obtained. The 'Base' edition of the product sometimes has a file with the name 'Base.product' while other versions have 'BASE.product'. Solution: Pattern updated to take this variation into account. | IBM.WebSphereApplicationServer |
| N/A | 12957 | Problem: Apache Tomcat pattern can exit with an ECA Engine error when scanning Windows hosts running Apache Tomcat where the pattern fails to obtain information it requires via registry query.
Solution: Errr handling code improved in the pattern. | ApacheFoundation.Tomcat |
| N/A | 12982 | Problem: Microsoft IIS Services and Microsoft IIS Web Server pattern can exit with ECA Engine error when if they trigger on Windows hosts running IIS 6 and fail to obtain version information
Solution: Error handling code improved in the patterns. | Microsoft.IIS |
Labels:
None
Tideway Blog