Matt, It sounds like the functionality I am looking for is not there. I was hoping for some kind of middle ground between manually adding every CI into BMC ASSET then reconciling to get the attributes synced up (very slow), or auto-identifying all CIs in the discovery dataset and firehosing them all into BMC ASSET (very fast, but difficult to validate).
If you were only forced to manually populate Computer System CIs into BMC ASSET, and the discovery dataset child CIs could auto-identify once their computer system parent was identified, it would be a very good compromise. On this same topic, computer system child CIs should also have the option of inheriting ownership/support data/relationships and asset lifecycle data/relationships from their parent computer system CIs. A lot of work needs to be done here to enhance the maintainability of large CI count production datasets. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Matt Worsdell Sent: Wednesday, October 29, 2008 3:15 PM To: [email protected] Subject: Re: Merging of non-reconciled child CIs Tim If the "child CIs" have not been given an RE id then they won't merge. You could run a separate merge activity with auto discover on, or alternatively a copy job and specify the classes for inclusion. Matt -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Tim O'Connor Sent: 29 October 2008 20:07 To: [email protected] Subject: Merging of non-reconciled child CIs I'm looking for a method whereby I can enforce a slow and methodical inclusion of hosts into BMC ASSET from discovery tool datasets. By not auto-identifying BMC_ComputerSystem instances in the discovery tool dataset, I can prevent them from being merged into BMC ASSET unless a BMC_ComputerSystem instance already exists in BMC ASSET and can be matched via the identification group rules. However, for child CIs (harddrives, installed software, etc) I'd like to not have this same constraint. I want them to automatically merge with their parent BMC_ComputerSystem instance once that instance has been reconciled to a BMC ASSET computer system instance. It seems to me that when creating a merge activity, the "include child CI's?" option should facilitate this type of functionality. However, even when I set this option to "yes" Atrium refuses to merge Computer System child CIs with their associated parent instance. Can anyone shed some light on how best to achieve this sort of functionality (if its even possible)? I don't want to have to hand create each computer system child CI in BMC ASSET before their associated CIs in the discovery dataset can be merged, but I also don't want to firehose all the child CIs into BMC ASSET either, which is what happens when I auto-identify them. Tim O'Connor Staff Consultant Cell 925 324 6958 EMC² ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
