1. Babelway
  2. Babelway User Guide
  3. Chapter 4. Manage & Build

4.2.4.13. Http Gateway In

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 of the gateways. 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 from BASIC or CERT. BASIC is user/password authentication. CERT is 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 http(s)://{URL}/ws/HttpPostIn is still available, where {URL} is the same as the one in the new url http(s)://{URL}/ws/gateways/... 

 SOAP HTTP(S) Url 

 Using the SOAP Post protocols. WSDL. 

 Support HTTP and HTTPS protocols. 

 HTTPS Post URL 

 Using the HTTPS 2way authentication Post 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 selects the parameter where to find the content of the message. 

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

This "Gateway In" allow 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.

mceclip0.png

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 contain ~ 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.