Informatica Migration Check List

By

Anvaya Akhouri Wipro Technologies

September 2005

MIGRATION CHECKLIST
Note: Migration is a critical process that directly impacts production.
Workflow Names: Mapping Names: Migrated by : Reviewed by : No of Migration errors : No of Review errors : New Errors (to be included in the checklist ) : Sl. Checklist Item Yes/No/NA Actions To Be Taken/ No. Remarks Analyze differences between Test and Production. List down any issues or missing information and clarify with the development team before migration. Are the number of sessions and other tasks in the 1. two environments equal and in the same order? Does anyone have a lock on the sources? 2. Cause : Cause : Migration Date: Review Date:

3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.

Are the mappings and workflows valid? Are the naming standards being followed? Are the best practices being followed? Are the database connections the same? Do you have adequate information on what the new DB Connections should be? Are the pre and post session command tasks the same? Has the scheduling information been specified the first run, the frequency, the time? Are there any shortcuts for sources, targets or mapplets? Are the differences mentioned in the migration form there in the mappings or workflows? Is there any discrepancy between what is listed in the migration form and what you can see in the Informatica client? Are you required to make any changes for scp to DW or ftp to mainframes, etc and in which task? Are the command tasks/ the scripts being called by them using environmental variables? Are there any scripts, sources or parameter files that need to be copied to production?

INTERNALLY RESTRICTED

Page 2 of 4

MIGRATION CHECKLIST
Sl. No. Checklist Item Do operations need to be paged if the workflow fails? Is there any reason not to suspend the workflow in case of failure? Are there any other special instructions? Yes/No/NA Actions To Be Taken/ Remarks

16. 17. 18.

Migrate from Test to Production. Please make sure that you do not make any unwanted changes e.g. spelling mistakes, specifying incorrect script path, moving untested scripts, forgetting to change the test mail recipient back to the production one, forgetting to delete command tasks when all underlying commands have been removed, etc. 19. Have the list of objects to be migrated is verified using Migration Request form? (Sources, Targets, Transformations (reusable), mapplets, mappings, sessions (reusable) and workflows in order) 20. Have you created a new folder for that project with the admin of the group as owner and given the proper privileges on the folder? 21. Have the shortcuts for sources, targets or mapplets, not already present in the shared folders been moved? 22. Have you created any new database connection that may need to be created? 23. Have you given appropriate permissions on the new database connection? 24. For a SQL Server DBConnection, has the appropriate information been added in the .odbc.ini file? 25. If mapplets are involved, have you used importexport for migration? 26. In case the change is only in the mapping logic, did you refrain from moving the workflow? (You just need to migrate the mapping and validate the workflow ) 27. In case you need to create a new task (esp. session) in a workflow, have you made sure that all the details e.g. the sources, targets, database connections etc are given correctly? 28. If it is an existing workflow with changes in both mappings and workflows, have you moved the changed mappings first, and then the workflow? 29. Have you changed the database connections?

30.

Have you added any pre/post session command tasks e.g. for scp to DW or ftp to mainframes that may need to be added? Have you changed any command tasks to call the scripts? (Make sure you edit the path of the script to point to the correct path. Do not edit the name of the script.)

31.

INTERNALLY RESTRICTED

Page 3 of 4

MIGRATION CHECKLIST
Sl. No. Checklist Item Have you changed the scripts on server being called to use the Informatica Server directory variables? Does the script have header information? Are the comments in the scripts descriptive and up to date? Have you checked the Run if previous completed check box in all command tasks? Have you modified the workflow to suspend on error (unless stated otherwise) ? Have you modified the workflow to page to operations if requested in the migration form? Have you modified each session to send failure email to operations in case of session failure? In case you need to send email to more than one user, have you separated the email ids by a comma? ( ; does not work in this case ) Have you taken care of any special instructions listed in the migration form? Have you checked in your changes, closed the mappings and workflows and logged off? Have you moved any parameter files that need to be moved? Have you moved any sources that need to be moved? Have you given the required permissions on any new Unix folders you have created or any sources, parameter files or scripts you have moved? Are the session properties same as the developed and tested version? In case a common object has changed, have you validated all the affected workflows, even though this might not have been requested in the migration form? Yes/No/NA Actions To Be Taken/ Remarks

32. 33. 34. 35. 36. 37. 38. 39. 40. 41. 42. 43. 44. 45. 46.

INTERNALLY RESTRICTED

Page 4 of 4