Strategy for Testing and Importing the Data

This section discusses running the script to test the .xml data and to create time sheets from the .xml files. In summary, the recommended strategy is to perform the following sequence of tasks:

• Using a few .xml files, run the script in test mode on a TEST instance, which validates the source .xml files but does not create time sheets, and correct any resulting errors

• Using the same .xml files, run the script and create time sheets on the TEST instance, and correct any resulting errors

• Configure all the .xml files that will later be imported as time sheets on the production instance

• Using an appropriate subset of those .xml files, run the script and create time sheets on the TEST instance to evaluate the CPU resource demand of the script and to determine an optimal number of threads for the script to use

• Using a few .xml files, run the script in test mode on the production instance to verify correct operation

• Using all the .xml files, run the script and create time sheets on the production instance, and correct any resulting errors