The September 2014 TKU includes changes to the CMDB Sync mapping (introduced between TKU Mar 2014 and TKU Jul 2014)

• When you synchronize with the CMDB the first time, the BMC_ComputerSystem CIs mapped from partition Host nodes are updated and their PartitionIds are set.
• When you synchronize with the CMDB the first time, the BMC_ComputerSystem CIs 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.