Module for AS4 Version 10.1.May 2019 | Understanding and Using webMethods AS4 Module | Installing and Using AS4 Module | Configuring Module for AS4 | Configuring Optional Features | Configuring Reception Awareness
 
Configuring Reception Awareness
If reception awareness is enabled, an initiating MSH sends a user message to the responding MSH. If the responding MSH does not send a receipt within a specified time period, the initiating MSH retries sending the message. This continues until the receipt is received or the value specified in the maxRetries parameter is reached. The activity log in Trading Networks is updated with a message about each retry.
Duplicate detection detects a duplicate user message with the same UserMessage/MessageInfo/MessageId as a previous message. When a duplicate message is received, the message is flagged as duplicate and UserStatus in Trading Networks transaction analysis page is updated to DUPLICATE_RECEIVED.
Configure Module for AS4 to retry sending messages by configuring the reception awareness TPA parameters in the requestUM leg.
*To configure reception awareness
1. In My webMethods: Administration > Integration > B2B > Trading Partner Agreements > Trading Partner Agreement Details.
2. Select the TPA for which you want to configure reception awareness.
3. In the TPA Data panel, specify the following receptionAwareness parameters:
a. enabled: Select true to enable and false to disable reception awareness. The default is set to false.
b. retry: Select parameters that control push retry.
*enabled: Select one of the following:
true—Enabled.
false—Disabled. This is the default.
*Configure the following retryParameters that controls push retry:
maxRetries: Type the maximum number of times the module will try resending a message.
period: Type the length of time, in seconds, the module waits between retry attempts.
c. Select the following duplicateDetection parameters:
*enabled: Select true to enable and false to disable duplicate detection.
*checkWindow Optional. Length of time, in seconds (S) or days (D), that a message ID is retained in the cache and checked for duplicate incoming message IDs (for example, 4320000S or 5D).
*maxSize Optional. The maximum size, in bytes, of an incoming duplicate message that the module will save. When the size of the incoming duplicate message exceeds this value, the duplicate message is not saved in the Trading Networks database and an error is logged.
4. Click Save or Save and Close.
Note:
Duplicate detection will start only after the duplicateDetection parameter is enabled in Trading Networks. All messages received before enabling duplicateDetection are not considered.