INFORMATICA – DEPLOYMENT GUIDELINE DOCUMENT

July 27, 2009

Madhumitha Sekar

Table of Content

1. INTRODUCTION...................................................................................................3

2. ASSUMPTIONS......................................................................................................3

3. OBJECTS TO BE DEPLOYED..............................................................................3

4. SCRIPT CHANGES................................................................................................3

5. PARAMETER FILES.............................................................................................4

6. IMPORTING TABLES...........................................................................................5

7. MAPPING DEPLOYMENT...................................................................................6

8. SESSION DEPLOYMENT.....................................................................................7

9. WORKFLOW DEPLOYMENT..............................................................................7

10. CONCLUSION....................................................................................................8

2

1. INTRODUCTION

This document serves as a guideline for deploying the changes made into Informatica production environment. It specifies the steps that have to be carried out while moving ETL from development to production environment. This document can also be referred as checklist during deployment process.

2. ASSUMPTIONS

The production database is up and running.

All the new tables required for the deployment is available in the production database.

The necessary changes to the existing tables were done in the production database.

All the tables were given necessary privileges to be accessed by the ETL.

3. OBJECTS TO BE DEPLOYED

Scripts: The Scripts which are used for file handling and archiving are to be deployed.

Parameter file: If there any parameter files used, the necessary changes should be made for the production environment.

Mapping: The new mappings created and the existing mappings which are changed are to be deployed.

Session: The new sessions created and the existing sessions which are changed are to be deployed.

Workflow: The new workflows created are to be deployed.

4. SCRIPT CHANGES

1. Verify that all the UNIX scripts for file handling and archiving have been created for production environment.

2. Verify that the folders used in the script are available and have the necessary privileges.

3. Verify that the source and target connections of the script point to production servers.

4. Verify that the user name and password used for connecting any ftp servers are valid.

3

Sample Script file:

5. PARAMETER FILES

The following rules can to be applied while creating a parameter file in the production environment:

Capitalize folder and session names the same as they appear in the Workflow Manager. Folder and Session names are case sensitive in parameter file.

Define service process variables properly. Service process variables must begin with $PM.

List all necessary mapping parameters and variables. Mapping parameter and variable values become start values for parameters and variables used in a mapping.

Enter folder name for non-unique session names. When a session name exists more than once in a repository enter the folder name to indicate the location of the session.

Create a parameter file section for each session. To include parameter and variable information for more than one session in the parameter file, create a section for each session. The folder name is optional.

When defining parameter values, do not use unnecessary line breaks or spaces. The integration service might interpret additional spaces as part of a value.

4

List all session parameters. Session parameters do not have default values. An undefined session parameter fails a session.

Use correct date formats for date time values. Use any one of the following date time values:

o MM/DD/RRo MM/DD/RR HH24: MI: SSo MM/DD/YYYYo MM/DD/YYYY HH24: MI: SS

Do not include parameters or variables in quotes. The integration service interprets everything after the equal sign as part of the value.

Include mapplet name. Precede parameters and variables in mapplets with the mapplet name.

Sample parameter file:

6. IMPORTING TABLES

a. Import new or modified table in Source Definition:

If any new table has been created in the database, import the table in mapping designer to be used as source definition.

5

If the table in the database which is used as source definition in the mapping is modified, re-import the table in the mapping designer to reflect the changes.

b. Import new or modified table in Target Definition:

If any new table has been created in the database, import the table in mapping designer to be used as target definition.

If the table in the database which is used as target definition in the mapping is modified, re-import the table in the mapping designer to reflect the changes.

Note: Because views in a relational database can include columns from more than one table, the integration service might encounter database errors when trying to insert, update, or delete data. If a target view is imported, make sure that it is a view of a single table.

7. MAPPING DEPLOYMENT

The following steps should be followed while deploying the mappings in the production environment:

1. If the existing mapping in production environment is to be deployed, make sure backup of those mappings are taken.

2. Copy the newly developed mapping from the development repository to the production repository.

3. Copy the existing mapping which is changed in the development to the production repository. While copying, the user is prompted to either replace or rename the existing mapping. The user has to select replace option to reflect those changes.

4. Verify that all the mappings follow the standard naming format.

5. Provide the modification log in mapping comment area for the modified mappings.

6. Verify that the parameters and variables used in the mapping are the same as of those in the parameter file.

Parameters and variables wizard:

6

8. SESSION DEPLOYMENT

The following steps should be followed while deploying the sessions in the production environment:

1. If the existing session in production environment is to be deployed, make sure backup of those sessions are taken.

2. Copy the newly developed session from the development repository to the production repository.

3. For the session whose existing mapping changed for deployment, has to be refreshed to reflect the changes.

4. Verify that the session log file name matches the session name for the integration service to create session log files.

5. Verify that the session name in the parameter file is correct.

6. Verify that all the sessions follow the standard naming format. The session name should be of the following format: ‘s_mapping name’

7. Verify that all the session connections, source and target connections are correct and valid.

Sample copy wizard:

9. WORKFLOW DEPLOYMENT

The following steps should be followed while deploying the workflows in the production environment:

1. Verify that the workflow log file name matches the workflow name for the integration service to create workflow log files.

2. Verify that the worklets and workflows have appropriate description in the comment section.

3. Verify that the sessions and worklets used in the workflow have the necessary condition in the links.

7

Link condition:

10. CONCLUSION

Thus this document serves as a guideline and as a checklist to the Informatica team for deploying the changes into the production environment. Following the above steps ensures successfully deployment of ETL from development to production environment.

8