The EDIfly service is based on an EDIServer (or a message broker) that intercepts all
Type B and Type X messages that would normally be transmitted via the Type B network. It forwards all messages addressed to other EDIfly users directly to their
EDIServers over the internet thus bypassing the Type B or Type X network; only the
messages addressed to non-EDIfly users are forwarded to the Type B or Type X
network for processing. This means that no application changes are required to take
advantage of the EDIfly service.
The EDIServer has been designed as a modern message broker and therefore
includes a message distribution service allowing messages to be distributed to
multiple back-end systems based on rules defined using any combination of the
sender address, recipient address, or standard message identifier (SMI).
Back-end systems can be connected to the EDIServer using adapters; the following
adapters are currently available and included in EDIfly:
• File Input and Output Adapters
allow messages to be passed to and from
the EDIServer via either a local or remote file system.
• FTP Input and Output Adapters
allow the EDIServer to collect and store
messages on a standard FTP server.
• HTTP Post Input and Output Adapters
allows messages to be passed to and from the EDIServer as standard HTTP Post requests.
• Web Service Adapter allows messages to be send and received via a SOAP web service API.
• MQ Series Input and Output Adapters
provide the interface between the EDIServer and an IBM MQ Series based message infrastructure
• JMS Input and Output Adapters
provide the interface between the EDIServer and any JMS compliant message infrastructure
• MATIP TypeB Adapter
implements the MATIP Type B message protocol
• SMTP Input and Output Adapters
allow messages to be sent to and from
the EDIServer as standard SMTP e-mail messages
• POP3 Input Adapter
enables the EDIServer to download messages from a POP3 mailbox
• POP3 Output Adapter
enables standard email clients to download
messages from the EDIServer using standard POP3 clients
The EDIServer also includes a number of gateways which allow applications to print,
send emails and fax by sending standard Type B messages to the EDIServer.
Each of the adapters connecting a back-end system can be individually configured to
use one of five supported message formats
Standard Type B
Industry SDKs compatible data format
It is important to note that the first three formats are 100% compatible and
interchangeable. Within the EDIServer, these three message formats are all
translated into the same internal message format. This means that a message can
be received in TypeB:XML but forwarded to a back-end system that uses the SDK or
Type B format. In addition to this, the EDIServer also provides translation between
EDIFACT and Type B as defined by IATA.