Configure the HTTP Transport Connector

The HTTP Sender makes it possible to send messages to other systems or sites using SOAP/XML and the HTTP/HTTPS protocol.

Note: You can also use HTTP Sender for sending SMS messages. Most Cellular Phone providers, among them Clickatel, offer their customers to send SMS using Web Services.

Note: There is no HTTP Reader. Reading messages that are sent using the HTTP protocol is done using the SOAP Gateway.

Contents

• Common parameters
• HTTP sender specific parameters
• Configure HTTP Sender for SSL Server Authentication (https)
• How to create new instances of the HTTP Connector

• How to setup a HTTP call to a Bizapi in a remote IFS System

HTTP Sender specific parameters

• ACCEPTED_CODES
  Comma or semicolon separated list of response HTTP codes for which the sender will return response body rather then throwing an exception. The actual response code is saved to Application Context with name HTTP_RESPONSE_CODE.
• DEFAULT_RESP_ENCODING
  If the response is not binary and not an XML document with valid encoding specification in the XML header, this encoding will be used to decode received response. Default is UTF-8.
• TRACE_PATH
  Defines the path where the trace logs (i.e. the request and response) of the sender will be created. If not specified there will be no trace logs created.

Additional parameters are specified on Routing Address for Destination Type Http.

Configure HTTP Sender for SSL Server Authentication (https)

Server Authentication means that client (HTTP Sender) will not authenticate itself, but it will require that the server it connects to authenticates itself.

Server Authentication is the most common mode of SSL / TLS operation. If you are uncertain what kind of SSL mode you should configure, this is probably what you want to configure.

Whenever HTTP Sender attempts to connect to an external service over SSL (https protocol), it will only be able to connect to it if it can trust the certificate loaded there. As HTTP Sender is a Java application, the way trust is handled is that you have a keystore (typically <java_home>/jre/lib/security/cacerts) or also known as the trust store. This contains a list of all the known CA certificates and Java will only trust certificates that are signed by those CA certificate or public certificates that exist within that keystore.

So if you intend to access an external service via HTTPS and a self-signed certificate or a certificate that is not signed by a CA authority is being used to secure the external service, you'll need to import the certificate to your keystore.