To get the benefit of the trusted dataset you'd need to map the tier 1-3 values to constants in your data exchange.
This is what, for example, BMC Configuration Discovery does (all computer systems are Hardware, Processing Unit, Server). You may be able to add all possible computer systems, with appropriate tiering, to the product catalog. The product name/manufacturer combination should then fetch the correct tiering for each computer created. When a new type of computer is discovered the trusted dataset will allow a new product catalog entry to be created automatically and the computer will be saved without error. You could then monitor the product catalog for new entries with the default tiering and deal with these by changing the tier values and updating the computer CIs. Discovery returns only what it finds so you may need to take care of multiple different ways of referring to the same manufacturer (eg MS, Microsoft, Microsoft Inc, etc) and multiple ways of referring to the same computer model. The CMDB normalisation engine uses product and manufacturer aliases to deal with this. The addition of a few filters in CMDB 2.1 would allow you to do the same using the existing manufacture and product alias forms. Cheers Peter _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of John Kelley Sent: 07 January 2010 19:58 To: [email protected] Subject: Re: EIE Exchange field mapping CMDB2.1 I added that Trusted Dataset and now when I exchange, it comes over to the BMC.CORE:BMC_ComputerSystem form with NULL values. Now I will try Peters Suggestion. I'll let you know. JK Thomas Worth <[email protected]> Sent by: "Action Request System discussion list(ARSList)" <[email protected]> 01/07/2010 01:01 PM Please respond to [email protected] To [email protected] cc Subject Re: EIE Exchange field mapping Also, if it's CMDB 2.1 or earlier, you can make the dataset you're importing to a Trusted Dataset. This will automatically build the Product Catalog entries if it doesn't find an existing catalog record. To do this, just create a record in the Trusted Dataset form, adding your dataset. Thomas Worth IT Prophets, LLC -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Peter Romain Sent: Thursday, January 07, 2010 12:57 PM To: [email protected] Subject: Re: EIE Exchange field mapping It would help to know the versions you have installed. Turn on filter logging and try and create an entry manually in the BMC.CORE:BMC_ComputerSystem form using some sample data you are getting from SMS. The logs will reveal where the problem is. I suspect that the model/manufacturer is being looked up in the PCT:ProductCatalog form and, because no value(s) exist for the computers coming from SMS, the tiering is being left null. This assumes you are on CMDB 2.1 or earlier. CMDB 7.5 uses the normalisation engine which you can configure to continue even if the categorisation isn't found. You must also be mapping the dataset value otherwise the import will fail. Cheers Peter > Hi list > Need a little help > I am trying to run a single data exchange for computer system from SMS to > CMDB and I have errors during the exchange. "The Product Categorization > Tiers, Product Name and Manufacturer combination is not valid." > The fields I have mapped are the Domain, System Type, Manufacturer, > Model, Name, NumberofProcessors, Owner Name and AssetLifeCyclestatus. I'm > wandering if it does a reverse lookup on the model and then tries to > populate their own tiers. > > Does anyone know how I can fix this data mapping? What I want is to bring > in the Model of the system and do a reverse lookup and have it populate > the correct tiers for that model (to BMC.Core:BMC_ComputerSystem) once I > get it there I can then bring it into the Asset. > Has anyone done this? > What is the best way to populate the tiers? > > > JK > > > ************************************************************* > This e-mail message, including any attachments, is for the sole use of the > addressee(s) to whom it has been sent, and may contain information that is > confidential or legally protected. If you are not the intended recipient > or have received this message in error, you are not authorized to copy, > distribute, or otherwise use this message or its attachments. Please > notify the sender immediately by return e-mail and permanently delete this > message and any attachments. Dunkin' Brands Inc. makes no warranty that > this e-mail is error or virus free. > ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" ____________________________________________________________________________ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are" ************************************************************* This e-mail message, including any attachments, is for the sole use of the addressee(s) to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Dunkin' Brands Inc. makes no warranty that this e-mail is error or virus free. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
