This is something I have done many many times - and others have also done with only one hour learning and samples. I also offer fixed-price migrations of this nature using the power of Meta-Update and the confidence that such power and ease brings. Check out Meta-Update and email me for more information. There is a small bug in the creation of a company that assigns it always a new group id. Meta-Update scripts can get around this and preserve or change all fields and data as needed. Remember that with Meta-Update there are NO filters, NO staging forms, NO server touches at all. Meta-Update scripts can run on the server or on a Windows client. www.softwaretoolhouse.com Cheers Ben Chernys
Senior Software Architect Software Tool House Inc. Canada / Deutschland / Germany Mobile: +49 171 380 2329 GMT + 1 + [ DST ] Email: <mailto:[email protected]> mailto:[email protected] Web: <http://www.softwaretoolhouse.com/> http://www.softwaretoolhouse.com An ARS API scripting tool used for migrations, integrations, imports, reports, extracts, batch jobs: http://www.softwaretoolhouse.com/ _____ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of strauss Sent: February 24, 2010 7:18 AM To: [email protected] Subject: Re: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** It is not so much the Entry IDs as it is the other IDs that are then embedded in Incident records and other ticketing forms as they are created and processed through a normal life cycle. Excerpting some communication I had with someone off list today. We know that we MUST preserve the Group Name / Group ID / Long Group Name for all of our custom company structures (Customer Companies, Operational Companies, and Support Groups) because those are stored in field 112 all over the place. In an Incident, Group IDs are stored in Assignee Groups (112) and Vendor Assignee Groups (60900); the Group form IDs have to match those in all of the tickets that we are going to import. SGP group ids are stored in Assigned Group ID and Owner Group ID, and these much match too, so I need to import my 7.0 support groups even where it overwrites something BMC installed (like SGP000000000009, 10, and 11 which are Calbro Services in a clean install without sample data...oops!); we have already used those values for live data on our 7.0 system. STE IDs are stored in Site ID in Incidents, so those values will have to be preserved in the imported data as well. Our existing data starts at STE000000000003, so importing it with data management doesn't work - the IDs are different afterwards. Again, a base install of ITSM 7.6 with no sample data (but with Product Catalog data with AtriumCore 7.6) results in existing Site records that ours will have to overwrite (from STE000000000001 to STE000000003211). I will have to try a complete new fresh install from ARS on if I want a build where I don't import the Product Catalog data until after we get our existing foundation data loaded. What we still don't know (and cannot tell without difficulty), is if some of the fields that provide associations between foundation data records, either in association tables or the base tables, are using Entry IDs or GUIDs as the connecting value; that complicates the import by misaligning all of the relationships. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Guillaume Rheault Sent: Tuesday, February 23, 2010 7:02 PM To: [email protected] Subject: Re: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** Looks like you need to submit new requirements to the BMC product manager :-) As far as the order is concerned, the order to follow is the same order as layed out in the Data Management tool "Data Load Console", which is the Sequence column on the table field. If you follow this order you should be fine. Each "load" form has filters that push to the end-form. I can only sympathize with your requirement of keeping the Entry IDs the same.... that's some requirement! Don't rule out using SQL scripts for your data migration.... Guillaume _____ From: Action Request System discussion list(ARSList) [[email protected]] on behalf of strauss [[email protected]] Sent: Tuesday, February 23, 2010 3:36 PM To: [email protected] Subject: Re: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** You haven't spotted any entity relationship diagrams out there for the data tables in ITSM 7.6, have you??? Don and I are trying to figure out all of the tables (in order) that he will have to move data for - from our production ARS 7.1.00.002 / ITSM 7.0.03.009 system to the new ARS 7.5.00.004 / ITSM 7.6 system - using rrrchive, import, Migrator, carrier pigeon; whatever. Anything that ties to other tables on record ID, like everything that uses Group IDs (including Incidents, etc.) has to come over exactly as it is on the 7.1/7.0 system or those relationships will not be maintained; you cannot use the Data Management tool or the load tables since they generate a completely new set of record ids. Our concern is that we don't know about all of the underlying association tables that store those relationships, and were hoping that there are ERDs out there that document them. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Guillaume Rheault Sent: Tuesday, February 23, 2010 10:23 AM To: [email protected] Subject: Re: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** Hi Don, I only use the spreadsheets in the ITSM Data Management tool for reference. What I do is actually import the data in the "load" forms with the import tool. To figure out what are the "load" forms, in DevStudio, list the forms whose name contains "load". I got 110 "load' forms in ITSM 7.5.1. For instance, the load form for CTM:People is CTM:LoadPeople Guillaume _____ From: Action Request System discussion list(ARSList) [[email protected]] on behalf of McClure, Don [[email protected]] Sent: Thursday, January 28, 2010 4:07 PM To: [email protected] Subject: ITSM7.5 Data Management Tool--Specifically, Load Wizard ** I encountered the following situations utilizing the ITSM7.5 Data Management Utility. For those who have not yet encountered this 'wonderful' inventory item: First, installation: initial Windows 7 installation with default locations resulted in structure being under c:\Program Files(x86) on this Win7/x64 platform. Unfortunately, said structure is read-only, and did not respond to administrative change to write-eligible. Installation into c:\Users to access user space still encountered issues with writing CVS files from Excel macros, as Windows 7 security is very finicky concerning allowing macros to execute at all, let alone write files. Environment was re-installed on an XP machine, where these characteristics are no longer a hindrance. Second, filenames: this installer named the Macro files under the various sub-versions as: (workbook)CSV without a three-letter extension. System will not recognize them as Excel files at all without renaming them to : (workbook)CSV.xls (and, yes, the *CSV capitalized is hard-coded into batch files to find them for execution). Third, location sensitivity: please remember that the installation directory is hard-coded into worksheets by the installer at install time, so moving this structure (or copying from one platform to another...) requires significant attention and name-modification. Fourth, running the data import from User 7.5 : The 'convert CSV' and 'import CSV' functions each call a popup which prompts user to search for: location of DataImport.exe, location of Excel.exe, and installation directory for the overall data management structure. Yes, these will be searched the first time, as defaults noted by the Windows client are probably incorrect. CAUTION: these two popups expect DIRECTORIES--but the actual Windows search which is invoked will not allow a person to stop on a directory, requiring a standard file. Therefore, the easiest way was to selected a file WITHIN each desired directory. Then the user simply erases the filename (ONLY!) from its data window, leaving the first-level parent directory which is what the two functions require for their respective windows! Oh yes--this Data Management tool must be executed from the User Tool. Seems like a really appropriate place for the BMC development team to implement MidTier capability, right? After all, the statement of direction is that the Windows Client is headed for oblivion. I am interested in other user experiences on this item--either directly or to the list! Don W. McClure, P.E. Applications Administrator,CITC Call Tracking Administration University of North Texas dwmac @ unt . edu _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_ _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"
