Generating, Persisting, and Mapping a Message ID 

Use

To identify duplicate messages or trace back a message, the mapping of an XI message ID to an external message ID is saved. You can use the MessageIdMapper for the mapping.

More information: Transactions for the Asynchronous Sender Direction, Transactions for the Asynchronous Receiver Direction

Interface Overview

Characteristic	Value
Name	AF utility service
Purpose	To create message ID mappings for checking duplicate entries and for tracking in the PMI
Type	Service in the facade com.sap.aii.af.svc.facade
Technical name	com.sap.aii.af.service.idmapi
Certification	Optional
Syntax	JavaDoc package com.sap.aii.af.service.idmap

Features

●      The example shows how the MessageIDMapper is used.

Open SPIManagedConnectionFactory.java and search for the character string CS_IDMAPINSERT.

●      AS Java makes the library com.sap.guid available. You can use this library to generate ISO-compliant GUIDs on AS Java.

Open SPIManagedConnectionFactory.java and search for the character string CS_GUID.

If the XI message is created in the modules of the Adapter Framework, for example, you can use this mechanism. Generate the message ID in the adapter and specify it during instantiation of the XI message.

However, the mapping of the IDs must be executed in the adapter so that the procedure complies with the general strategy for using transactions.

When connecting to PMI, note that the XI message ID must be specified as a hexadecimal string if the parameter callPMIAgent is set to TRUE . Only then does the string comparison of the message ID string on the Integration Server match that of the adapter.

More information: Connecting to PMI.