BMC Atrium Discovery Technology Knowledge Update 2012-Jan-1 is a deliverable for BMC Atrium Discovery 8.2 and 8.3 series.
Release Compatibility
TKU 2012-Jan-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 January (TKU 2012-Jan-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 January 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-01-1.xls
In this Release
New Pattern Modules
| Vendor | Product | Category | Platforms | Instances | Versioning | Product Page |
|---|---|---|---|---|---|---|
| HP | OpenView Performance Insight | Performance Management Software | UNIX, Windows | Y | Y | HP OpenView Performance Insight |
| IBM | InfoSphere Discovery | Data Integration and Access Software | Windows | Y | Y | IBM InfoSphere Discovery |
| IBM | ILOG JViews Enterprise | Application Development Software | UNIX, Windows | Y | Y | IBM ILOG JViews Enterprise |
| IBM | Optim Open Data Manager | Enterprise Resource Management Applications | UNIX, Windows | Y | Y | IBM Optim Open Data Manager |
| IBM | Optim Server | Enterprise Resource Management Applications | UNIX, Windows | Y | Y | IBM Optim Server |
| IBM | Tivoli Service Automation Manager | Change and Configuration Software | UNIX | Y | Y | IBM Tivoli Service Automation Manager |
| Progress Software | OpenEdge RDBMS | Relational Database Management Systems | UNIX | Y | Y | Progress OpenEdge RDBMS |
| Symantec | Security Information Manager | Security and Vulnerability Management Software | UNIX | Y | Y | Symantec Security Information Manager |
Enhanced Pattern Modules
| RFE ref. | Product | Enhancement | SI Key Change | Product Page |
|---|---|---|---|---|
| QM001724267 | IBM Informix Dynamic Server | Discovery of IBM Informix Dynamic Server has been further extended through addition of extended database discovery for this product | N | IBM Informix Dynamic Server - Database Detail Pattern |
| QM001732071 | SAS Server | Path versioning method in the pattern enhanced based on customer feedback | N | SAS Server |
| QM001732150 | HP Data Protector | Package versioning method used by the patterns in the HP Data Protector module enhanced through an addition of a further package name to be used when trying to obtain the product version | N | HP Data Protector |
| QM001732359 | SAP Business Suite | SAP Business Suite model significantly enhanced through addition of patterns to to identify SAP Central Services, SAP Message Server and SAP Enqueue Server as well as through improved relationship creation between the product components | N | SAP Business Suite |
| QM001735638 | IBM Lightweight Infrastructure Server | Pattern updated with alternative method to obtain product installation path resulting in improvement in obtaining version information | N | IBM Lightweight Infrastructure Server |
| #15477 | BEA WebLogic Application Server | Version mapping table (and metadata) in the pattern module updated to add support for WebLogic Application Server 12c | N | BEA WebLogic Application Server |
| - | BEA WebLogic Application Server | Patterns in the WebLogic Application Server module have been enhanced with an improvement in the code logic used to obtain the product version from the registry.xml file | N | BEA WebLogic Application Server |
| - | BMC Remedy AR System | The Server and System patterns have been updated with improvements in the code that manages the creation and maintenance of relationship with the Microsoft SQL Server as well as adding code to create and maintain the relationship to Oracle Database Server when it is part of Oracle RAC. | N | BMC Remedy AR System |
| - | CA Wily Introscope | Based on customer feedback, the Enterprise Manager pattern has been updated to obtain channel and port information as well as including a further refinement to the versioning code. License information is now stored in a Detail node attached to the SI. webView pattern has been updated to create a communication relationship to the Enterprise Manager SI. Furthermore, port information is now obtained and stored as an attribute of the SI and the pattern includes a further refinement to the versioning code. | N | CA Wily Introscope |
| - | HP OpenView Performance Agent (OVPA) | The pattern was updated with an additional active versioning method | N | HP OpenView Performance Agent (OVPA) |
| - | HP OpenView Performance Manager (OVPM) | Pattern enhanced through addition of a new version method using Windows registry query | N | HP OpenView Performance Manager (OVPM) |
| - | IBM Cognos Business Viewpoint | Pattern updated to obtain information about and create a communication relationship to the related database server | N | IBM Cognos Business Viewpoint |
| - | IBM Tivoli Provisioning Manager | Pattern module updated with additional patterns for the following components: IBM TPM for OS Deployment, IBM TPM Deployment Engine, IBM TPM Agent Manager, IBM TPM for Dynamic Content Delivery, IBM TPM for Job Management Service Federation, with all SI type strings shortened for the existing patterns. Furthermore, the model for the product was extended by the addition of a second order SI 'IBM Tivoli Provisioning Manager' grouping all the components | Y | IBM Tivoli Provisioning Manager |
| - | IBM Tivoli Service Request Manager | Service Request Manager pattern updated to add support for discovering the product on UNIX/Linux platforms and code to confirm that the product is installed has been improved. Tivoli Process Automation Engine pattern has been updated to use a trigger on Windows only as this component is only running on Windows. Furthermore, the SI key for this component has been simplified as only 1 instance can be installed and running on a host. | N | IBM Tivoli Service Request Manager |
| - | Microsoft Forefront Threat Management Gateway | Pattern enhanced through addition of a new version method using Windows registry query. Build and service pack information is also now obtained and stored on the created Software Instance node. | N | Microsoft Forefront Threat Management Gateway |
Defects Resolved
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2012-Jan-1
| Case No | Defect No | Details | Product Page |
|---|---|---|---|
| ISS03873691 | QM001731481 | Problem: Changes to the Application Server pattern introduced in TKU September 2011 can with certain product installations lead to failure to obtain the edition and version through parsing of the relevant .product file due to potentially incorrect file being parsed
Solution: Code fix to the algorithm choosing the file to be parsed | IBM WebSphere Application Server |
| ISS03878701 ISS03883467 | QM001731729 | Problem: The Microsoft SQL Server extended database discovery pattern can set the database name to be an empty string in case where the database information was discovered via directory listing on SQL server data files and the data file name contains a space. This further causes a failure to sync this Database Detail node to the Atrium CMDB
Solution: Code fix. Pattern updated to handle data file names with spaces | Microsoft SQL Server Extended Database Discovery |
| ISS03799760 ISS03896568 | QM001732947 | Problem: WebLogic Application Server discovery when running as a Windows service is very limited, either not discovering the instances or not obtaining enough information about discovered instances to allow extended J2EE discovery
Solution: WebLogic Application Server (Windows) pattern updated, significantly enhancing the code to identify and model WebLogic Application Server when running as a Windows service | BEA WebLogic Application Server |
| ISS03881427 | QM001733048 | Problem: Informix Dynamic Server pattern can due to a generous regular expression used in the package versioning method, assign an incorrect version to the SI node that is created
Solution: Pattern updated with a stricter regular expression in the package versioning method | IBM Informix Dynamic Server |
| ISS03883376 | QM001733153 | Problem: The extended WebSphere Application Server pattern can exit with an ECA engine error when it encounters an unexpected time format in the log files it parses and tries to then convert this to a time type variable in Atrium Discovery
Solution: Pattern updated with code to handle the variations in the time format in the log file | IBM WebSphere Application Server |
| ISS03880650 | QM001733251 | Problem: In some cases the IBM WebSphere Application Server package versioning does not pick up the package version even though the package is discovered
Solution: Pattern updated with an additional regular expression in the package versioning method | IBM WebSphere Application Server |
| ISS03885793 | QM001735307 | Problem: BMC Remedy AR Server pattern can fail to create a communication relationship between the Remedy AR Server SI and the Microsoft SQL Server SI even though the related DB Server is discovered
Solution: Code fix. Pattern updated with an improved algorithm to detect and create a relationship between the SIs. | BMC Remedy AR System |
| ISS03895752 ISS03892114 | QM001736715 #15251 | Problem: The extended Apache Tomcat pattern can exit with an ECA engine error when it encounters an unexpected time format in the log files it parses and tries to then convert this to a time type variable in Atrium Discovery
Solution: Pattern updated with code to handle the variations in the time format in the log file | Apache Tomcat |
| - | #15290 | WebSphere Application Server pattern has had the regular expression to obtain installation path made slightly more rigorous | IBM WebSphere Application Server |
| - | #15433 | Problem: The package versioning method used in the Server pattern of IBM Tivoli Directory Server module can return different product version on hosts which have had the product upgraded over time. This happens due to the algorithm picking the first version found in a package and the order of packages that match the package regular expression is not guaranteed Solution: Pattern updated with the package versioning code now using the algorithm which picks the highest version found | IBM Tivoli Directory Server |
| - | #15523 | Problem: Actuate BIRT iServer pattern uses an inefficient datastore search
Solution: Pattern updated with a more efficient datastore search code | Actuate BIRT iServer |
| - | #15535 | Pattern code no longer creating a dependency relationship to the application server SI that is running the product as this increases the complexity of the model without providing additional information | IBM WebSphere Business Events |
| - | #15536 | Pattern code no longer creating a dependency relationship to the application server SI that is running the product as this increases the complexity of the model without providing additional information | IBM Lotus Forms Server - Webform Server |
| - | #15538 | Pattern code no longer creating a dependency relationship to the application server SI that is running the product as this increases the complexity of the model without providing additional information | Adobe Macromedia JRun |
| - | #15542 | Pattern code no longer creating a dependency relationship to the application server SI that is running the product as this increases the complexity of the model without providing additional information | IBM Rational Asset Analyzer |
| - | #15547 | Problem: OracleVM VMManager pattern unnecessarily downloads a config file in order to parse it, but this can be achieved by cat/grep combination on the host itself. As the config file can be very large, this can impact the size of the Atrium Discovery datastore over time
Solution: Code fix. Pattern now parses a pre-processed output of the file | Oracle VM |
Labels:
None
Tideway Blog