Technology Knowledge Update 2012-Nov-1
BMC Atrium Discovery Technology Knowledge Update 2012-Nov-1 is a deliverable for BMC Atrium Discovery 8.3 and 9.0 series.
Release Compatibility
TKU 2012-Nov-1 is released in two streams:
- Release compatible with BMC Atrium Discovery 8.3 series
- Release compatible with BMC Atrium Discovery 9.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 of components packaged as two licensable 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 ) 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.
Installation and Upgrade
- Atrium Discovery 8.3.00 - Installation and upgrade instructions are provided here
- Atrium Discovery 9.0.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-11-1.xls
In this Release
New Pattern Modules
Vendor | Product | Category | Platforms | Instances | Versioning | Product Page |
|---|---|---|---|---|---|---|
Axway | SecureTransport | Data Integration and Access Software | UNIX | Y | Y | |
Layer 7 | SecureSpan SOA Gateway | Other Application Server Middleware | UNIX | Y | Y | |
Oracle | Data Service Integrator | Data Integration and Access Software | UNIX/Windows | Y | Y | |
TIBCO | Adapters | Event-Driven Middleware | UNIX/Windows | Y | Y |
Enhanced Pattern Modules
RFE ref. | Product | Enhancement | SI Key Change | Product Page |
|---|---|---|---|---|
QM001735354 | Oracle (BEA) WebLogic Server | Oracle WebLogic pattern was enhanced to attempt to deal with scenarios where the process command line is greater than the OS limit and is therefore truncated leading to the pattern not triggering due to the original trigger condition relying on arguments at the very end of the process command-line. The pattern now includes additional trigger conditions combined with checks to confirm that the process it has triggered on is a WebLogic Server | N | |
QM001768307 | Oracle RDBMS | Oracle TNS Listener pattern has been updated with an improved method of locating listener.ora file path, when it is located in a non-standard directory | N | |
QM001770156 | SAP Business Suite | Patterns within the SAP Business Suite module have been enhanced with additional versioning methods | N | |
QM001771108 | Oracle (BEA) WebLogic Server | Pattern performing extended J2EE discovery of Oracle WebLogic Server has had the model of the J2EE Domain node updated to not include the hostname to properly represent multiple servers sharing the same domain | N | |
QM001771280 | Oracle (BEA) WebLogic Server | Oracle WebLogic pattern was enhanced with an additional method for locating the config.xml file (required for file based extended J2EE discovery) through parsing of the domain-registry.xml file which is present on the recently released versions of WebLogic Server | N | |
QM001771608 | Oracle Siebel CRM | Patterns in the Oracle Siebel CRM module were enhanced, based on customer feedback, with more robust parsing of data when performing file based versioning | N | |
QM001773148 | SAP MaxDB | Patterns in the SAP MaxDB module were updated, based on customer feedback, with an improved regex to parse the installation path of the SAP MaxDB components, which in turn assists in file based versioning of the product | N | |
QM001773199 | Red Hat KVM | The pattern that creates a relationship from virtual Host node to the KVM VM SI it is running within has been updated with an additional trigger condition to take into account newer releases of KVM which are part of Red Hat Enterprise Virtualization setups | N | |
ISS03994141 | Red Hat JBoss Application Server | Red Hat JBoss Application Server pattern was further updated to improve the file based versioning method | N | |
#16009 | Java Virtual Machine | Java Virtual Machine pattern updated to support correct identification of OpenJDK VMs | N/A | |
#16604 | Citrix XenServer | Citrix XenServer Xen domain pattern updated to support extraction of domain names when they include white spaces as part of the name | N | |
- | Informatica PowerCenter | Informatica PowerCenter Server pattern was enhanced through addition of registry versioning (Windows platform) and improvements to path versioning | N |
Defects Resolved
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2012-Nov-1
Case No | Defect No | Details | Product Page |
|---|---|---|---|
ISS04015174 | QM001765171 | Problem: In certain environments the Oracle WebLogic Server pattern may create a single SI out of multiple instances of WebLogic Server because the only unique information about the running instances is related to the domain they belong to. Solution: Oracle WebLogic Server pattern was updated to include domain information in the SI key if this data can be obtained on the first scan, i.e. from the WebLogic Server command-line arguments. | |
ISS04024988 | QM001769093 | Problem: Symantec VERITAS Cluster Server pattern creates duplicate Cluster nodes when scanning Windows hosts that belong to a single cluster Solution: Code fix. Incorrect Cluster node key updated to resolve this issue | |
ISS04035387 | QM001773028 | Problem: BMC Remedy AR Server pattern fails to create a relationship between the Remedy AR Server SI and Microsoft SQL Server SI if the SQL Server is within an SQL Server Cluster Solution: Code fix | |
ISS04045222 | QM001773290 | Problem: Microsoft SQL Server pattern can exit with an ECA engine error under certain circumstances while determining whether SQL Server is part of a cluster Solution: Code fix | |
ISS04050000 | QM001773673 | Problem: IBM Tivoli Service Automation Manager pattern can exit with an ECA engine error when validating that the product is installed if the directory listing it attempts to perform fails (e.g. due to permission error) Solution: Code fix | |
- | #16026 | IBM Rational Performance Tester pattern updated with improved code that handles ageing of License Detail nodes | |
ISS03916697 | #16364 | Problem: Host node 'os_class' attribute for VMware ESX/ESXi was changed in Atrium Discovery 8.3 from 'UNIX' to 'Other' as it is a Hypervisor. This can impact patterns that trigger on instances of ESX Server (when discovered via ssh) and use the 'os_class' attribute to run specific parts of the code (typically related to versioning) Solution: Continuing on from TKU August, an additional set of patterns was reviewed and updated if required. Products for which patterns were updated are listed | |
- | #16436 | Problem: IBM DB2 Connect pattern has no SI management code - once the SI is created, if it cannot be confirmed it will remain until the DB2 RDBMS SI from which it was triggered ages out resulting in potentially a software product being reported to be present when it is no longer the case Solution: Pattern updated with code to manage the SI lifecycle | |
- | #16588 | Problem: Code in Microsoft IIS Extended discovery pattern to extract website information from metabase.xml file (i.e. IIS 6 configuration) fails to do so due to a faulty regex used Solution: Code fix | |
- | #16589 | Problem: Code to extract Microsoft IIS minor version from registry only works if the version obtained is not 0 Solution: Code fix | |
- | #16622 | Problem: IBM Data Studio Administration Client pattern can exit with an ECA engine error if the code that attempts to determine presence of the product cannot access the files it is looking for (e.g. due to permission error) Solution: Code fix | |
- | #16636 | Problem: When synchronizing to CMDB a Mainframe IMS/CICS Transaction (BMC_Transaction) and its related Programs (BMC_Activity), new feature introduced into ADDM 8.3 SP3, the dependency and impact relationships are in the wrong direction. Source should be BMC_Activity and Destination BMC_Transaction, in order to model for example that "Programs impact Transactions". Solution: Pattern updated | ADDM System patterns |