HTTP Connector
The HTTP Connector resource template represents an incoming HTTP connection. HTTP connectors are used by a service's SOAP binding and also by the WebApp component.
General
| Property | Required? | Editable? | Accepts SVars? | Description |
|---|---|---|---|---|
| Machine Name | Y | Y | Y | The name of the machine that accepts the
incoming requests. For machines that have only one network card, the default
value, localhost, specifies the current machine. For machines that have more
than one network card, this field specifies the host name of the card that will
be used to accept incoming HTTP requests.
If there is more than one network card on the machine, and you specify 0.0.0.0 in this field, all network cards on the machine will listen for incoming HTTP requests on the specified port. Only one HTTP connector can be started on each port. Therefore make certain that all HTTP connection resources that use the same machine name specify different port numbers. Default: 0.0.0.0. Note that machine name signifies the machine on which the node is running, not the machine on which the Administrator server is running. |
| Port | Y | Y | Y | The port number on which to listen for
incoming requests.
Note: Once you install an HTTP connector resource instance the
port is bound to the connector even if there are no applications using the
connector. You should uninstall unused instances to conserve ports.
Default: 9895. |
| Accept Queue Size | N | Y | Y | The number of incoming requests that can be
queued before additional requests are rejected.
Default: 0, which indicates that the JVM should use the default value for accept queue size. For Oracle JVM, the default value is 50. |
| Acceptor Threads | N | Y | Y | The number of threads dedicated to
processing incoming connection requests. Ideally, you want to have enough
acceptor threads so that there is always one available when a user needs one,
but few enough so that they do not provide too much of a burden on the system.
The threads are started when the HTTP Connector resource instance is installed
on a node.
An acceptor thread accepts the connection, then queues the request to the worker thread pool and returns to process the next connection request. In general, the number of acceptor threads should be kept low. A good rule of thumb is the number of acceptor threads should not be greater than twice the number of processors. Default: 1 and grey. |
SSL
| GUI Property | Required? | Editable? | Accepts SVars? | Description |
|---|---|---|---|---|
| Enable SSL | N | N | N | Indicate that SSL connections should be
enabled. When checked, the SSL Certificate Source field is enabled.
Default: Unchecked. |
| SSL Certificate Source | N | Y | N | The source of the SSL certificate: |
| SSL Server Provider | N | Y | Y | The name of an SSL Server Provider resource instance. |
Advanced
| GUI Property | Required? | Editable? | Accepts SVars? | Description |
|---|---|---|---|---|
| Header Buffer Size (B) | N | Y | Y | The size of the buffer available for the
HTTP header.
Default: 4096. |
| Request Buffer Size (B) | N | Y | Y | The size of the buffer available for the
HTTP request.
Default: 8192. |
| Response Buffer Size (B) | N | Y | Y | The size of the buffer available for the
HTTP response.
Default: 24576. |
| Low Resources Max Idle Time (ms) | N | Y | Y | The period that a connection is allowed to
be idle when there are more than (the number of) Low Resources Connections.
Default: -1. There is no timeout. |
| Max Idle Time (ms) | N | Y | Y | The maximum idle time for a connection. The
maximum idle time is applied when:
Default: 200000 ms. |
| Linger Time (ms) | N | Y | Y | The time to delay before a socket resets.
Before a socket terminates a connection, it can linger, allowing unsent data to
be transmitted or it can reset, which means that all unsent data will be lost.
Default: -1. There is no delay before resetting. |
| Use Non-Blocking IO Sockets | N | N | N | Indicate whether to use non-blocking or
blocking IO. In non-blocking IO, the thread will read whatever data is
available and return to perform other tasks. In blocking IO, the thread will
block on a read operation until all the data is available.
Default: Checked. |
| Use Direct Buffers | N | N | N | Indicate whether to use
direct buffers with non-blocking IO. Some
JVMs have memory management issues with direct buffers.
Default: Checked. |
| Worker Thread Pool | N | Y | Y | The name of a
Thread Pool resource
instance containing the threads used to handle the HTTP request.
Default: None. |