Understanding Request Timeouts in IFS Integration

When working with integration requests, it's essential to understand the various timeout parameters available to ensure efficient communication between systems. In this article, we will explore the different timeout values used in IFS Integration and how they can be overridden for specific requests.

The first set of timeout parameters includes `IFS_INTEGRATION_STATEMENT_TIMEOUT`, `IFS_INTEGRATION_MAX_QUERY_TIMEOUT`, and `IFS_INTEGRATION_QUERY_TIMEOUT`. These parameters define general integration timeouts for various types of requests, including data retrieval and modification. The default values for these parameters are 30 minutes, but they can be overridden using the wait property of the HTTP preference header.

In Batch Requests, individual requests (parts) are executed with a timeout value determined by `IFS_STATEMENT_TIMEOUT`. If the request is a data retrieval request, the wait preference must be less than `IFS_MAX_QUERY_TIMEOUT`, or the default value will be used. Similarly, for data modifying requests, the wait preference must be less than `IFS_STATEMENT_TIMEOUT`, or the default value will be used.

Another set of timeout parameters includes `IFS_STATEMENT_TIMEOUT`, `IFS_MAX_QUERY_TIMEOUT`, and `IFS_QUERY_TIMEOUT`. These parameters define general timeouts for various types of requests, including data retrieval. The default values for these parameters are 15 minutes, but they can also be overridden using the wait property of the HTTP preference header.

In addition to these timeout parameters, there is also a concept of connection timeouts. A connection timeout is the maximum amount of time that the program is willing to wait to establish a connection to another process. This value can be set in milliseconds and ensures that the system doesn't waste resources waiting for a connection that may never be established.

Socket timeouts are also an important aspect of request timeouts. Socket timeouts refer to the timeout when waiting for individual packets to be received. This value can also be set in milliseconds and helps prevent the system from waiting indefinitely for packets that may not arrive.

In some cases, setting the timeout on the `req` object may not be sufficient. For example, when uploading large files, it's essential to allow the client to continue sending data for an extended period. In such cases, overriding the request timeout value for a specific endpoint can ensure efficient communication and prevent timeouts.

In conclusion, understanding the various timeout parameters available in IFS Integration is crucial for ensuring efficient and reliable communication between systems. By knowing how to override these values for specific requests, developers can fine-tune their integration requests to meet the unique requirements of their application.

Request time out