Notes: The Remote Sessions
page is available for assets running Axeda® Gateway, Axeda® Connector,
and Axeda® Agent Embedded Agents
as well as Axeda® IDM Agents.
For assets running these agents, you can run and view the history of the
remote session types listed in this page. Refer
to Creating
a TotalAccess Session
for more information about running remote sessions with assets running
IDM Agents.
You must be defined in a user group with security privileges to
this page to start remote sessions on assets.
This page shows a "No items found" message if this asset's agent
was not configured to support any remote sessions.
As with other tools in Axeda® Connected Product Management Applications,
your
Platform administrator can configure Remote Session operations and behaviors,
such as timeout lengths and so forth. If you have questions about the
Remote Session operations, contact your Platform's administrator.
Important: If the asset is muted, you will be not able to view this page. This page will be available again once the asset is unmuted.
The Remote Sessions page for an asset provides tools for starting Remote Sessions on deployed assets configured with support for those sessions. To view the types of remote sessions you can view and manage from this page click here.
This page shows the following information for all remote sessions configured for this asset:
Type - identifies the type of remote session.
Name - as defined for the related agent. For example, this field may specify the name of the interface to which you can connect a remote session. For the selected asset, the Remote Sessions table shows all types of remote sessions configured for that asset.
Description - optional text describing this type of remote access session (defined in the project that the Axeda Agent is running) or this connection type (defined using the Create/Edit TotalAccess Connection Types page for assets running Axeda IDM Agents).
Active Users - shows
the login name of the user who created the session.
For Remote Terminal sessions: if this is not an exclusive
session, shows a [join]
link for other users to join the session.
For Remote Application sessions: shows all users actively connected
to the related remote access session; multiple users can connect to
a single session, and those will all appear in the same row of the
Active Users column.
Actions - shows the Run
link for starting a remote session of this type with this asset. Also
shows the History link for
viewing Session History for all
types of sessions. For Remote Terminal sessions only, shows the Join link for active, non-exclusive
sessions and the View Log
link for viewing the log created during a Telnet session.
The Session History page lists all connections created for the selected
remote session, whether active, not active, not connected, or otherwise.
The Session History page also
shows whether the user is a Partner Access user or an internal user
(that is, a user who logged in with a valid Axeda® Connected Product Management Applications
user name and password).
Authorized users can view and delete remote sessions using the Administration application's View and remove remote sessions page or View TotalAccess Sessions page.
From the Remote Sessions page for an asset, you can start remote sessions and join remote terminal sessions. Depending on the type of session, refer to the appropriate topic for detailed instructions:
For assets running Axeda IDM Agents, refer to Creating a TotalAccess Session.
For assets running Axeda Gateway, Axeda Connector, or Axeda Agent Embedded, refer to one of the following topics:
In addition, you can select to view a history of session activity for a remote session in either of two ways:.
Locate the desired remote session in the table, and then, under Actions, click History. The Session History page appears.
In the Session History page you can also select to view a log of asset responses received during a remote terminal session.
o If you are using one or more Axeda® Global Access Servers (GAS server) for remote sessions and your IT department requires that only one URL be used for remote sessions, you can assign a GAS server to an asset by clicking the Assign Servers link in the Remote Sessions module of the Asset dashboard. Refer to Assigning remote servers to an asset for details. Similarly, you can assign assets to a particular GAS server from the Administration application. Refer to Assigning assets to a remote (GAS) server for details.
o As
of the Summer '11, Upgrade 2, release, the Application Bridge supports
a range of port numbers for Remote Application sessions that require a
range of ports (for example, an application that uses dynamic ports).
ALL of the ports in the range must be available for the application on
the asset for the remote session to succeed. If any of the ports are in
use by another application, the Application Bridge ends the session.
In addition, iIf you use the <$HOST> variable in the Model
Remote Interface definition and want to use a range of ports for a
Remote Application type of session, make sure that you have cleared the
Java Plug-in cache. Refer to the topic, Clearing
the Java_Plug-in_Cache.
o Use the navigation path to return to a previous page.
o Refer to the tables of Axeda® Service application, Remote Session error messages and possible solutions if you are having trouble starting or running sessions.