Is that process directly push the data to BMC.ASSET? If you can explain about that process will help.
It is not recommended to bypass RE, but yes there is an option to skip specific class in Merge activity by providing qualification.
Go to merge activity, there is section shown as below, by default the checkbox is checked. Uncheck and create new qualification set by adding rule for specific classes, such that the qualification never met, so that those CIs are not going to merge. Not even any single attributes.
I think this can be handled by recon engine. If this is for ADDM- ASSET sync, you need to check identification and merge activity rules and update if required so that whenever CI gets created in ADDM dataset for monitor class, Recon engine will set existing reconid to that record instead of creating new one in Asset.
@Ganesh, since we don't know much about the process of pushing monitor CIs to BMC.ASSET, there may not even Recon IDs generated, in that case it will lead to data integrity issues.
We upload our monitors from a spreadsheet into BMC.Asset for asset tracking. Our discovery finds monitors that are not company assets even though they are attached to a company computer and we don’t want these to go into BMC.Asset, there are not a lot of these but over time it will create an audit issue.
If the CI reconciles based on serial number to an existing monitor in BMC.Asset we want it to update the record with a scan date and create a relationship to the computer it’s attached to. If it doesn’t find a match we want it to stop there and do nothing, don’t create a new CI in Asset because it’s not a company asset.
Directly updating to BMC.ASSET is not recommended. Should import to some staging data set(say STAGING), then reconcile to BMC.ASSET.
Ensure all the mandatory attributes are populated for monitor CIs as per the reconciliation identification rules.
Then when discovery discovers the same monitors, identification rules should match existing monitors, so that duplicate monitors are not created.
In order to update only require attributes from ADDM, merge precedence can be set to higher (> 100) for these attributes of ADDM data set.
I don’t think we’re directly updating BMC.Asset, we’re using Discovery, it goes into ADDM and runs through Recon. If it finds a match it reconciles and updates the CI in Asset, if it doesn’t it creates a new CI, we just don’t want it to create that new CI, how can we prevent that from happening?
1 of 1 people found this helpful
I expect you are using the standard identification rules.
The way to prevent it creating a new CI is to stop it from having a reconciliation ID generated during the identification activity, and for that you need to uncheck using the standard rules, and create custom rules. With custom rules you can uncheck the box for generate ID.
It's a little time consuming to basically recreate the rules but may give you the opportunity to make other changes which may suit your individual circumstances as you go
Then instead of moving monitor CIs into ADDM, move them to different data set, then reconcile to ASSET.
When discover discovers monitors and sync to ADDM dataset, then reconcile this with ASSET, so that matching monitors get updated with mentioned attributes as per the merge precedence.