BMC Atrium Discovery Technology Knowledge Update 2014-Nov-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0, 10.0 and 10.1 series.
The November 2014 TKU includes changes to the CMDB Sync mapping (introduced in TKU Jul 2014)
You can enable BMC Atrium Discovery to set the impact attributes directly, rather than relying on Atrium CMDB’s impact normalization rules. Relationships in Atrium CMDB are marked as being “impactful” by setting the
HasImpact attribute to Yes and the
ImpactDirectionattribute to a suitable value. This new data model will become the default in future releases of BMC Atrium Discovery. To enable HasImpact population and the new data model:
In Atrium CMDB, in the Normalization Console Configuration Editor, disable Impact Normalization for the ADDM dataset.
On the BMC Atrium Discovery command line, run the following command: tw_options CMDB_SYNC_DATAMODEL=6. Restart tideway services for the change to be taken into account.
You can start using simple static application modeling.
BMC Atrium Discovery enables you define dynamic automatically-updating application models, using Collaborative Application Mapping and related features. That leads to robust comprehensive application models, but it does require time to investigate the application and define a suitable set of patterns. In some circumstances it is useful simply to manually group some hosts or software instances together to create a “static” application model. Such models are of course not automatically updated, but they are extremely quick and easy to define.
To define a static application model, add Hosts or SoftwareInstances to a group in BMC Atrium Discovery, and give the group a name that starts with “StaticApp:”, in exactly that form. Do not use sub-groups. That causes the creation of a BMC_Application CI in Atrium CMDB, named after the group. For example, a group named “StaticApp: Example Application” results in a BMC_Application CI with name “Example Application”.
Changes to Oracle Database modeling
To support multitenancy introduced in Oracle 12c, the changes to modeling Database Details has been introduced: all the Database Details, like Schemas and Tables, are now linked to the logical databases instead of the Database Software Instance. For versions earlier that Oracle 12c, and for the root database in Oracle 12c and later, the Database Details are also linked to the Software Instance.
The old model, where the Database Details are only linked directly to the Software Instances, is outdated.
TKU 2014-Nov-1 is released in three streams:
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
The release comprises components packaged as two entities:
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-11-1.xls
|Apache||HBase||Nonrelational Database Management Systems||UNIX||Y||Y|
|MapR||M7||Clustering and Availability Software||UNIX||Y||Y|
|IBM||WebSphere Application Server Liberty Core||Application Server Software Platforms||UNIX, Windows||Y||Y|
|CFEngine||Change and Configuration Management Software||UNIX, Windows (client only)||Y||Y|
|IBM||InfoSphere BigInsights||Clustering and Availability Software||UNIX, Windows||Y||Y|
|Apache||Hive||Nonrelational Database Management Systems||UNIX, Windows||Y||Y|
|Cisco||Content Services Switch 11500 Series (CSS)||Application Server Software Platforms||UNIX, Windows||Y||Y|
|Oracle||Business Transaction Management||Transaction Processing Monitors||UNIX||Y||Y|
|BMC||Release Lifecycle Management||Supply Chain Management||UNIX, Windows||Y||Y|
|Apache||Cassandra||Nonrelational Database Management Systems||UNIX, Windows||Y||Y|
|IBM||Worklight||Other Application Server Middleware||UNIX, Windows||Y||Y|
|Oracle||Utilities Data Model||Relational Database Management Systems||UNIX||Y||Y|
|Apache||Zookeeper||Clustering and Availability Software||UNIX, Windows||Y||Y|
|RFE ref.||Product Page||Enhancement||SI Key Change|
Oracle Management Packs pattern has been updated with the following changes:
|-||The Apache Hadoop was enhanced to model two new Components: Apache Hadoop YARN and Apache Hadoop MapReducere.||N|
|QM001862161||Microsoft Hyper-V virtualization namespace was changed for Windows 2012 R2.||N|
|QM001821249||Microsoft SQL Server has been enhanced.||N|
|QM001861501||The pattern has been updated to model FTP Site, FTP Applications and FTP Virtual Directory details.||N|
The BMC Atrium CMDB pattern has been updated with the following changes:
The BMC Performance Manager Portal pattern has been updated with the following improvements:
|QM001861749, QM001854578 (Idea 5668)|
The Oracle RDBMS pattern has been updated with the following improvements:
|QM001862615 (Esc 064472)||Symantec VERITAS Volume Replicator (Windows) The Symantec VERITAS Volume Replicator pattern does not create a Symantec VERITAS Volume Replicator SI for Windows, which should be licensed separately.||N|
The Microsoft Internet Information Services - Extended Discovery pattern was enhanced to do the following:
|Esc 066000||The Sun Java System Webserver pattern was improved to obtain the product and full version on iPlanet Webserver and Sun ONE / Sun Java System Webserver correctly.||N|
|QM001864736 (Esc 065746)|
The BMC Patrol Agent pattern has been updated with the following:
|Esc 066149||J2EEInferredModel||The J2EEInferredModel pattern has been updated to avoid a ECA Error that sometimes happened during the Tomcat Extended Discovery.||N|
|TKU-2284||BMC Decision Support for Server Automation now is connected to the BMC Server Automation server.||N|
The BMC Release Process Management pattern was updated with the following changes:
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Nov-1
|Defect No||Details||Product Page|
|QM001863252 (Esc 065700)||Problem: The Microsoft Message Queuing might through an ECA error. Solution: Code fix.|
|QM001864621 (Esc 066361)||Problem: Scan never ends when IBM WebSphere Application Server extended discovery is triggered. Solution: Code fix.|
|QM001865380 (Esc 066500)||Problem: The Microsoft Biztalk pattern did not recognize Biztalk Group as Software Instance. Solution: Code fix.|
|QM001863909 (Esc 065639)||Problem: The pattern could create an invalid host containment relationship. Solution: Code fix.|
|TKU-2416||Problem: The Nginx Webserver pattern retrieves the install_root incorrectly for the NginxWebServer SI. Solution: Code fix.|
|TKU-2364||Problem: The BMC CONTROL-M Enterprise Manager pattern sometimes fails to retrieve the install_root. Solution: Code fix.|
|TKU-2323||Problem: IBM InfoSphere DataStage reports incorrect publisher for version 7.5.0. Solution: Code fix.|
|TKU-2180||Problem: The Apache HTTPD-based Webservers pattern versioning can infer version where none is intended. Solution: Code fix.|
|TKU-2245||Problem: The BMC BladeLogic Server Automation Suite pattern does not use path versioning. Solution: Code fix.|
|TKU-2365||Problem: BMC Batch Discovery has inadequate false positive check. The pattern should only create an SI if the relevant text exists in installed-versions.txt. Solution: Code fix.|
|TKU-2404||Problem: The IBM Tivoli Enterprise Console pattern uses old branding for the IBM Tivoli Enterprise Console Event Console SI (IBM Tivoli Enterprise Console UI Console). Solution: Code fix.|
|TKU-2397||Problem: The CA Clarity pattern uses old branding for the CA Clarity System Administration SI (CA Clarity Niku System Administration Service). Solution: Code fix.|
|TKU-2183||Problem: The product version extraction for HP OpenView Operations has to be more granular. Solution: Code fix.|
|TKU-2234||Problem: The IBM Tivoli Key Lifecycle Manager pattern sometimes fails to trigger. Solution: Code fix.|
|TKU-2384||Problem: The IBM WebSphere Extended Deployment pattern fails to discover IBM WebSphere Extended Deployment version 7.0 and 8.0 correctly. Solution: Code fix.|
|TKU-2383||Problem: The BEA AquaLogic Enterprise Security pattern fails to discover BEA AquaLogic Enterprise Security version 4.1 and 4.2 correctly. Starting from 4.1, the type of the modeled SI should be BEA WebLogic Enterprise Security Administration Server. Solution: Code fix.|
|TKU-2386||Problem: The SAP Crystal Query Server pattern modeled an SI with incorrect type for versions earlier than 9.0. Solution: Code fix. Now the pattern models a Software Instance with Crystal Report Application Server type for earlier versions.|
|TKU-2382||Problem: The Symantec VERITAS Storage Foundation pattern fails to discover correctly Symantec VERITAS Storage Foundation version 6.0 and higher. Starting from 6.0, the type of the modeled SI should be Symantec VERITAS Storage Foundation. Solution: Code fix.|
|QM001856886||Problem: On UNIX and windows, the agent for CA Autosys R11 is not discovered. Solution: Code fix.|