Babel Academy
Community Forum
Support
- Welcome
- Introducing Babelway B2B Integration
- Starting with Babelway
- Managing Account Environments
- Managing Channels
- The Catalogue
- Tracking Messages
- Managing Alerts
- Managing Your Account
- Best Practices
- Channels
- List of Channels
- View Change Log
- General
- Gateway In
- Message In
- Transformation
- Message Out
- Gateway Out
- Email Gateway Out
- Ftp Client Gateway Out
- SFTP Client Gateway Out
- Ftp Server Gateway Out
- AS2 Gateway
- Http Client Out Gateway
- Web Gateway
- Generic Gateway
- Internal Gateway Out
- Null Gateway
- OFTP Server Gateway out
- OFTP client Gateway out
- Http Out Gateway
- SOAP Gateway
- Soap Client Out Gateway
- X.400 Gateway out
- Aggregator Gateway Out
- Email Gateway Out
- Email Notifications
- Routing
- Testing
- List of Channels
- Building a Channel
- The Catalogue
- Tracking Messages
- Alerts
- Account Management
- Rest API
- Receive Orders From
- Receive Orders from Colruyt
- Receive Orders from Carrefour
- Receive Orders from Brico
- Receive Orders from Castorama
- Receive Orders from Cora BE
- Receive Orders from Delfood
- Receive Orders from Delhaize
- Receive Orders from DEliXL
- Receive Orders from Intergamma
- Receive Orders from Intermarche
- Receive Orders from JavaFresh
- Receive Orders from Makro
- Receive Orders from Match
- Receive Orders from Carrefour France
- Receive Orders from Armonea
- Receive Orders from Colruyt
- Integrate Orders with
- Tradeshift
- Integration with Exact Online or Exact Globe
- Channel:SAP Idoc XML Order05 w/ Http client out
- System Metadata
- ODETTE Messages List
- External References
See: Managing Channels - Manage a Channel
With an Http in Gateway, incoming messages are received on a Babelway specific server and processed as soon as they arrive.
To create a Http in gateway, select an existing template or make a copy of the generic Httpin template in the catalogue and following screen will be displayed.
The following fields should be defined in order to configure your Http in access:
Login or username to access the service . | |
Password associated to previous username. | |
using the HTTP Post protocols. | |
using the SOAP Post protocols. WSDL |
After channel deployment, your connection will be available to send messages.
The HTTP Post can do the following:
Take the input of the HTTP Post as the message.
Use the HTTP Post with an HTML Form. You need to set the string-property "contentIsForm" to true. You can specify which parameter to use as the file input "messageParameterName". You can also decode the message with one of the following method : "base64" and "urlencode".
 Prev |  Up | Next |
| 1.4.11. OFTP client Gateway In |  Reference Manual | 1.4.13. X.400 Gateway In |