4.2.4. Gateway IN Types – Babelway

Here is the list of all the gateway types available for gateway INs used to receive messages into Babelway. You will find additional information about how to use and configure them.

Email Gateway In: Incoming messages are attached to email messages and sent to a specific Babelway email address and processed as soon as they arrive.
IMAP mail client Gateway In: This gateway allows the customer to connect his own mailbox to Babelway. Babelway then polls a folder in the mailbox as messages. We use the IMAP protocol to connect and fetch mail. This could be used for example to poll messages from your gmail or outlook account.
FTP Client Gateway In: Incoming messages are polled and retrieved from a remote ftp server using a login and password.
SFTP Client Gateway In: Incoming messages are polled and retrieved from a remote sftp server using a login and password.
FTP Server Gateway In: Incoming messages are transferred to a specific Babelway Ftp server and processed as soon as they arrive.
SFTP Server Gateway In: Incoming messages are transferred to a specific Babelway sftp server and processed as soon as they arrive.
AS2 Gateway In: A communication standard largely used in retail environment to secure communications over the Internet.
Internal Gateway In: A gateway used to transfer messages between 2 channels within Babelway.
Message record Gateway In: Used to export the messages details from the Monitoring in a message processed by the channel.
Lookup table Gateway In: Used to create a message using values present in a lookup table.
OFTP Server Gateway In: Incoming messages are transferred to a Babelway specific OFTP server and processed as soon as they arrive.
OFTP client Gateway In: Incoming messages are polled and retrieved from a remote OFTP server using login and password
Http Gateway In: Incoming messages are transferred to a Babelway specific Http server and processed as soon as they arrive and it is using synchronous request.
Rest Gateway In: Allows you to implement a REST API and it is using synchronous request.
Http Client Gateway In: Incoming messages are polled and retrieved from a remote Http server.
Http Client Gateway In (Deprecated): Incoming messages are polled and retrieved from a remote Http server.
X.400 Gateway In: Incoming messages are transferred to a Babelway specific X.400 server and processed as soon as they arrive.
Scheduler Gateway In: Create new messages based on time triggers.
SAP Gateway In: Incoming messages are pushed to Babelway from an SAP server and processed as soon as they arrive.
Dropbox Gateway In: Incoming messages are polled from a Dropbox account.
Tradeshift Gateway In: Incoming messages are polled from a Tradeshift account.
E-conomic Gateway In: Incoming messages are pushed to Babelway from an E-conomic account and processed as soon as they arrive.
VAN Gateway In: Incoming messages are polled from ECGrid VAN.
PEPPOL Gateway In: Incoming messages are received from the PEPPOL network.
RosettaNet Gateway In: Incoming messages are received from a RosettaNet server.
ePrior Gateway In: Incoming messages are received from ePrior requests.
Simpl.ePrior Gateway In: Incoming messages are received from Simpl.ePrior requests.
Amazon Marketplace Gateway In: Incoming messages are polled from an Amazon marketplace account.
NemHandel Gateway In: Incoming messages are received from the NemHandel network.
Chorus Pro Gateway In:This gateway allows you to get information from the Chorus Pro platform, the French administration network.
Oracle Fusion Gateway In: Incoming messages are received from the Oracle Fusion CMK.
Database Gateway IN: pulls rows out (gateway IN) of a table and converts them to an XML file
AS4 Gateway In: Incoming messages are received from a requests.
Netsuite gateway IN: Incoming messages are received from a requests.