TCP/IP connection
TCP/IP connections are used between the Strategy Web XML API and Strategy Intelligence Server to pass requests to and retrieve the responses from the Strategy Intelligence Server.
Connection pool
When Strategy Web connects to a Strategy Intelligence Server node, either manually or automatically, the Strategy Web XML API establishes a connection pool with each Intelligence Server node. The connection pool consists of a number of TCP/IP connections equivalent to the number specified in the "Initial pool size" property in the Administrator page.
Connection status
When a user request comes in, the Strategy Web XML API gets a free connection in the connection pool to serve the request. All connections in the connection pool are initially in free status. When in use for processing a user request, they are set to busy status. Once a response for the request has been completed, the connection is returned to the connection pool in free status.
Connection pool growth
When the Strategy Web XML API detects that the number of free connections in a connection pool is less than two and the connection pool has not reached the maximum pool size, it dynamically expands the connection pool.
In the event the connection pool reaches the maximum pool size, as when a user request comes in when all connections are busy, the request waits for a free connection. The wait time is configurable through the Administrator page, by using the "Server busy timeout" property. If this time is reached and no connections are available, a "Server too busy" error is returned to the client browser.
Connection termination
It is the responsibility of the client (in this case the Strategy Web XML API) to properly terminate the connections with Strategy Intelligence Server. Proper termination involves the close-connection three-way handshake that terminates the connection on both ends. In Strategy Web, this is accomplished by disconnecting the Intelligence Server from the Strategy Web Administrator page.
