Hi William I know it's of no help to you with ITSM7, but in ESS we have a separate application specifically designed to manage, compare and migrate configuration data between servers. The theory is exactly as you describe - you set up your config data on a Dev or QA server, test it there, and when approved simply click a button to move the data to other defined servers.
For this to work you have to design you application to not rely on a Request ID value for links between things like SLA/CTIs and tickets. We use an ID-GUID field for all these internal links. In an system like ESS (and ITSM7 I assume) where the configuration data affects system operation as much as workflow changes do, having a method to safely and reliably manage and migrate configuration data is essential. IMHO, without such a mechanism you've only got half an application. Regards David Sanders Remedy Solution Architect Enterprise Service Suite @ Work ========================== ARS List Award Winner 2005 Best 3rd party Remedy Application tel +44 1494 468980 mobile +44 7710 377761 email [EMAIL PROTECTED] web http://www.westoverconsulting.co.uk -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Thursday, June 05, 2008 7:26 PM To: [email protected] Subject: Re: Moving Task Templates, Support Groups, etc Unfortunately we're going from Dev > QA > TRN > PROD The theory is data will only be manipulated manually in the DEV environment and replicated across appropriately. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of T. Dee Sent: Thursday, June 05, 2008 1:17 PM To: [email protected] Subject: Re: Moving Task Templates, Support Groups, etc We had trouble with this as well. I export everything and imported onto the production server. I then had the users reselect the Assignment Info (group, etc.) so it would be the Assignment group info from production and not development. Or .... if you are lucky take a snap shot of production and restore it on development. Now both environments can be the same - should be easier to move things then. On 6/5/08, Pierson, Shawn <[EMAIL PROTECTED]> wrote: > ** > > > It's not a "good" strategy, but here's what we do. We only work on a > certain number of things before moving them into production. Once the > project is complete, we restore the backup of production to our other > servers, then start on whatever is next. > > > > > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow > Sent: Thursday, June 05, 2008 12:32 PM > To: [email protected] > Subject: Moving Task Templates, Support Groups, etc > > > > > ** > > > Just curious...this is with ITSM 7 and specifically IM 7.x > > > > > > We have 4 servers: Dev, QA, Training, and Prod. We frequently have to > move things that are ID-dependent from server to server and I wonder > how people are doing it. > > > > > > For example, assignment information for groups reference the group ID > which can quite easily be different when you move groups from server > to server - you have to take care of this when you do the move and > re-map things. Task templates (IM patch 9002) reference the parent ID > of the Task group template and are also prone to the same problem. > > > > > > Anyone come up with a good strategy for doing these moves? > > > > > William Rentfrow, Principal Consultant > > [EMAIL PROTECTED] > > C 701-306-6157 > > O 952-432-0227 > > > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ Private and confidential as detailed here. If you cannot > access hyperlink, please e-mail sender. > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ ________________________________________________________________________ _______ 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"

