Software AG Products 10.7 | Administering Integration Server | Configuring the Server | Configuring Outbound HTTP Settings
 
Configuring Outbound HTTP Settings
 
Specifying Outbound HTTP Settings
Outbound HTTP parameters control how the server presents and processes outbound HTTP and HTTPS requests (i.e., requests that Integration Server issues on behalf of a client). The parameters control behavior such as how long the server waits for a response, how many times it retries a failed request, and so forth.
Developers can override some of the server's outbound HTTP setting defaults at run time, as described below.
Parameter
Description
User Agent
Specifies the value that the server uses in the HTTP User Agent request header that it sends when requesting a web document. The User Agent header tells a web server what type of browser is making the request. In the case of the Integration Server, the User Agent header indicates the type of browser that the Integration Server appears to be to the web server. Some web servers examine this header to determine a client's capabilities so they can tailor their responses accordingly.
When you install the Integration Server, the User Agent parameter is set to Mozilla/4.0 [en] (WinNT; I). You can change this value as you need; however, the value you set should satisfy the majority of services that your server executes.
Be sure your developers know the User Agent value your server uses. If their applications require a different User Agent, they can override the server's default at run time by including an HTTP User Agent header with their request.
Maximum Redirects
Specifies the number of times that the Integration Server allows a request to be redirected (i.e., automatically sent to another URL by the target server. If a request exceeds the specified number of redirections, the Integration Server immediately returns an I/O exception to the client.
When you install the Integration Server, Maximum Redirects is set to 5. You will need to increase this value if the targets that you access typically redirect their requests more than this. (This may happen if the target operates in a clustered environment.)
Timeout
Specifies the length of time the server waits for a response from a target server. If the Integration Server does not receive a response in the allotted time, it retries the request up to the number of times specified by the Retries parameter. When the allowed number of retries is exceeded, the server returns an exception.
When you install the Integration Server, the Timeout parameter is set to 300 seconds (5 minutes). To set Integration Server to wait indefinitely for a response from the target server, set this parameter to 0.
Important:
If you set the Timeout parameter to 0 and the target server does not respond to the request, the Integration Server making the request cannot process new requests due to thread pool exhaustion.
You can also specify number of seconds the server waits for an HTTP request to be fulfilled using the watt.net.timeout server configuration parameter. For more information, see Server Configuration Parameters.
Retries
Specifies the number of times the server reissues a request that has timed out (i.e., one from which it did not receive a response within the time period specified by the Timeout parameter).
When you install the Integration Server, Retries is set to 0. This means that the server automatically returns an exception if it does not get a response within the allotted time. Set Retries to a value greater than 0 if you want the server to retry (reissue) timed-out requests. The server will retry the request the number of times you specify.
Make sure that your developers know the Retries value that your server uses. If they need to use a different value, they can explicitly assign a Retries value to their service.