Manage duplicate messages in peer network

If you plan on using the peer network to link instances of Interchange that are actively trading, you must implement a solution for detecting duplicate messages.

You do not need to manage duplicate messages if the peer network is employed only to promote configurations from a staging environment to a production environment or only as a backup to a production environment.

Normally Interchange handles duplicate messages effectively on its own. At the business protocol level, Interchange always checks for duplicate messaging IDs in the headers of packaged inbound messages. Optionally, Interchange also can be set to detect and reject duplicates after unpacking inbound messages and checking document content for such things as duplicate EDI control IDs (see Inbound message validation rules). But in a peer network, duplicate message checking is not reliable because only objects are shared between peer databases, not messages.

There are a number of possible solutions. The following describes some of these. Keep in mind these are general descriptions. You may require the help of a professional services consultant to plan and implement a solution that works for your peer network.

Have the back-end perform duplicate checking

This solution presumes the peer network has a common back-end system to which inbound messages from all peers are sent. If the back-end system does not perform duplicate checking, a tool would have to be developed for detecting duplicate messages based on parsing document content.

Use a smart router to direct inbound messages

An intelligent router could be employed as an advanced load balancer. The router would ensure duplicate messages are predictably routed to the same peer, making duplicate checking reliable.

The router could:

  • Remember messaging IDs and always route duplicate messages to the same peer.
  • or
  • Use an algorithm based on information such as the sender IP address or the message ID to predictably route duplicate messages to the same peer. For example, a scheme based on a hash of the message ID could route odd numbers to peer 1 and even numbers to peer 2.

Related topics

Related Links