You could select an Application connection type to access PowerExchange sources and targets. In 10.5 you could use a relational connection object for each Netezza source or target that you want to access. The relational database connection defines how the Integration Service accesses the underlying database for Netezza Performance Server. When you configure a Netezza connection, you specify the connection attributes that the Integration Service uses to connect to Netezza.
Appreciate for responding quickly. What you have suggested is for new development which is the best practice. If we already have 1000's of workflows in Production does it going to impact? Is there any Global Change that was part of the 10.5 upgrade recommended by Informatica. Let me know?
I don't know whether this is taken care of as part of a repository upgrade, but if not, there is a possible strategy. Not nice but works.
Export all affected workflows to XML files (e.g. one XML per folder).
Build a process to patch these XML files such that the relational Netezza connections are replaced by Netezza application connections. In a XML export, that should only take one string replacement, no more.
However, it is important that these connections are set up in the target repositories before these XML files are imported, otherwise you will end up with 1000s of invalid sessions / workflows.
In other words: the upgrade process will become more complex because you cannot simply upgrade the repository contents IF that should not be part of the built-in upgrade process. But it is possible.