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.

The name of the processor is MappedVirtualInteractionProcessor. It reads an InfoSphere® MDM Request-Response log file or a Initiate® Interceptor file to extract virtual MDM interactions. The processor then replicates the behavior of the Interceptor. However, instead of requiring the interceptor.jar file, the MappedVirtualInteractionConsumer requires that two versions of the com.ibm.mdm.engine.sdk.madapi.jar file are present:
  • the com.ibm.mdm.engine.sdk.madapi.jar file for the version of MDM you are upgrading from, and
  • the com.ibm.mdm.engine.sdk.madapi.jar file for the version of MDM you are upgrading to.
Note: The location of the .jar file is RAD/RSA install home/com.ibm.mdm.tools/mds_sdk/com.ibm.mdm.engine.sdk.madapi.jar
Note: As the name of the processor suggests, MappedVirtualInteractionProcessor helps to map virtual MDM interactions from one version of MDM to another. If you do not need to do mapping, consider using the VirtualInteractionProcessor, a simpler Batch Framework processor that simply reads a message recorded by the Request-Response logger, passes it to the current com.ibm.mdm.engine.sdk.madapi.jar file, and calls the EXECUTE command.
The diagram shows the flow:
Insert info about the diagram.