BMC Atrium Discovery Technology Knowledge Update 2014-Aug-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
The August 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).
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
ImpactDirection attribute 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 (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-Aug-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-08-1.xls
|Microsoft||Active Directory Domain Services||Data Integration and Access Software||Windows||Y||Y|
|Microsoft||DNS Server||Data Integration and Access Software||Windows||Y||Y|
|Oracle||Cloud File System||File System Software||UNIX||Y||Y|
|Oracle||Traffic Director||Network Management Software||UNIX||Y||Y|
|BMC||FootPrints Service Core||Problem Management Software||Windows, UNIX||Y||Y|
|BMC||Release Process Management||Application Deployment Software||Windows, UNIX||Y||Y|
|Teradata||Database||Relational Database Management Systems||UNIX||Y||Y|
|IBM||IBM WebSphere MQ Cluster||Application Server Software Platforms||Windows, UNIX||Y||Y|
|RFE ref.||Product Page||Enhancement||SI Key Change|
|QM001855629 (Esc 060452)||The pattern was updated with alternative method of handling database sizes to correctly identify all possible values.||N|
MSSQLServerVersionTables for Microsoft SQL Server
|The MSSQLServerVersionTables pattern was updated to cover more version pairs in the Microsoft SQL Server Version Tables.||N|
|QM001853783||The pattern was updated to support alternative possible registry.xml file location.||N|
|QM001853705||The pattern has been improved to correctly perform Oracle 8i extended discovery.||N|
|QM001851914||The pattern has been improved to correctly create relationships between IBM WebSphere Application Server Deployment Manager and Cells with the same name.||N|
|QM001850237||The Oracle Business Activity Monitoring pattern was updated with a new triggering condition. From now on Oracle Business Activity Monitoring triggers on the java process with "-Dbam.oracle.home" argument to handle the situation when Oracle Business Activity Monitoring is installed without Oracle Service Oriented Architecture.||N|
|QM001850235||The Oracle Enterprise Manager pattern trigger was updated to match java process with oracle.sysman.gcagent.tmmain.TMMain parameter.||N|
|TKU-2222||Improved trigger for IBM Maximo Asset Management.||N|
|QM001850069||Improved identification of Oracle MySQL Server process.||N|
|TKU-2317||Improved Software Instance type to correctly report the product name for versions before 8.5 (IBM DB2 Document Manager).||Y|
AirWatch Mobile Email Management
|Some patterns were updated to model additional attributes for the Software Instance (short_name (TKU-2353), listening_ports (TKU-2355)).||N|
|TKU-2297||HSQL Development Group HyperSQL and SAP MaxDB pattern were updated to model additional logical_database_type attribute for the Database Details.||N|
|-||The pattern was updated to support new product versions, and now includes new attributes (listening_ports and expected_ports) and additional attributes (install_root and member_of_clusters). The queue_manager attribute was substituted with the instance attribute.||N|
|-||The pattern was updated to model channels and queues in IBM WebSphere MQ.||N|
|-||The pattern was updated to identify Oracle Database Vault, Oracle Label Security, Advanced Analytics, Advanced Compression, and Active Data Guard options.||N|
|TKU-2344||The pattern was updated to correctly retrieve the service pack and patch version.||N|
|TKU-2331||The Microsoft Lync Server pattern was updated to model an instance attribute for Microsoft Lync Server SoftwareComponent.||N|
|TKU-2242||The BMC BladeLogic Server Automation Suite pattern was updated to model the BMC BladeLogic Server Automation TFTP Server.||N|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Aug-1
|Defect No||Details||Product Page|
|QM001853395||Problem: SAP Business Suite Software Components are not linked to Software Instance. Solution: Code fix.|
|QM001853848||Problem: The Oracle Database Installed Options pattern execution generates ECA error. Solution: Code fix.|
|QM001854563||Problem: Model for HBA cards not sycned to BMC_NetworkPort class in CMDB Solution: Code fix.|
|QM001855277||Problem: The Microsoft Internet Information Services - Extended Discovery pattern execution generates ECA error. Solution: Code fix.|
|QM001855506||Problem: IBM WebSphere Application Server Node Agent creates invalid relationships. Solution: Code fix.|
|QM001855657, QM001822936||Problem: The install root retrieved by Sybase Adaptive Server Enterprise pattern is sometimes incomplete, which results in a failure extracting database details from the log file. Solution: Code fix.|