The eiConsole and eiPlatform support the HTTP Post Transport for communicating with a wide variety of HTTP compliant Target systems. To configure the HTTP Post Transport, select this option from the Transport Type drop-down.
On the Basic configuration tab, you will see the Target URL configuration item. Here you’ll enter the URL for where you wish to send the data to. The Test Connection button allows you to test the connection using the specified Trust Store. The Timeout field specifies how long in milliseconds the transport should wait for a response before timing out the connection
The Credentials tab allows you to specify the Credentials to use if the website that you’re posting to requires HTTP Authentication. Here you will enter the User Name, Authentication Host string, Authentication Port (Post) and the Password. The Preemptive Authentication allows the users to select preemptive authentication.
On the Response tab you can specify:
Response Listener: The programmatically-invoked Listener to be invoked upon response.
Response Code Handling: Determine how to treat HTTP response codes. Can be Default, Error Only On Listed Codes and Succeed Only On Listed Codes.
Response Codes: Comma-separated list of HTTP response codes.
Error on connection failure: Specifies if this transport should throw an Exception on timeout/connection failures.
On the Advanced tab, should you wish to handle the HTTP response, enter the name of the triggerable or programmatic Listener to invoke by entering that in the Response Listener configuration item. If you wish to take that response from a particular Form Element, enter in the Form Element configuration item. On the Advanced tab, you can also configure HTTP Headers. These are the Headers that will be used when posting the data. One typical example of a configured Header is the Content-Type, which is defaulted to a value of text/xml, which may need to be modified for your specific purposes. Also, you can specify the TLS Version with an optional ability. This should ONLY be used if having difficulty connecting to a server using TLS 1.1/1.2. In the TLS Version drop-down menu, you can choose TLSv1.1 or TLSv1.2
Explicitly Disable Chunking: specifies if HTTP chunking encoding should be explicitly disabled
Trust self-signed certs: enables a trust strategy that accepts self-signed server certificates as trusted
Validate SSL Hostnames: SSL certificates include hostnames that they are valid for, under certain circumstances, you may want to disable this hostname validation
On the Proxy tab you can configure the HTTP Transport to use a particular Proxy. This is useful in corporate environments where all HTTP traffic is Proxied through an internal server. The Use Proxy configuration item should be checked when you wish to send data through a known Proxy. When the Use Proxy configuration item is checked, the Proxy Host configuration should be configured to include the IP address that the Proxy will be using. The Proxy Port configuration item will specify the Port of this Proxy. Should this Proxy require authentication, The Proxy Authentication Username should be populated with the Username used to authorize with the Proxy Authentication Password should be populated with the password used to authenticate.
On the KeyStore tab you can specify:
KeyStore Path: The file path for the certificate file.
KeyStore Type: The format of the certificate file.
KeyStore Password: The certificate password.
Use KeyStore Attribute: Specifies whether a certificate is to be loaded from a transaction attribute.
KeyStore Attribute: Specifies the attribute to load the certificate from.
When you set Key file location, note that network paths are not evaluated in the eiConsole.
On the TrustStore tab you can specify:
Trust Store Path: File Path for a certificate store.
TrustStore Type: The format of the TrustStore file.
Trust Store Password: Password for the certificate store.
Use Trust Store Attribute: Specifies whether the trust store is to be loaded from a transaction attribute.
Trust Store Attribute: Specifies attribute to load the trust store from.
On the Encoding tab you can specify:
URL Param Encoding: the encoding to use for any parameters in the URL string
Form Element Encoding: the encoding to use for the value if the Form Element option was specified in the configuration
Error Response Encoding: the encoding to use when serializing a response message in the event of an error with the request