

In addition any external use of the stored procedure API will need to be updated. The effort involved in converting these user exits to Java will depend on many factors, not the least of which is the use of the deprecated stored procedure API’s that Informatica has moved into the Services Integration Framework. Customizations to hub server logic through database user exits will need to be refitted or rewritten in Java as the API was deprecated after version 9.5.1. Finally, if your current version is prior to 9.6 you may need to convert hub user exits from PL/SQL to Java. In addition in v9.5.1 the Timeline feature was introduced, which will likely require a data migration effort to maintain the effective date functionality as well as some re-work in the Data Director (IDD) user interface. If your current version is prior to v9.5.1 it will be necessary to perform a metadata conversion as there were significant changes to the structure of lineage metadata in this version. The key factors that will determine the scope of effort of an upgrade are:

Once you have confirmed that everything has been successfully transitioned to the new version you can start working on new enhancements and other improvements. The first priority should be to ensure that your existing functionality is working and regression tested on MDM 10. There are enough moving parts in the upgrade itself that it is not advisable to also attempt to enable new features or perform other enhancements at the same time. There are several factors that will influence the effort required to perform an upgrade to MDM 10, with the total effort varying from as little as just a few weeks to as long as several months from start to finish.īefore I delve into the various aspects of the actual upgrade I would like to make a recommendation: focus first on upgrading current functionality and wait to enhance with new functionality after the upgrade itself is complete.

In this part of the Upgrading to Informatica MDM 10 series, I will focus on what one needs to be aware of when upgrading existing functionality to the new version. In my last post I talked on a high level about the new features of Informatica MDM 10 and the driving reasons behind considering an upgrade this year, especially for those who are currently on versions 9.5.1 and lower.
