Message exchange platform

The concept of electronic message exchange by means of asynchronous messaging has been around since the early 90’s when EDIFACT messages were exchanged between insurance carriers and agents over the Insurance Data Network (ADN).
Despite the increasing use of webservices as an alternative, asynchronous messaging through a digital post office box is still an integral part of current business processes. The fundamental principle is that messages to and from different parties are delivered to, and collected from, one single location. Each party has a single clear 1:1 message exchange point, instead of an 1:n distribution. This simplifies technical complexity and gives low cost of ownership for the entire distribution chain. Although new formats and message exchange platforms have been added to the message exchange realm, the basic principle of an asynchronous exchange of data through a PO box structure has remained the same throughout the years.

In recent years the required technology has become less complex, and more accessible due to the functionality becoming embedded in other solutions. Setting up an asynchronous messaging system to send or retrieve a message is relatively simple and does not require much effort. But, at the same time, technological development in general has led to higher expectations for volume handling and response time, as well as near real-time asynchronous messaging possibilities.

The container function group provides a message exchange platform (MEP) as an API-based man-in-the-middle PO box solution. This concept is described in the first section, followed by the description of the functions.


Thanks for your feedback.

Post your comment on this topic.

Post Comment