BMC Atrium Discovery Technology Knowledge Update 2014-Jul-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
The July 2014 TKU includes changes to the CMDB Sync mapping (introduced between TKU Mar 2014 and TKU Jul 2014)
BMC_ComputerSystemCIs mapped from partition Host nodes are updated and their PartitionIds are set.
BMC_ComputerSystemCIs mapped from Cisco Nexus NetworkDevice nodes are updated and their PartitionIds are set (data only discovered with ADDM 9.0 SP3).
For synchronization with BMC Atrium CMDB version 7.6.03 and higher, you can enable ADDM 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
ImpactDirection attribute to a suitable value. This new data model is recommended and 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 (it prompts for the "system" ADDM user password). Finally, 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-Jul-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-07-1.xls
|AirWatch||AirWatch Mobile Email Management||Security and Vulnerability Management Software||Windows||Y||Y|
|BMC||BMC Capacity Optimization (BCO)||Performance Management Software||UNIX||Y||Y|
|BMC||BMC Cloud Lifecycle Management (CLM)||Cloud Management||Windows/UNIX||Y||Y|
|RFE ref.||Product Page||Enhancement||SI Key Change|
|TKU-2248||Management relationships are created from a BMC BladeLogic Server Automation Suite File Server software instance to the filesystem nodes it uses.||N|
|QM001852280 (Esc 059057)||The versioning in RSCD Agent pattern has been improved to correctly discover the version of BMC BladeLogic Server Automation running on UBUNTU operation system.||N|
|QM001822093 (Esc 059746)||The versioning has been improved to correctly identify installation root.||N|
|TKU-2296||To reflect the naming changes in the recent Entuity releases, the duplicate of 'Entuity' has been removed from SI's type and name attributes. SI key remained unchanged for instance-based SIs, but has been changed for grouped modern versions.||N|
|QM001849980||The versioning has been enhanced to correctly discover the Oracle Coherence v12.1.2.||N|
|TKU-2301||BMC IT Service Management Suite SI is now linked to the BMC Remedy AR System SoftwareComponents instead of linking to the BMC Remedy AR System SI.||N|
|TKU-2295||BMC Performance Assurance Console v9.0, 9.0.01, 9.0.02, 9.0.03, 9.0.04, 9.0.05, 9.5, and 9.5.01 are now supported. Active versioning for UNIX was updated to address the changes in new version.||N|
|TKU-2228||The IBM Tivoli License Compliance Manager pattern was enhanced with improved pattern triggering to support IBM WebSphere Application Server trigger update.||N|
|TKU-2224||The IBM Tivoli Usage And Accounting Manager pattern was enhanced with improved pattern triggering to support IBM WebSphere Application Server trigger update.||N|
|TKU-2237||CA DPL is renamed to CA Dataminder, according to the naming in the new versions.||N|
|TKU-2318||Ability to synchronize BMC_LANEndpoint to BMC_IPEndpoint connectivity for NetworkDevice||N|
|QM001811868||Support of the Oracle Management Pack for Oracle GoldenGate on UNIX platform has been added.||N|
|Support of the BMC Analytics for BSM on UNIX platform has been added and the file versioning has been improved.||N|
|QM001849603||New client-server relationship is created between the Microsoft Windows SharePoint Services software instance and the Sharepoint Configuration Database software instance.||N|
|Esc 059258||The Microsoft Internet Information Services pattern has been enhanced to model the FTP Server running on the Microsoft IIS instance and the dependency relationship between them. The false positive check has been removed.||N|
J2EEInferredModel and RDBMS_Functions patterns are updated in perspective of Oracle RDBMS support
|The J2EEInferredModel and RDBMS_Functions patterns were enhanced to support new·syntax of the JDBC connection. The SID and service name are now extracted correctly.||N|
|QM001849547||The triggering conditions were improved to discover IBM Business Process Manager v7.5.1 correctly (QM001849547).||N|
|QM001822230||Enhanced OracleRDBMS_DBDetails pattern to support Oracle 12c Pluggable Databases (PDBs). PDBs are modelled as DatabaseDetails.||N|
|QM001849557, QM001849559||AirWatch Mobile Email Management pattern now triggers on the AirWatch Mobile Email Management Exchange ActiveSync (EAS) Integration Service.”||N|
|QM001823982||Added support for IBM Cognos Business Intelligence Graphics Service and IBM Cognos Business Intelligence Metadata Service.||N|
|QM001851192\\ QM001851191||Hardware Reference Data for certain IBM models added.||N/A|
|QM001851190||Hardware Reference Data for certain Cisco models added.||N/A|
|QM001851189||Hardware Reference Data for certain Oracle models added.||N/A|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Jul-1
|Defect No||Details||Product Page|
|QM001850601||Problem: Microsoft Exchange Server pattern does not handle special characters (brackets) correctly. For example, if a cluster name includes brackets and there is a cluster member with Microsoft Exchange Server running on it, scanning of this host fails. Solution: Code fix.|
|QM001850793||Problem: Apache Extended Discovery patterns include files masked with a wildcard character in the filename which leads to incorrect pattern behavior. Solution: Code fix - the versioning has been improved to correctly identify installation root.|
|QM001851127||Problem: Incorrect naming is used for Oracle RAC SI located on single host. Solution: Code fix.|
|QM001852135||Problem: BMC Analytics for BSM generates ECA error. Solution: Code fix.|
|QM001852008||Problem: The IBM InfoSphere DataStage pattern could not correctly extract install root in certain cases. Solution: Code fix - the versioning has been improved to correctly identify installation root.|