Installation guide

6.7.4.2 - Terminal Emulator Settings
Setting Description
Status Window Displays the time-stamped status messages.
Connect Connects to ShareScan using the server name and port configured in the configuration
dialog.
Note: This button is disabled once a connection has been established.
End Only enabled once a connection has been established as disconnects from the TCP
server.
Clear Clears all text in the status window.
Keep connection alive When checked, the TCP connection between the Emulator and Server is kept alive. If
not checked, it terminates the TCP connection after the logon packet is sent to server
and no timer or pulsing events occurs.
Original XML Format When checked, the original XML format is used.
Top Most When checked, the emulator is always displayed on top of any window. When
unchecked, the emulator retains its normal order.
Seconds left until lock Displays a running countdown in seconds until the emulator times out. When the
emulator times out, it disconnects from the TCP server. Maximum timeout is 120
seconds.
Config Enables the configuration dialog.
NetStat Enables a command prompt window that runs the netstat –a –p TCP command .
Exit Closes the application.
6.7.5 - Session Logon service
The Session Logon service is located on the Configure Services tab under the Device Services section.
The Session Logon service provides secure access to the application and avoids prompting you multiple
times for credentials; that is, it provides a single sign-on for ShareScan.
Session Logon is provided as a single point of authentication for the entire workflow. If Session Logon is
configured and enabled for a device, you need to log on only once into ShareScan. The logon information is
effective for the entire session. You do not have to enter your logon information each time you select a
connector during the current session. The ShareScan Manager passes the logon information to the Connector
using an internal interface called "Credentials" in Data Publishing.
Note:
If you need to access different servers, and the logon credentials are not the same on those servers, the system
prompts you to enter logon information, even when Session Logon is enabled.