OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Configuring WebSpeed Messengers <strong>and</strong> WebSpeed Transaction Servers<br />
7–6<br />
Table 7–3: WebSpeed Messenger Logging Setting properties (2 of 2)<br />
Property Description<br />
Maximum number of log files The number of rolled-over log files to keep. The value<br />
can be 0 or a value between 2 <strong>and</strong> 999999, where 0<br />
means there is no limit on the number of server log files<br />
to keep. The specified number represents the maximum<br />
total number of log files to keep on disk at any time,<br />
including the current log file being written to.<br />
When the file becomes equal to or greater than the Log<br />
file threshold size, the client process renames it <strong>and</strong><br />
creates a new log file. The file is renamed as follows,<br />
where ###### is a number starting at 000001 <strong>and</strong><br />
increasing to 999999, after which it rolls back over to<br />
000001:<br />
filename.######.extension<br />
Table 7–4: WebSpeed Messenger SSL properties<br />
Property Description<br />
Enable SSL client connections If checked, this property directs that the connection to<br />
the WebSpeed Transaction Server use SSL tunneling.<br />
Disable client verification of<br />
SSL host name<br />
If checked, this property turns off host verification for<br />
an SSL connection. If cleared, the client compares the<br />
host name for the WebSpeed Transaction Server<br />
specified by Host Name (or as returned by any<br />
Controlling NameServer) with the Common Name<br />
specified in the server digital certificate, <strong>and</strong> raises an<br />
error if they do not match. With this parameter<br />
specified, the client never raises the error.<br />
Disable SSL session reuse If this property is checked, the connection does not reuse<br />
the SSL session ID when reconnecting to the same<br />
WebSpeed Transaction Server.<br />
Disable SSL session caching Disables session caching. (Session caching allows a<br />
client to reuse a previously established session if it<br />
reconnects prior to the session cache timeout expiring.)<br />
SSL session cache timeout Specifies in seconds the length of time an SSL session<br />
will be held in the session cache.<br />
The default is 180 seconds.