Technology Knowledge Update 2014-Feb-2
BMC Atrium Discovery Technology Knowledge Update 2014-Feb-2 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
Release Compatibility
TKU 2014-Feb-2 is released in three streams:
- Release compatible with BMC Atrium Discovery 8.3 series
- Release compatible with BMC Atrium Discovery 9.0 series
- Release compatible with BMC Atrium Discovery 10.0 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 components packaged as two entities:
- BMC Atrium Discovery Technology Knowledge Update
- Core - Patterns that model various software products
- Extended Database discovery - Patterns that extend some of the core database patterns to obtain additional detailed information about certain databases
- Middleware discovery - Patterns that obtain detailed information about certain J2EE Application Servers and Web servers
- Network Device Integration Module with associated Network Device definition files, Printer definition files and SNMP Managed Device definition files
- System - Patterns that detect configuration issues and populate Discovery Conditions (Atrium Discovery 8.3.xx , Atrium Discovery 9.0.xx , Atrium Discovery 10.0.xx ) as well as patterns used by the CMDB sync system
- BMC Atrium Discovery Extended Data Pack, which is a separately licensable product.
- 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.
Installation and Upgrade
- Atrium Discovery 8.3 series - Installation and upgrade instructions are provided here
- Atrium Discovery 9.0 series - Installation and upgrade instructions are provided here
- Atrium Discovery 10.0 series - 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-2014-02-1.xls
In this Release
New Pattern Modules
Vendor | Product | Category | Platforms | Instances | Versioning | Product Page |
---|---|---|---|---|---|---|
IBM | Cognos Express | End-User Query, Reporting, and Analysis | Windows | Y | Y |
Enhanced Pattern Modules
RFE ref. | Product | Enhancement | SI Key Change | Product Page |
---|---|---|---|---|
QM001812391 | IBM Cognos Business Intelligence | Support for version 10.2 added to pattern | N | |
QM001813443 | BMC Remedy AR System | Additional file versioning method added when installed within Apache Tomcat as well as package versioning | N | |
QM001813509 | IBM TXSeries | Support for CICS Region added to pattern | Y | |
QM001816185 | Sybase SQL Anywhere (ASA) | Support added for version 11 | N | |
QM001816727 | MongoDB MongoDB | Publisher changed from 10gen to MongoDB | Y | |
QM001817791 | IBM General Parallel FileSystem | Alternative path added to pattern due to looking for mmlsfs command in the wrong location | N | |
QM001818485 | Various | Fixed issue where Oracle service_name was extracted as tns_alias | N | |
QM001818659 | IBM WebSphere Application Server | The pattern trigger was updated with the addition of extra command line arguments | N | |
#TKU-1907 | Oracle Internet Directory | Product version mapping table updated to better handle version 10g release 2 | N | |
#TKU-2051 | Microsoft SQL Server | Pattern now alternatively obtains instance and server name information from the DiscoveredService node if information cannot be parsed from the trigger process command-line | N | |
#TKU-2073 | IBM InfoSphere Information Server | Pattern trigger loosened as too strict. Installation root as grouped SI key now converted to lower case on Windows platform | Y | |
#TKU-2080 | Oracle Automatic Storage Management (ASM) | SI type now uses the full product name of 'Automatic Storage Management' rather than its abbreviation of 'ASM' | Y | |
#TKU-2081 | IBM CommonStore | License details now reported as a separate license detail node | N | |
#TKU-2082 | IBM Cognos TM1 | Pattern now builds "IBM Cognos Analytic Admin Server" SI if it is a part of IBM Cognos Express product | N | |
#TKU-2088 | Microsoft Lync Server | Pattern now distinguishes between Lync Front-End Server and Lync Server Access Edge | Y | |
#TKU-2090 | Adobe Macromedia JRun | Pattern updated to obtain installation root and version for cases when triggering process has relative path on Unix | N |
Defects Resolved
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Feb-2
Defect No | Details | Product Page |
---|---|---|
QM001811914 | Problem: InformixDS pattern could potentially issue ECA error Solution: Updated regular expression to extract server_names on the Unix platform | |
QM001816042 | Problem: Poor error handling of 'cemutlo -n' command output Solution: Better error handling in 'cemutlo -n' command output added | |
QM001816641 | Problem: AIX Host is sometimes removed from HACMP cluster after discovery Solution: Changed HostContainment relationship to unique relationship where type equals LPAR or HACMP respectively | |
QM001818755 | Problem: Pattern sets erroneous "Name" attribute on HostContainer Solution: Fixed issue with SI name | |
#TKU-1533 | Problem: Rational ASE pattern had weak trigger Solution: Trigger has been tightened | |
#TKU-2032 | Problem: Server pattern failed to extract install root from bin64-based trigger process Solution: Regular expression updated to handle bin64-based processes | |
#TKU-2041 | Problem: Package versioning method added unnecessary trailing zero to product version Solution: Trailing zero now removed from product version | |
#TKU-2058 | Problem: Marketing version mapping omitted from pattern Solution: Marketing version mapping implemented | |
#TKU-2061 | Problem: Pattern can report false version from path versioning method Solution: Path normalization implemented to correct issue | |
#TKU-2073 | Problem: Java path in Engine Tier pattern trigger was too strict Solution: Java path in pattern trigger loosened | |
#TKU-2084 | Problem: Pattern unable to create relationship to multiple Jrun servers running on the same host and using the same install_root for versions 8.x and 9.x Solution: Pattern updated to create relations to Jrun | |
#TKU-2092 | Problem: Pattern may trigger on Tomcat Service Manager on Windows and incorrectly create Tomcat SI Solution: Pattern now stops if it has triggered on the Service Manager binary | |
#TKU-2111 | Problem: Agent pattern was reporting product version to wrong level of detail Solution: Product version is now extracted to three levels | |
#TKU-2119 | Problem: SI type does not quite match marketing name Solution: SI type brought into line with marketing name | |
#TKU-2120 | Problem: The generated End-Of-Life (EOL) patterns sometimes had SI types omitted where the list of SI types differed between product versions. Solution: All associated SI types are now included. | [] |
#TKU-2122 | Problem: BMC ProactiveNet Analytics Server pattern can potentially issue an ECA error Solution: The issue has been resolved. | |
#TKU-2124 | Problem: IBM Tivoli Monitoring Portal Server not linking to IBM TEMS on Unix Solution: Updated Tivoli Monitoring Server linking code | |
ISS04209857 | Problem: Microsoft SQL Server pattern sometimes failing to obtain correct bind address which prevents extended database discovery Solution: Pattern now strips out the IPv6 zone index value in case it is retrieved as part of the IP address the SQL Server is listening on | |
QM001821093 | Problem: Update of the BMC Performance Manager pattern released in TKU 2014-Feb-1 creates a model that breaks a cardinality constraint on certain relationships between CIs in the Atrium CMDB. This causes the CMDB sync to fail. Solution: Code fix. Model updated and problematic relationship removed. Code added to remove the relationship if present (for customers who are already on TKU 2014-Feb-1) on first scan of the hosts running BMC Performance Manager. | |
QM001821110/#TKU-2152 | Problem: BMC Patrol Agent pattern can in certain circumstances exit with an ECA engine error. Solution: Code fix. |