Generating, Persisting, and Mapping a Message ID 

Use

The mapping of an XI message ID to an external message ID is saved to identify duplicate messages or to track a message. You can use the MessageIdMapper for the mapping.

See: Steps in the Asynchronous Receiver/Outbound Message Flow and Steps in the Asynchronous Sender/Inbound Message Flow

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	J2EE service
Technical name	com.sap.aii.af.service.idmap com.sap.aii.utilxi.misc.api
Certification	Optional
Syntax	See Javadoc (.\index.html) package com.sap.aii.af.service.idmap

Features

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

The example shows how the MessageIDMapper is used. It also shows how the GUIDFactory and IGUID help classes are used to generate an ID before creating a message.

You can use this mechanism if you want to generate the XI message at a later point in time, for example, in the modules of the Adapter Framework. However, the mapping must be executed in the adapter so that the procedure complies with the general strategy for using transactions.

In the call for createIDMap(), the XI message ID must be specified as a hexadecimal string if you use callPMIAgent and this is set to TRUE.