To outline the necessary step required for deploying informatica objects for complete and
partial deployment from one environment to another.
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 \u2018folder. log\u2019 file; user can review this to make
sure there is no error in exported XML file. It\u2019s very important to export the XML file
without any error.
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\u2019t have to choose the folder which contains shortcuts. As, it\u2019s a prerequisite that
all the shortcuts are deployed prior to the referenced object.
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 \u2018all objects\u2019
under \u2018Selection Criteria\u2019 and \u2018Prompt User\u2019 under \u2018Section Resolution\u2019
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\u2019t be any
conflict, if at all there is it could be for the \u2018default session config\u2019. See below for the
General Conflict resolutions:
Conflict can occur when / if another workflow with the same name exists already.
Choose \u2018Reuse\u2019, if you decide to use the existing one available in the
with the object to be deployed
Choose \u2018Rename\u2019, if you decide to keep both the objects
Choose \u2018Skip\u2019 if you decide to skip this object from deploying.
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.
This action might not be possible to undo. Are you sure you want to continue?