Code Deployment in Informatica

Migrate/Deploy Code in Informatica

1. Using Deployment Groups: Creating deployment group in repository manager including all objects into other environment suppose development environment to QA environment this is implemented where version control is used so that later if we want to roll by code to old code, should be able to roll back to previous version.

Below are steps to create deployment groups

In power center repository manager under Tool>deployment> Group click on new provide name select based on your requirement static/dynamic and provide permission on this then start copying objects into newly created deployment group after copying all objects.

A. static deployment group: we manually add objects to static deployment group, dependent objects can be configured automatically, ex- if one mapplet used in various mappings it will automatically added to deployment group

B. dynamic deployment group: we can configure deployment group with query to enable informatica to add object in dynamic type deployment group, we can build query during dynamic deployment group creation.

We can start deploying groups to new environment or QA Environment.

2. Import and export as XML: Here all objects can be exported as XML to destination directory then later on we can import those object in destination environment.

3. Copy/Paste: copy all objects and paste to destination repository using power center repository manager make sure that first copy source and target definition and then mapping, session and workflow sequential order.

Important points during code migration:

Source and target definition not available in Deployed environment: While copying mapping if those source and target definition not available in target environment then mapping get copied with previous source and target shortcuts, we have to make sure before migrating mapping we have to create source and target definition first.

Impacts post migration: Before migration it is necessary to check all source/target that getting updated, those changes might cause other mappings to fail.

Connection setup missed: As database changes in QA and pro in this case your mapping will fail in production

So in this case after migration we have to make sure we have proper database connection with permission.

Permission on Target environment objects: After migration we have to make sure, proper permission given in all the folders to user and admin.

Parameter/Variables: We have to change parameter and variables as well in parameter file after creating it in target environment.

Unix/Shell script: Path in shell script as well as access to all user been done.

Recreating Views: As base table got change we have to create view again for new base tables, which is going to be used in target environment.

Creating indicator file: Creating indicator file or getting indicator file from upstream we have to make sure we have done required changes.

Job Schedule: we have to do required changes for job schedule as we have multiple workflow dependent each other we have to make sure we have proper job scheduling.