BMC Atrium Discovery Technology Knowledge Update 2014-Sep-1 is a deliverable for BMC Atrium Discovery 8.3, 9.0 and 10.0 series.
The September 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. 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-Sep-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-09-1.xls
|Teradata||Aster Database||Relational Database Management Systems||UNIX||Y||N|
|Oracle||Communications Data Model||Relational Database Management Systems||UNIX||Y||Y|
|Oracle||Real Application Testing||Database Development and Management Tools||UNIX||Y||Y|
|Puppet Labs||Puppet||Change and Configuration Management Software||UNIX, Windows||Y||Y|
|Oracle||Airlines Data Model||Relational Database Management Systems||UNIX||Y||Y|
|Oracle||Retail Data Model||Relational Database Management Systems||UNIX||Y||Y|
|Teradata||Viewpoint Portal||Advanced Analytics Software||UNIX||Y||Y|
|Open Source||Jenkins||Development Languages, Environments and Tools||UNIX, Windows||Y||Y|
|Sailpoint||IdentityIQ||Identity and Access Management||UNIX, Windows||Y||Y|
|Apache||ActiveMQ||Application Server Software Platforms||UNIX, Windows||Y||Y|
|Microsoft||DHCP server||Data Integration and Access Software||Windows||Y||Y|
|RFE ref.||Product Page||Enhancement||SI Key Change|
|QM001853407||-||Minor improvements to J2EEInferredModel pattern.||N|
|Esc 062769||The pattern has been improved to better identify related UNIX virtual machines and the Microsoft Hyper-V server.||N|
|QM001856957 (Esc 062310)||The pattern now supports Microsoft Internet Information Services version 7.0, 7.5, 8.0, and 8.5.||N|
|QM001857051 (Esc 062153)|
J2EEInferredModel and RDBMS_Functions patterns were updated in perspective of Oracle WebLogic Server deep discovery.
|Improved identification of databases hosted on the Oracle WebLogic Server.||N|
|QM001789877||Added extended discovery of the Oracle Application Server.||N|
|Idea 1574||Discovery of Microsoft SQL Server 2000 Edition has been improved. The pattern now allows using an alternative database query versioning method.||N|
|QM001857358||Cluster modeling has been improved in the Oracle Clusterware pattern. The cluster key has been enhanced.||Y|
Microsoft Windows PowerShell (BETA)
|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|
|QM001858520||The path versioning has been improved in the Oracle WebLogic Server pattern.||N|
|TKU-2355, TKU-2353||The Apache Tomcat pattern has been updated with new attributes (listening_ports and short_name).||N|
|QM001857216||The Microsoft SQL Server pattern now discovers more versions of the Microsoft SQL Server (version table updated).||N|
The following defects have been fixed in BMC Atrium Discovery Technology Knowledge Update 2014-Sep-1
|Defect No||Details||Product Page|
|TKU-2361||Problem: For IBM Tivoli Netcool/OMNIbus Software Instance, the link to the documentation does not work. Solution: Code fix.|
|TKU-2310||Problem: The pattern did not recognize a new product name introduced in version 5.5 and higher (Embarcadero DB Change Manager). Solution: Code fix.|
|TKU-2312||Problem: The pattern did not support Embarcadero Performance Center version 2.7.3. Solution: Code fix.|
|TKU-2311, TKU-2309||Problem: The Embarcadero DBArtisan pattern reported incorrectly a product version for Embarcadero DBArtisan version 8.7 and later. Solution: Code fix.|
|TKU-2309||Problem: The Embarcadero DBArtisan pattern reported incorrectly a product version for Embarcadero DBArtisan version 8.7 and later. Solution: Code fix.|
|TKU-2328||Problem: The pattern creates SoftwareInstances with incorrect type. Solution: Code fix.|
|TKU-2213||Problem: The pattern reported incorrectly a product version for IBM WebSphere Enterprise Service Bus major versions. Solution: Code fix.|
|TKU-2373, Esc062112||Problem: The Microsoft Windows PowerShell pattern creates SoftwareInstance instead of RuntimeEnvironment node. Solution: Code fix. Note: The RuntimeEnvironment is created even when the Microsoft Windows PowerShell is not running during scan.|
|TKU-2333||Problem: The BMC Patrol Agent pattern does not set instance for Patrol KM SoftwareComponents. Solution: Code fix.|
|TKU-2356||Problem: IBM Rational Asset Analyzer pattern fails to correctly expand install_root. Solution: Code fix.|
|TKU-2357||Problem: The pattern failed to correctly parse license detail nodes (TKU-2357). Solution: Code fix.|
|TKU-2341||Problem: BMC Batch Impact Manager searches a file that contains version in the wrong location. Solution: Code fix.|
|QM001857184||Problem: The Oracle Traffic Director pattern does not trigger in some circumstances. Solution: Code fix.|
|QM001857233 (Esc 062654)||Problem: File versioning could fail on UNIX, if the log file was in an alternative location. The Sybase Adaptive Server Enterprise pattern could fail retrieving a version from a log file, if the file was not available in the default location. Solution: Code fix. Alternative method of log information retrieval added.|
|TKU-2315||Problem: The IBM Cognos PowerPlay pattern did not support the new product name introduced in version 8.4 (IBM Cognos Business Intelligence PowerPlay). Solution: Code fix.|
|TKU-2349||Problem: The IBM DB2 RDBMS pattern does not parse license file correctly. Solution: Code fix.|
|TKU-2303||Problem: The Autonomy IDOL pattern did not support the new product name introduced in version 10.0 (HP Autonomy IDOL). New versions are now supported (10.3 and 10.5) Solution: Code fix.|
|TKU-2362||Problem: IBM Tivoli Netcool/Webtop pattern extracts build from version incorrectly. Solution: Code fix.|
|TKU-2358||Problem: IBM Tivoli CAM for SOA Platforms fails to create Communication relationship with IBM Tivoli Enterprise Monitoring Server on Windows. Solution: Code fix.|
|TKU-2131||Problem: The IBM Alphablox pattern fails to correctly identify cell name on WebSphere Application Server. Solution: Code fix.|
|TKU-2314||Problem: HP Openview Performance Insight has incorrect si_type (HP OVPI instead of the HP OpenView Performance Insight). Solution: Code fix.|
|TKU-2115||Problem: BMC Impact Manager package versioning was corrected. Solution: Code fix.|
|QM001856706 (Esc 062306/062249)||Problem: TIBCO Rendezvous ECA Error Solution: Code fix.|