BMC Atrium Discovery Technology Knowledge Update 2014-Oct-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
The October 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
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. 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-Oct-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-10-1.xls
|MemSQL||MemSQL||Relational Database Management Systems||UNIX||Y||Y|
|OpenLDAP||OpenLDAP||Identity and Access Management||UNIX, Windows||Y||Y|
|SaltStack||Salt||Change and Configuration Management Software||UNIX||Y||Y|
|Docker||Docker||Virtual Machine Software||UNIX||Y||Y|
|Opscode||Chef||Software Configuration Management Tools||UNIX||Y||Y|
|Microsoft||Message Queuing||Event-Driven Middleware||Windows||Y||Y|
|Pivotal||RabbitMQ||Event-Driven Middleware||UNIX, Windows||Y||Y|
|IBM||Tivoli Access Manager WebSEAL||Data Integration and Access Software||UNIX, Windows||Y||Y|
|RFE ref.||Product Page||Enhancement||SI Key Change|
|QM001859037||The BMC Remedy AR System Server versioning is improved: active versioning is now a primary versioning method, registry versioning is not used any more.||N|
|Esc062112||The Microsoft Windows PowerShell pattern has been improved and creates a RuntimeEnvironment node even when the Microsoft Windows PowerShell is not running during scan.||N|
|QM001859844||The CA Directory pattern now supports discovery of the CA Directory deployed on a UNIX platform. Version 12.0 is now supported.||N|
|QM001860126 Esc 063823 Esc 063812 ISS04362449||The Oracle WebLogic Server pattern was updated with more suitable trigger for discovering instances running as a Windows service. Server name attribute extraction method has been also improved.||N|
|QM001860981||The Oracle Hyperion Financial Reporting pattern has improved trigger mechanism with improved discovery of the legacy system version.||N|
|QM001861008||The IBM Tivoli Storage Manager pattern now supports package versioning for HP-UX deployments of IBM Tivoli Storage Manager Client.||N|
|QM001860730||The pattern was improved to identify the Red Hat JBoss Application Server edition.||N|
|-||Trigger condition has been update in the Oracle Automatic Storage Management pattern.||N|
|QM001861696||A minor issue related to path truncation has been fixed in the Oracle Coherence pattern.||N|
|QM001861699||Simple identification mapping has been improved for Adobe Connect.||N|
|-||The Microsoft Hyper-V pattern was updated to support versions 2012 and 2012 R2.||N|
|TKU-2174||The product version identification was improved for HP Performance Agent.||N|
|TKU-2174||The product version identification was improved for HP Operations Manager.||N|
|-||The Nginx Webserver pattern was updated to support the latest versions: 1.4, 1.5 Release 1, 1.5 Release 2, 1.5 Release 3, 1.5 Release 4, and 1.6.||N|
|QM001855657||Minor issue related to the install root truncation has been fixed.||N|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Oct-1
|Defect No||Details||Product Page|
|QM001860176||Problem: In some circumstances the Apache Tomcat pattern failed with ECA error. Solution: Code fix.|
|QM001860805||Problem: The Red Hat KVM pattern requires enhancement to treat the wrong UUID format correctly. Solution: Code fix.|
|TKU-2406||Problem: In some circumstances the Oracle Enterprise Single Sign-On pattern failed with ECA error. Solution: Code fix.|
|TKU-1847||Problem:The Software Instance type was updated to reflect the recent changes for HP Performance Agent (from HP OpenView Performance Agent to HP Performance Agent). Solution: Code fix.|
|TKU-2394||Problem:IBM LotusConnections pattern creates Software Instances with incorrect branding for modern versions. Solution: Code fix. The pattern was updated to support versions 3.0, 4.5, and 5.0. For versions 4.5 and 5.0 the Software Instance type was updated to IBM Connections. An alternative file versioning method was introduced on Windows platforms.|
|TKU-2320||Problem:The pattern does not account for a recent changes in IBM FileNet Business Process Manager naming. IBM FileNet Business Process Manager has been renamed to IBM Case Foundation. Version 5.2 is now supported and an IBM Case Foundation Content Platform Engine Software Instance is modeled for this version. Solution: Code fix.|
|TKU-2367||Problem:The BMC CONTROL-M pattern populated tw_meta_data_attrs with unnecessary information. Solution: Code fix.|
|TKU-2299||Problem:IBM Rational Jazz Server pattern created a jazz_home attribute even when the value was not discovered. Solution: Code fix.|
|TKU-2313||Problem: The HP Discovery and Dependency Mapping pattern generates a Software Instance with incorrect type. Solution: Code fix. The SI type is now HP Discovery and Dependency Mapping Inventory.|
|TKU-2307||Problem: The BMC Performace Analyzer for Servers pattern could retrieve more information on the product version. Solution: Code fix. Increased depth of product version discovery.|
|TKU-2324||Problem: The IBM InfoShpere Data Event Publisher pattern created Software Instances with incorrect type for IBM WebSphere Data Event Publisher version 9.59 and earlier. Solution: Code fix.|
|TKU-2345||Problem: The HP Data Protector pattern sometimes created a Software Instance with insufficient evidence. Solution: Code fix.|
|TKU-2411||Problem: The BMC FootPrints Service Core pattern created a Software Instance when a Tomcat was running on the same host with any BMC product. Solution: Code fix.|
|TKU-2266||Problem: The Adobe Livecycle pattern used vague conditions for relationship creation with a web application server. Solution: Code fix.|
|TKU-2351||Problem: The IBM DB2 Connect pattern was updated with improved file versioning and a new path versioning method. Solution: Code fix.|
|TKU-2392||Problem: The Oracle Connection Manager pattern retrieved incorrect product version. Solution: Code fix.|
|TKU-2393||Problem: The IBM FileNet Image Import pattern generated a non-informative key. Solution: Code fix.|
|TKU-2385||Problem: The Oracle Secure Enterprise Search pattern did not discover some Oracle Secure Enterprise Search versions. Solution: Code fix.|
|TKU-2329||Problem: The Oracle Enterprise Service Bus pattern reported incorrect version of the Oracle Enterprise Service Bus. Solution: Code fix.|
|TKU-2327||Problem: The IBM Records Manager pattern used non-valid Software Instance type for newer versions (IBM FileNet Records Manager for v5.1 and later). Solution: Code fix.|
|TKU-2366||Problem: The BMC BladeLogic Database Automation pattern was updated with improved method for PostgreSQL Database Server software instance identification. Solution: Code fix.|