actually, the recon process does not create relationships that are not already there (in the source data set). The merge step identifies and copies these relationships into ASSET if the prerequisites are met.
- both sides of the relationship must be identified and "ready to merge" or "merged"
- neither side may be mark as deleted
- the merge rule must not exclude relationships.
Can you check if the patches have arrived in the asset dataset? I don't think so.
If not, this can be the cause. Maybe they're not normalized. I remember such a problem in one of my environments
Hi Stefan, Thank you for your suggest.
How can I check this: the merger rule must not exclude relationships?
Identify and merge steps know qualification sets to restrict the elements to be edited. You can find this option at the bottom left of the steps.
Do the three patches have a reconID or is this 0 (Zero)?
If it is still 0, your identification is not correct for patch and therefore you don't see any related patches in the ASSET. BTW t522tst is a product?
Patch has a reconID, it is not a zero(everthing is correct).
I got answer for support: When you manually create a CI this is not the case; there is no information about the related CI as this point so there is no ability to auto create the relationship.
Do you have one example in you environment when you created manually CI via Asset console who has the same name and token ID with CI who created from ADDM side. After recon job finished you will have two CI in diferent dataset with same recon ID and all relationship on both CIs?
Remote diagnosis is not so easy, Recon is a bit too complex.
I think you should increase the log level and set the file here. Usually the error messages are quite good and clear. Maybe with a few devices, products and patches. A screenshot of your reconjobs and the merge activity could also be helpful.
I'm sure that's not the truth. We have many manual CIs, which are enriched with ADDM via the merge function, including relationships.
Btw, which version do you use
Can you create a recon job just for single CI and its relations and see if you are able to merge the CI to different dataset including its relations?
Is this a mandate that related CIs must be identified/merged in the same activity? If I have 2 CIs related to each other on source side, and if they are identified and merged in 2 different Recon Jobs, will they not get related in Asset?
1 of 1 people found this helpful
You can merge CIs, you can merge relationships, or you can merge both.
Normally, both is the assumption. If you merge only CIs, relationships will not show up. If you merge relationships, they will only be created if both endpoints exist in the target.
So if you only merged the ComputerSystem CI, but you did not merge the child CIs, the relationship cannot be created.