About Axeda Access

Axeda Access is a Web-based technology that enables one or more operators to securely view and operate the same remote desktop, through the Internet. Axeda Access includes a server component that is installed on the remote computer, a client that runs on the local computer, and the Axeda Access Application. The Axeda® Service application also includes some of this functionality, as described later in this topic.

Computers with an Axeda desktop-sharing server installed can allow the users at computers with an Axeda desktop-sharing client installed to view and operate their user interfaces. All data passed between the computers is made secure with data encryption. When a desktop is shared, the client operator can perform the same types of actions (security permitting) as the local operator. Using Axeda® Access Viewer, service technicians and support personnel can troubleshoot problems on the Axeda® Access Remote server computer; upload or download files between the computers; and run applications. Multiple client operators can share to the desktop of the same server computer, enabling collaboration in diagnosing customer problems.

There are three ways to connect the computers for desktop sharing. Click the titles below to display the details. Click the title again to hide the details.

Through the Axeda Access application

For desktop sharing through the Access application, you use the Request Session ID link to generate a shared session ID. Then, you connect the client computer to that session ID, and the operator at the server computer connects it to the same session ID. If the server application is configured with a password, you will need to type that password to connect to the session.

Through the Axeda Service application (Remote Sessions page or module on the Asset dashboard)

For desktop sharing through the Axeda Service application, you create a virtual tunnel or socket between the client and server computers. An Axeda® Connected Product Management Applications Agent or a Axeda® IDM Agent can be installed on the server computer, and the desktop sharing server must be running. For Axeda Gateway and Axeda Connector agents and Axeda Desktop Server, both the agent and the desktop server should be running.

When you define the project for an Axeda Gateway or Axeda Connector agent, you select the Desktop type of remote session for communication through an Axeda Application Bridge. This type of desktop sharing does not require an operator at the server computer to permit the session. If the server computer is configured with Policy Server support, then the ability to start a remote session on the asset is subject to the security defined for the Axeda® Policy Server.

To request a desktop sharing session through Axeda Service, use the Asset dashboard Remote Sessions module to run the configured Desktop remote application configuration. If the session is allowed, you connect the Access Viewer computer to the session. If the Access Remote application is configured with a password, you will need to type that password to connect to the session. Additional requirements for this type of desktop sharing are as follows: the Access Remote computer must be configured to accept direct LAN connections; the Axeda Agent running on the asset must be configured with support for Remote Application sessions to its desktop; you must have privileges to the asset and the Service application.

Through a direct LAN connection

For desktop sharing through a direct LAN connection, both the Axeda desktop-sharing client and server computers must be on the same local network. No session ID is required. The server computer must be configured to allow connections through a direct LAN connection, and the server application must be running; a local operator is not needed to connect to or allow the session. You use Access Viewer or Desktop Viewer to connect to the remote desktop. If the server application is configured with a password, you will need to type that password to connect to the desktop.

When the desktop sharing is through the Access or Service application, the Axeda® Enterprise Server enables and coordinates the communication between the computers, including computers behind firewalls and connections through proxy servers. Because the Enterprise Server is Firewall-Friendly , IT departments do not need to assign external IP addresses, reconfigure firewalls, or install direct telephone lines. The Enterprise Server authenticates users and manages sessions, making administration secure, centralized, and easy.

Using the Axeda® Configuration application, you can define an Execute an application type of action that starts Access Remote on an asset that is running an Axeda Gateway or Axeda Connector agent and connects to a specific session ID. For information about the arguments you can use with that type of action, see Arguments for Access Remote program.

For more information about the Access Remote, Access Viewer, Desktop Server, and Desktop Viewer applications, and about the types of actions that operators can perform during shared sessions, refer to the PDF user guides available with your Axeda software or from the Axeda Web site, http://help.axeda.com.

Notes:

As of version 5.2 of Axeda® Connected Product Management Applications, the client/server software that supports remote desktop connections through the Axeda® Service application is comprised of Axeda® Desktop Viewer (client) and Axeda® Desktop Server (server). While Axeda Service also supports the Axeda® Access Viewer (client) and Axeda® Access Remote (server) applications for remote sessions, Axeda Access supports only Axeda Access Viewer and Access Remote server software for remote desktop connections.

Axeda Access does NOT support large file transfers (over 2MB). For other options, refer to Ways to Transfer Files to and from Assets.

The Axeda® IDM Agents do not support the Axeda Access Viewer and Axeda Access Remote Server for remote desktop connections. Similarly, the Access Application does not support remote session capabilities of the IDM Agents. Instead, remote sessions with assets running IDM Agents are handled by the TotalAccess server. The TotalAccess server is separate from and does not communicate directly with the Enterprise Server. However, you can configure remote session information for models running IDM Agents through the Model Remote Interface page of the Axeda® Configuration application and view session information through the Axeda® Administration application (Remote Access menu).. Refer to the TotalAccess documentation for details about the server, its installation, configuration, and operation. Refer to Axeda IDM Agents for information about remote sessions with assets running these agents.

About Axeda® Access

Through the Axeda Access application

Through the Axeda Service application (Remote Sessions page or module on the Asset dashboard)

Through a direct LAN connection