3.0 Server Settings

The Server Settings panel opens when you log on to the Terminal ID Manager Console.

Use this panel to configure your preferences for monitoring your terminal IDs.

3.1 Server status

Note the Server database status in the top colored band, and what it means:

Server database available (green)

The Enable client requests box is checked, and Terminal ID Manager server is ready to be configured or used in sessions.
Server database not yet configured (red)

The server database has not yet been populated with data.

HINT:If you see this message, follow the steps to Set up the Database.
Server database unavailable (red)

The server database is not functioning or cannot be accessed.

To troubleshoot, check the Terminal ID Manager log files, idevent.log and trace.log, located in <MSSData>/idm/log. You may need to review how you Set up the Database.
Client requests disabled (orange)

The Enable client requests box is cleared, and the database is available.

3.2 Server management

Enable client requests

Check this box if you want to process Terminal ID Manager requests from the client whenever the database is available.

Click Apply. If the database is available, the status changes to green: Server database available.

3.3 Server ID management

Review the server default values and change, as needed.

3.3.1 Heartbeat interval

Set the frequency (in minutes) that a client is expected to send a regular heartbeat message to the server. The message conveys that the ID is still in use by the client.

This value applies to all pools unless the value is explicitly overridden for an individual pool in the Pools configuration.

3.3.2 Communication timeout interval

Set the number of minutes that must elapse without communication with an allocated session for an ID to be classified as timed out.

This value applies to all pools unless the value is explicitly overridden for an individual pool in the Pools configuration.

3.3.3 Reclaim timed-out IDs automatically

Specify the number of minutes before automatically reclaiming an ID that has been flagged as timed-out.

3.4 Logging and tracing

Select the log levels as needed. Keep in mind that performance may be affected when more information is logged.

3.4.1 audit.log

The audit.log records administrator actions, such as changing settings.

Log level options:

Log errors and informational messages
Log errors
Disable logging

3.4.2 idevent.log

The idevent.log file contains details about ID event activity, such as clients requesting IDs.

Log level options:

Log errors and informational messages
Log errors
Disable logging.

3.4.3 trace.log

The trace.log is frequently used when analyzing server problems. The trace.log file is located in the log folder within the MSSData folder. Your Technical Support representative may request that this setting be changed to include debug information.

Log level options:

Log errors, warnings, informational, and debug messages
Log errors, warnings, and informational messages
Log errors and warnings

3.5 Change administrative password

The Terminal ID Manager server Administrator password permits access to the Terminal ID Manager Console where the server settings are configured.

To change the current password (set during installation), enter the new password, and then enter it again to confirm it. Characters appear as dots.

Next step: When the server preferences are set, continue with the configuration to Monitor IDs.