|Sessions to autostart
||For environments where it is desirable to have a certain number of host connections "live" following startup, you can use the setting to control the number of sessions automatically started.
|Session group definitions
||Defines up to 10 host connections to either SNA or TN3270 hosts. You can only define as many connections as you have licenses for concurrent users.
Note: if you change your host configuration here, you will want to synchronize access by modifying the defined links in the GLOBAL.STML file's TESECTION HOME.
|User Session Timeout
||When all your defined sessions are "busy" (in-use), the timeout value is used to "knock-off" any user that has been idle for the number of minutes specified.
|Console Port Number
||Use this setting to change the HTTP Port that the Administration and Development pages are served from.
|Console User Security
||Provides a dialog to set machine address-based security or userid/password security for the administration and development port.
|Terminal Emulation Port Number
||Use this setting to change the HTTP port that the web gateway (user) pages are served from.
||By entering a filename in this entry field, you activate logging of the buffers received and sent by Screensurfer to a selected host session (see following setting). The actual file name created will be a combination of the file name specified here and the session ID being logged.
|Session ID to Log
||Enter a 0 to turn-off logging or a session ID to activate logging on.
|Clear Logfile on Submit
||A checkbox: when checked, the active logfile and sessionID will be cleared. Note that if the SessionID setting is "*", Screensurfer will enumerate through all defined sessions, deleting any files matching the name and sessionID.
|Catch Program Exceptions
||To provide a more robust production environment, Screensurfer implements exception catching which surrounds all template execution. If an internal Screensurfer exception occurs, the Screensurfer exception handler will terminate the current terminal HTTP request thread without affecting operations.
During testing and development, leave this unchecked, so that proper exception reporting can assist in resolving errors.