The Session History page shows all activity for the remote session selected from the Remote Sessions page for the asset. If you selected a remote session to which connections have not yet been made, the table in this page shows "No items found."
The table shows the following information:
o Session Id - the number assigned to the session.
o Access Server - the server used to establish the session. If the Access server that is part of an Axeda Platform is used, this column shows "Internal;" otherwise it shows the name of the Axeda® Global Access server used.
o User Name - the login name of the user who connected to that remote session.
o User Type - whether the user is a Partner Access user ("Partner") or a Axeda® Connected Product Management Applications user ("Internal"). If the type is Partner, you can position the cursor over the word "Partner" to view the name of the company in a Tool Tip.
o Description - information entered by the user who created the session.
o Start - the date and time that the session was connected.
o End - the date and time when the session was disconnected.
From the Actions column of the table you can click links to perform actions such as ending a session, deleting a session, or viewing more information about the session.
From this page, you can view a log of the communications for a remote session and view details for the session. For a session that is still active, you can end the session from this page.
In the Actions column for a session, click View Log.
A new window opens with a log of session activity (comprised of the responses from the asset echoed to the Platform). This information is available only if the Platform is configured to save session log information and the Platform received asset responses during a session.
For a Telnet session, this audit log displays the complete log of the commands entered during the session.
The following messages may appear if the window does not display valid log information:
§ "Unable to display log file" - appears if there is no log file available for the selected session.
§ "No log file for session" - appears if there is no log file available for the selected session.
You can copy the log information and save it to your local computer.
§ To copy the information, use the browser's standard Copy and Paste tools.
§ To save the information to your computer, use the browser's standard File - Save tool.
In the Actions column for a session, click Details. The Audit Details window opens with an overview of the session.
In the Actions column for a session, click End. When prompted to confirm, click OK to end the session or Cancel to keep the session open.
o If you resize the Remote Terminal Applet window to view more data, you need to issue a command to the terminal server to notify it of the size change. Otherwise, the server terminal window will continue to show data within the confines of the original window size. To notify a Unix-based terminal server of a new window size, type the following in the Remote Access Terminal applet window: stty columns xx rows yy (replacing xx with the new x-axis position and yy with the new y-axis position.
o For Remote Application and Remote Browser sessions: If the ping rate is longer than the amount of time that the server is configured to attempt to create a session with that asset (indicated by the "Waiting to connect" message), then the session may terminate before it begins on the asset. You can check the ping rate in the Asset dashboard; and change that rate, if necessary, through a Set Ping Rate action. For example, if the Platform is set to attempt the session connection for 30 seconds, but the ping rate is set so that it will not contact the server for another 40 seconds, the remote session cannot be established.