Integration Server 10.7 | Integration Server Administrator's Guide | Configuring Ports | Designating an HTTP/S Port as Stateless
 
Designating an HTTP/S Port as Stateless
Integration Server now provides the ability to make Integration ServerHTTP and HTTPS ports stateless. A stateless port will not provide or maintain any sessions or session IDs for requests received by the port. This might be useful when using multiple non-clustered Integration Servers with a load balancer (this configuration is sometimes referred to as a stateless cluster).
Use the server configuration parameter watt.server.portStateless to specify a comma-separated list of the port numbers for the ports on Integration Server that are stateless. For example:
watt.server.portStateless=8443
watt.server.portStateless=8443,8081
You can configure any HTTP or HTTPS port on Integration Server to be stateless with the exception of the primary port and the diagnostic port. Additionally, do not configure any ports used for WebSockets or for administering Integration Server to be stateless. If you specify the primary port, diagnostic port, a port that is not an HTTP or HTTPS port, or a port that does not exist in the value for watt.server.portStateless. Integration Server logs an warning message stating that the port cannot be made stateless and that it will be skipped.