The options available on the Advanced tab are used when creating sockets for
connecting to the Remote Host. Default values are provided for all fields, which should only be
modified under advice from the
Oracle Support Team.
You can configure the following configuration options on the Advanced tab:
Active Timeout:
When the Enterprise Gateway receives a large HTTP request, it reads the request off the network
when it becomes available. If the time between reading successive blocks of data exceeds
the Active Timeout, the Enterprise Gateway closes the connection. This prevents
a Remote Host from closing the connection while sending data. Defaults to 30000 milliseconds
(30 seconds). For example, the Remote Host's network connection is pulled out of the machine
while sending data to the Enterprise Gateway. When the Enterprise Gateway has read all the available data
off the network, it waits the Active Timeout period before closing the
connection.
Idle Timeout:
The Enterprise Gateway supports HTTP 1.1 persistent connections. The Idle Timeout
is the time that Enterprise Gateway waits after sending a message over a persistent connection to
the Remote Host before it closes the connection. Defaults to 15000 milliseconds (15 seconds).
Typically, the Remote Host tells the Enterprise Gateway that it wants to use a persistent connection.
The Enterprise Gateway acknowledges this, and keeps the connection open for a specified period of time
after sending the message to the host. If the connection is not reused by within the Idle
Timeout period, the Enterprise Gateway closes the connection.
Input Buffer Size:
The maximum amount of memory allocated to each request.
Output Buffer Size:
The maximum amount of memory allocated to each response.
Cache Addresses For:
The period of time to cache addressing information after it has
been received from the naming service (for example, DNS).
SSL Session Cache Size:
Specifies the size of the SSL session cache for connections to the remote host. This controls the
number of idle SSL sessions that can be kept in memory. You can use this setting to improve performance
because it caches the slowest part of establishing the SSL connection. A new connection does not
need to go through full authentication if it finds its target in the cache. Defaults to
32 . If there are more than 32 simultaneous SSL sessions, this does not prevent another
SSL connection from being established, but means that no more SSL sessions are cached. A cache size
of 0 means the cache size is unlimited.
At DEBUG level or higher, the Enterprise Gateway outputs trace when an entry goes
into the cache, for example:
DEBUG 09:09:12:953 [0d50] cache SSL session 11AA3894 to support.acme.com:443
If the cache is full, the output is as follows:
DEBUG 09:09:12:953 [0d50] enough cached SSL sessions 11AA3894 to support.acme.com:443
already
Input Encodings:
Click the browse button to specify the HTTP content encodings that the Enterprise Gateway can accept
from peers. The available content encodings include gzip and deflate .
By default, the content encodings configured the Default Settings are used.
You can override this setting at the Remote Host and HTTP interface levels. For more details,
see the topic on Compressed Content Encoding.
Output Encodings:
Click the browse button to specify the HTTP content encodings that the Enterprise Gateway can apply to
outgoing messages. The available content encodings include gzip and deflate .
By default, the content encodings configured the Default Settings are used. You
can override this setting at the Remote Host and HTTP interface levels. For more details, see the
topic on Compressed Content Encoding.
|