Super Contributor.. Super Contributor..
Super Contributor..

Understanding Identification Rules


What is the purpose of the attribute "conditiontype" in the identification rules?.

We have problems with node reconciliations rules (UCMDB merges input CI with already UCMDB CI) and we have discovered that the problem is the next attribute-condition, which is part of one of the validation-criterion:

<attribute-condition attributeName="ip_address_property" includeNullValue="false" conditionType="contradictionOnly" matchNameOnly="false">

The node in the UCMDB contains an empty value in the ip_address_property
The input node contains an empty value in the ip_address_property

With the previous attribute in ConditionType="contradictionOnly" the UCMDB merges the input node and the UCMDB node (which is not what we want)
With the previous attribute in ConditionType="approveAndContradict" the UCMDB creates a new node in UCMDB (is that we want to do)

The problem is that we have computers with dual partitions and we want that UCMDB discover them as different CI's.
The identification rules merges the nodes and the result is that we have a node which contains the software that are in the two partitions.

Is there any solution or other way to remediate this?


The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.