A set of steps describes the process of upgrading from Initiate Master Data Service® to InfoSphere® MDM, Version 11.3.
About this task
Upgrading your MDM environment often requires assistance from members of your own organization as well as IBM® Services or an IBM consulting partner. Do not upgrade your implementation without first identifying the team and relying on guidance from that team.
The version 11.0 release of InfoSphere MDM represented several large-scale architecture changes to the Initiate Master Data Service product. Most significantly, the engine and its services began to run exclusively within an application server. The application server provides infrastructure (for component-to-component communication, authentication, and logging) that was previously managed by the Initiate® application itself. WebLogic and Tomcat application servers are no longer supported.
In addition, because the InfoSphere MDM product combines the Initiate Master Data Service product with the InfoSphere MDM Server product, it creates a default set of table spaces and shared schema definitions designed to accommodate the legacy needs of both products. For that reason, the upgrade process allows you to update your Version 10.1 database and then point to that database from your Version 11.3 installation.
If you are prompted that you are missing "add" xeia records and asked whether you want to insert them, choose yes. The installation process assumes that these records are inserted prior to the upgrade to Version 11.3.
A third architectural change involves LDAP. The Initiate Master Data Service product included an embedded LDAP directory server. By contrast, the InfoSphere MDM product takes advantage of the LDAP directory server available within the application server. Initiate Master Data Service customers using the embedded LDAP server will have to export LDAP content and import it either into the application server LDAP directory server or into an external LDAP directory server.
Lastly, because of new security requirements, unsecured context is no longer supported. You must modify custom code to include credentials in order to create context pools or contexts. Until it is updated, existing code will not compile against the new API JAR file.
