For production environments with heavy usage of Time Management, such as more than 300 users logging or approving time in a peak hour, we recommend running the script at a time other than peak usage.
When the data in all the
.xmlfiles is ready to use for time sheet creation on the production instance, do the following:
Copy all of the
.xmlfiles for time sheets to the desired directory on the production instance. Be sure to use any
.xmlfiles to which you made corrections while testing on the TEST instance.
Run the script on your production instance without using test mode, to create time sheets in PPM. Use the number of threads (
-maxThreadcountargument) indicated by your performance testing on the TEST instance. See Running the Time Sheet Data Importer Script.
While the script is running, monitor the following:
Usage of system resources (CPU, memory, disk space)
Table space available in the database
Redo archive log growth in the database
When the script completes, review and correct all errors as in step 4 in Task 1 and step 5 in Task 1, and rerun the script until it moves all of the
.xmlfiles to the
SUCCESSsubdirectory and creates corresponding time sheets.
kTMPMSync.shscript with the
-includeDatesargument set to
yes.For information about the
kTMPMSync.shscript, see the Project Management Configuration Guide.