Using HTTP Adapters with Ensemble
Settings for the HTTP Outbound Adapter
Provides reference information for settings of the HTTP outbound adapter, EnsLib.HTTP.OutboundAdapter.
The outbound HTTP adapter has the following settings:
||HTTP Server, HTTP Port, URL, Credentials
||SSL Configuration, SSL Check Server Identity, Proxy Server, Proxy Port, Proxy HTTPS, Response Timeout, ConnectTimeout
Specifies the number of seconds to wait for the connection to the server to open. The default value is 5.
If the connection is not opened in this time period, the adapter retries repeatedly, up to the number of times given by Failure Timeout
divided by Retry Interval
Specifies whether the proxy (if any) uses HTTPS to communicate with the real HTTP/HTTPS server.
Specifies the proxy server port on which to send HTTP requests, if using a proxy server (will use 8080 by default).
Specifies the proxy server through which to send HTTP requests, if any.
Specifies the timeout for getting a response from the server (the timeout for opening the connection to the server is set by ConnectTimeout
). The default value is 30.
SSL Check Server Identity
Specifies that when making an SSL connection, the adapter should check that the server identity in the certificate matches the name of the system being connecting to. This defaults to specifying that the check should be made. Uncheck this for test and development systems where the name specified in the SSL certificate does not match the DNS name.
The name of an existing SSL/TLS configuration to use to authenticate this connection. Choose a client SSL/TLS configuration, because the adapter initiates the communication.
If your SSL configuration requires a private key password, include that in the SSL Configuration
setting. To do so, add a vertical bar character |
after the configuration name, followed by the password. For example: MySSLItem|mypassword
is a Boolean setting that controls whether the outbound adapter creates a SuperSession header in the HTTP header and assigns an identifier to it. When finding a message, you can use the SuperSession value to match a message in one production with the related message in another production. Within a production, it is easy to track a message as it travels between business services, processes, and operations using the SessionId. But once a message leaves a business operation via an HTTP message and enters a different production, the production receiving the message assigns a new SessionId.
Check if the message has an empty value in Ens.MessageHeaderBase.SuperSession property. If it does have an empty value, the adapter generates a new value and stores it in the SuperSession property.
Stores the value of the SuperSession property in the private InterSystems.Ensemble.SuperSession HTTP header of the outgoing message.
When an HTTP incoming adapter receives a message, it checks for the SuperSession value in the incoming HTTP message header. If the value is present, it sets the Ens.MessageHeaderBase.SuperSession property. This property is preserved as the message passes from one production component to another.
There are no tools to automate tracking messages between productions using SuperSession.
URL path to request from the server (not including http://
or the server address).
Specifies whether to save cookies received in HTTP responses while this adapter is instantiated, and insert them in each subsequent HTTP request.