Mapping Interceptor interactions to the new version

The Replayer client takes advantage of existing code to map interactions from prior versions of InfoSphere® MDM to the format that the current version of InfoSphere MDM uses.

About this task

The format of virtual MDM interactions can vary from one version of InfoSphere MDM to the next. For that reason, using the Interceptor tool for upgrade must map the interactions generated within your version of Initiate Master Data Service® (MDS) to the interaction format for the version to which you are upgrading.

While running the upgrade you capture interactions using the Recorder tool. For Initiate Master Data Service (MDS) versions 8.7 through 10.1, the Recorder tool is available as part of the engine software, as explained in a previous topic. After the upgrade is complete, you can map the interactions captured by the Recorder tool so that they conform to the interaction format used by the version of InfoSphere MDM to which you have upgraded. After you have completed the mapping, you can replay the interactions using the Replayer tool.

To convert the interactions, a file reader that is part of the Replayer tool reads the recorded interactions. Part of the recorded interaction is the version number for the Initiate® Master Data Service (MDS) installation that was used to record the interaction. For example, in the following interaction, the 100 (in bold) indicates that the transaction was recorded using version 10.0 of Initiate MDS:

1309192629972|231|0|100|4d454d435245415445000000006e000000010073797374656d0073797374656d00...000000|MEMCREATE|system|[RMC:]

The .jar file for the Replayer tool contains a snapshot of the API for multiple previous versions of the Initiate MDS. The package name for each version is madison<version-number>.mpi. The interceptor.jar file contains a package for each of the previous versions of Initiate MDS. These packages correspond to previous versions of the madapi.jar file:

madison95.mpi
madison92.mpi
madison90.mpi
madison87.mpi

Because each previous version's format is included with each release, the mapping mechanism uses the .mpi package for the version of MDS in which the interactions were originally recorded. That package contains the format information that the mapper needs to read those interactions and map them to the format of the version you are upgrading to. Specifically, the Replayer reads the message, detects the version (which is embedded in each interaction), and then instantiates the correct package.

You run the Replayer client as described in the next topic. When you do, it accesses the madapi.jar file for the current version (the version you have upgraded to). Based on the discovered version for the recorded interactions, the Replayer client calls the appropriate mapper in order to map the interactions from the old format to the new format. After the message is mapped from the old version to the new version, the Replayer client calls the EXECUTE method on the API to run the interaction against the operational server (engine):

Recorded interactions are prepared for mapping by the Interceptor. The Mapper reformats the interactions and uses current madapi.jar file to generate the new interactions to be written to the Engine.

Last updated: 22 Apr 2016