Hi,
Thanks for your suggestions. For initial load of the data, I accept it would be possible to use the AST forms and forget about normalization and reconciliation of the data before it hits the golden dataset and load everything straight to it. However, ongoing maintenance through regular updates of data to a staging dataset is not an option for asset attributes. My main concern, and I perhaps did not make it clear enough in my original post, is that asset attributes can no longer “enjoy” the functionality available in Atrium CMDB. These attributes can no longer be used in the reconciliation engine, their values cannot be compared between datasets and difference reports available in reconciliation engine cannot be generated to highlight any potentially un-authorized changes. It seems nobody raised this as a concern so far, so I am perhaps taking wrong approach to this. Hope somebody can share their experience with how they go about regular CMDB data updates that include asset attributes in Atrium v 8.x Thanks and regards Jiri Pospisil From: jortega999 . [mailto:jortega9...@gmail.com] Sent: 05 November 2015 17:07 Subject: Re: Loading of Asset Lifecycle Status and other Asset attributes to CMDB in version 8.x ** Try using the ast:computersystem form, which will feed the bmc_computersystem and ast:attributes. This worked for me. On Nov 2, 2015 11:43 AM, "Jarl Grøneng" <jarl.gron...@gmail.com <mailto:jarl.gron...@gmail.com> > wrote: ** Hi You should load your attributes using the form AST:LoadAttributes, using the AROutput step. Regards, Jarl 2015-11-02 12:47 GMT+01:00 Pospi ARSList <pospi.arsl...@gmail.com <mailto:pospi.arsl...@gmail.com> >: ** Hi all, Hope somebody can shed some light on this. As of version 8.x, all asset attributes such as Asset Lifecycle Status have been removed from the core CMDB data model and are stored in its own asset form called AST:Attributes. I am trying to define a data load job to CMDB using Atrium Integrator transformation that would also include Asset Lifecycle Status. In Atrium Integrator Spoon, if I select CMDB Output step as the means of writing the data to CMDB class, the Asset attributes are missing. I could add them by a separate push to AST:Attributes using AROutput step, but the link is based on reconciliation ID, which I do not have at the time when importing the data to the CI class as that would be only available once the data has been through the identification phase of reconciliation. In addition, the link to AST:Attributes is only based on reconciliation ID and does not include the dataset, so there can only be one entry per CI, meaning that any changes to asset attributes would be made to the live data straight away without going through the reconciliation process. Is this a shortcoming of the design implemented for asset attributes since version 8 of CMDB or is there a different way this is intended to work? Any advice, opinions, suggestions would be greatly appreciated. Thanks and regards Jiri Pospisil _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
