I would like to go one step further than just checking for object counts and log files. It would be really nice and helpful to have a definitions file of the vanilla module, or combination of modules, and being able to do an object comparison, for instance with the Migrator tool, or some other similar tool than can compare workflow. This is exactly what I did to "certify" a CMDB upgrade from 1.0 to 1.1 patch 2, I believe, last year during a project: I had requested support the definitions files for a vanilla CMDB at the latest patched version at that time and support was very kind and helpful and provided me with the definitions file, and I used Migrator to compare the actual CMDB workflow. I did find a couple of filter actions that did not match exactly, even though the log files did not show any errors, neither the HTML file. Of course I could have installed a vanilla CMDB in another environment, and do the comparison there, but it was just easier and more formal to get the definitions from support to be able to prove to management that the CMDB upgrade was successful (after fixing the couple of filters that did not match). So to summarize, it would be really helpful if, specially for upgrades, there was an automagic method to compare the code (workflow) to make sure everything that should be there is there. Maybe a stripped down version of the migrator could be used for such purpose and be part of the install/upgrade process...
Guillaume From: Joe D'Souza Sent: Tue 04/10/07 10:54 AM To: [email protected] Subject: Re: ARS 7.0.1, CMDB 2.0.1 and version 7 apps... That's what I do too and I do take a look at the Share application properties form too to make sure that all the entries that are supposed to be there specific to that application and patch you are installing have been created or modified.. Another test I do is if there is more than one server that we are installing on (e.g. Dev, QA, Prod), then I make sure that I choose similar installation options so that the object count would remain the same for all instances.. Sometimes this though is not a good way of looking at it as more often than not many sites do have server groups for QA and Prod but none for Dev, or the same might stand good for other such options that might lead to creation of a couple of more forms or a few more AL's or Filters.. But in case you have an environment where you get the luxury of installing as identical instances, the total counts of objects like Forms, AL's, Filters etc and comparing them does help.. Joe _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
