Upgrading from Initiate Master Data Service, prior to version 11

A set of steps describes the process of upgrading from Initiate Master Data Service® to InfoSphere® MDM version 11.4.

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.

There are separate steps required to upgrade from pre- and post-version 11.0 releases of InfoSphere MDM products. The version 11.0 release of InfoSphere MDM represented several large-scale architecture changes to the Initiate Master Data Service application (virtual MDM). 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 InfoSphere MDM combines the Initiate Master Data Service application with the InfoSphere MDM Server application, it creates a default set of table spaces and shared schema definitions designed to accommodate the legacy needs of both applications. 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.4 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.4.

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.

The following overview diagram conceptually shows the upgrade process for the various components, where the grey boxes show components that are taken offline after the upgrade:
Figure 1. Upgrade overview: Initiate components in version 11.4
Components in the upgrade process are shown.
  1. Updating custom code for new security requirements
    You must modify custom code to include credentials to create contexts. Until it is updated, existing code does not compile against the new API JAR file.
  2. Upgrading the existing database for Initiate Master Data Service
    When you install the new version of InfoSphere MDM, you must point to a new database. Do not provide the connection information for the existing database that you are upgrading.
  3. Modifying server configuration and updating configuration tables
    You must update the data sources, messaging engines, and installation name to link the upgraded database to the InfoSphere MDM application.
  4. Encrypting database passwords in configuration files
    To encrypt the database passwords stored in configuration files, follow the steps in this procedure.
  5. Moving the Initiate user repository
    If your installation of Initiate Master Data Service uses the internal LDAP user repository, you can move the content of the repository into a WebSphere® Application Server user repository or into an external LDAP repository that you choose.
  6. Migrating configuration settings from Initiate
    Migrate customized values from key configuration files within Initiate so that they are available within your new InfoSphere MDM installation.
  7. Upgrading Initiate clients and other components
    You must install the 11.4 clients and set up their connections to the operational server.
  8. Finalizing and verifying your upgrade
    You finish the upgrade process by finishing some final tasks and verifying that the new system is functional.
  9. Sample: Interceptor tool
    To minimize the impact of downtime during upgrade, the current release provides a sample tool called Interceptor that you can use to capture incoming interactions while the operational server is offline being upgraded. When the upgraded operational server is online again, you can replay the captured interactions to the upgraded operational server.
  10. Sample: MappedVirtualInteractionProcessor
    As an alternative to the Interceptor tool, you can use a new Batch Framework processor to extract virtual MDM interactions and replay them to an upgraded operational server.
  11. Sample: VirtualInteractionProcessor
    As a second alternative to the Interceptor tool, you can use a new Batch Framework processor to extract virtual MDM interactions and replay them to an upgraded operational server. Unlike the MappedVirtualInteractionProcessor processor, the VirtualInteractionProcessor processor does not map interactions from one format to another. Use it only if you are sure that your virtual MDM interactions can be replayed without being mapped to the format for the upgraded operational server.
Previous topic: Upgrading from InfoSphere MDM version 11.0 or 11.3
Next topic: Upgrading from InfoSphere MDM Server, prior to version 11
Related concepts:
Architecture and concepts

Last updated: 22 Apr 2016