4.2.2.13. HTTP Gateway In – Babelway

With an Http In Gateway, incoming messages are received as HTTP Post on the Babelway HTTP server and processed as soon as they arrive.

The HTTP Post can use the following encoding method: HTML Form, base64 and urlencode.

Babelway is supporting synchronous processing of messaging. This is available when you submit messages using our HTTP gateway using SOAP and the SOAP operation: "process Message". The response will contain the final result of the execution of the messages. If the messages generate more than one message, the response will contain the full graph of processed messages.

It is also available through the REST API gateway. There is only a limited available documentation on this topic, but we would be more than happy to understand more your requirements and provide a proof of concepts for you.

The specific settings are:

Authentication method	You can select between: BASIC: user/password authentication CERT: 2-way SSL authentication. OAuth 1a
Username	Login or username to access the service.
Password	Password associated with previous username.
2-way auth. certificate	The certificate used to validate the client certificate.
HTTP(S) Post URL	Using the HTTP(S) Post protocols. Support HTTP and HTTPS protocols. The old address is still available, where {URL} is the same as the one in the new url http(s)://{URL}/ws/gateways/... http(s)://{URL}/ws/HttpPostIn
SOAP HTTP(S) Url	Using the SOAP Post protocols. WSDL. Support HTTP and HTTPS protocols.
Submitted using a FORM	Check the message posting was performed using a Http POST submit.
FORM parameter	If the option "Submitted using a FORM" is used, this field will indicate the parameter that will contain the content of your message. All other form fields and their values will be added as user metadata. You can access them in the rest of your channel steps.

Note: The HTTP server Gateway uses the port 80 for HTTP and 443 for HTTPS.

This "Gateway In" allows you to provide the username and password in the URL when using the HTTP Post URL, The below print screen shows an example for this configuration.

HTTP Gateway IN example

The URl is http://eu1.babelway.net/ws/gateways/501484?userName=test4321&pwd=kM7kqSpFRkSX5nXZ

Note:

You will need to download the WSDL file for this gateway by using the SOAP URL in the browser then login using the user name and password for this gateway in order to download the WSDL file for this environment as for some environments the SOAP URL and the WSDL file are different from other environments.
When using OAuth 1a, Then the Authorization header, must be in the request headers, and not in the body.
If there is a file name provided in the "Message In" or "Message Out" which contains a ~ tilde character, All browser based on Chromium will replace the ~ tilde character by the _ underscore character when you try to download the file from the Babelway interface, For more details you can check this link https://bugs.chromium.org/p/chromium/issues/detail?id=479419
The maximum file size accepted by this gateway is 100 MB.

FORM Usage

You can use 2 types of Http methods, the POST and the POST/Multipart.

POST

Used with a Content-Type like application/json or application/xml.

The field defined as FORM PARAMETER is used as the channel message, all the other fields are saved as user metadata and can be used later.

The "Filename In" and the "Reference" in Babelway will be "attachment" by default.

POST Multipart

Used with a Content-Type: multipart/form-data.

The field defined as FORM PARAMETER is used as the channel message. All the other fields are save as user metadata and can be used later.

If the type of the field is FILE, the name of the file will be used as "Filename In" and "Reference" in Babelway.