Configure and tune HTTP ports and some general
- In the left navigation pane, select Configuration.
- In the right administration pane, click the Web Container tab.
- Configure the following web server properties, as required:
- Max form content size – amount of data that can post back
from a browser or other client to the server. The default is 10000000 bytes, with
a maximum of 100000000 bytes.
- Perform server side
compression – enables HTTP compression in a production environment when client
demand becomes high and affects server performance for ODP applications.
Note If you enable server compression, notify developers that client
behavior must accommodate compression: namely, the client needs to use the
Encoding parameter for HTTP headers and set the value to GZIP Information is
available on the Internet if more information is required. See ODPRequest class in Developer Guide: OData SDK.
- To create a new HTTP/HTTPS port, click New.
- Configure the port properties, as required:
- Port – port number where the server listens for
- Status – whether the port is enabled.
- Protocol – communication protocol. When Protocol is set to https, the Security Profile drop down is displayed to allow
selection of a security profile.
- Maximum threads – maximum number of active threads that the
server allows for this listener. This value must be less than or equal to the
allowed number of connections.
- Statistics on – enables statistics collection on connections.
- Maximum idle time – the length of time, in seconds, that a
socket is idle before it disconnects.
- So linger time(s) – the length of time, in seconds, that a
socket lingers before it disconnects to enable a graceful shutdown.
Acceptors number – number of acceptor threads to be run.
Do not set this number too high. Use the following method to
determine the recommended number: Math.max(1,
(<<processesCount> or <coresCount>+3)/4).
- Acceptor priority – priority of the acceptor threads relative
to the other threads. The priority is adjusted by the value you enter here (the
default 0) to either favor the acceptance of new threads and newly active
connections, or to favor the handling of already dispatched connections.
- Response buffer size (k) – size of the content buffer for
sending responses. These buffers are used only for active connections that are
sending responses with bodies that do not fit within the header buffer.
- Request buffer size (k) – size of the content buffer for
receiving requests. These buffers are used only for active connections that have
requests with bodies that do not fit within the header buffer.
- Header buffer size (k) – size of the buffer to be used for
request and response headers. An idle connection has a maximum of one buffer of
this size allocated.
- Listen backlog – maximum backlog for incoming
- Low resources connections – number of connections, which if
exceeded, places this connector in a low resources state. This is not an exact
measure, as the connection count is averaged over the select sets. When in a low
resources state, different idle timeouts can apply on connections as specified in
the low resources maximum idle time property.
- Low resources maximum idle time(s) – period, in milliseconds,
that a connection is allowed to be idle when there are more connections than the
number set for the low resources connections property. This allows the server to
rapidly close idle connections to gracefully handle high load situations.
- Include server info in session – includes the server's IP
address and port in the HTTP session ID. This is required when using the Web
redirectors for load balancing to ensure sticky sessions.
- Click OK.
- Click Save.