A Deployment

Version History: Version Date

By

Changes

Contents 1 Executive Summary 1 1.1 Notation 1 2 Folder level deployment 3 Incremental deployment:

1 8

1 Scope To outline the necessary step required for deploying informatica objects for complete and partial deployment from one environment to another. 1.1 Notation Blue colored text Options available in GUI Heading Bolded Text Sub Heading Bolded Italic 2 Folder level deployment Execute the script $PM_HOME/export_fold.sh as infauser, this should create the XML of the whole folder. Also, this should create a ‘folder. log’ file; user can review this to make sure there is no error in exported XML file. It’s very important to export the XML file without any error. a)

Sftp the xml file to development and subsequently to local or share drive.

b) Invoke the repository manager GUI, Choose “Repository -> Import Objects“and choose the XML which was copied over from the server. Fig 1 c)

Informatica will analyze the XML file and collate all the require information Fig 2

d) For a full deployment, choose the top level folder and move onto the right pane. If there are shortcuts referring to the folders, those also will be displayed on the left pane. You don’t have to choose the folder which contains shortcuts. As, it’s a prerequisite that all the shortcuts are deployed prior to the referenced object. Referenced object deployment Fig 3 Standalone object deployment: Choose the complete folder Fig 4 e) If the name of the folder need to be changed, it can be done by pressing the down arrow in the ‘Destination folder’ : If this is redeployment make sure the folder name is same as ‘Folder in XML File’, otherwise, this could potentially overwrite the folder specified in Destination. Standalone object Fig 5 Referenced object Fig 6

f) Next step will provide more control on what objects to be deployed and what sort of action to be taken if any conflicts occur during deployment. Choose ‘all objects’ under ‘Selection Criteria’ and ‘Prompt User’ under ‘Section Resolution’ Note: By default there will not any rule, you need to click on ‘New Rule’ to add. Fig 7 g) Upon clicking Import, informatica will produce a conflict report and expect the user to choose the course of action. This is pretty important step and a wrong option might lead to unwanted results. For a fresh deployment, usually there won’t be any conflict, if at all there is it could be for the ‘default session config’. See below for the resolutions. General Conflict resolutions: Conflict can occur when / if another workflow with the same name exists already. Choose ‘Reuse’, if you decide to use the existing one available in the destination.(choose this option for ‘default session config’ conflict) Choose ‘Overwrite’ if you want to overwrite the existing object in destination with the object to be deployed Choose ‘Rename’, if you decide to keep both the objects Choose ‘Skip’ if you decide to skip this object from deploying. Session Conflict: For the mapping which had gone changes, informatica will ask user to decide which mapping session correspond to a session, user needs to associate the session to the right mapping. Shortcut Conflict: As a rule of thumb, make sure shortcuts are available well ahead of deploying the objects that are being referenced, On account of object is deployed without parent objects, then all the links to and from the objects will be disconnected. If the copy folders option is selected and if the parent for the shortcut(s) is/are not available then shortcut will be created as copy. So the bottom line is, be sure to successfully deploy the parent of the shortcuts first of everything. Fig 8

h) Once done, Summary of the conflict resolution will be displayed, go through it carefully to make sure all the actions are correct.

Fig 9

i)

Once all the conflicts are resolved, we are ready to deploy Fig 10

will be be

On clicking of import, progress bar showing the current status and output window be displaying the messages for each object. Any failures / errors / warning must looked upon and rectified. Post deployment, messages in the output window can saved on a separate file for future references. Also, if you are a implementer you need to mail this log file back to the group or person raised the request.

Fig 11 j) Once the object is deployed make sure they are valid, if not , validate them either in the respective client or repository manager. 3

Incremental deployment:

Informatica allows to export multiple objects into one XML file, this is available starting from 7.X. Incremental deployment is necessary whenever an existing object undergone a change or when a new functionality is introduced. Deployment of existing object is not very much different from deploying a full folder, except the conflict resolution step. Here we don’t need to export the XML via script; rather we can do it from client GUI. a)

Connect to the source repository in Repository Manager.

b) Highlight the relevant mapping / maplet / transformation to be deployed from the source repository c)

Choose ‘Repository-> Export Objects‘

Fig 12 d) Examine the log files for any errors. e) If no errors on step d, connect to the target repository and open the folder in which object o be deployed. f) Choose ‘Repository-> Import Objects‘ g) Once the object is deployed make sure they are valid, if not validate them either in the respective client or repository manager Fig 13 h) Choose only the relevant object, referenced object need not be selected. Again this is under assumption parent of the shortcut has been already available in target repository i)

Repeat the steps 2.d through 2.i from folder level deployment.