Important: If the asset is muted, you will be not be able to start any remote sessions Once the asset is unmuted, the ability to start remote session for this asset is restored.
You can start a Remote Application session in two ways:
o From the Asset dashboard, click the name of the session in the Remote Sessions module. When the Remote Session window appears, continue to step 2 in the following procedure.
o If the name of the session you want to start does not appear in the Remote Sessions module, click View All and use the following procedure.
1. For a remote session shown in the table with a type of Application, under Actions click Run. The Remote Session window opens.
2. Type a description for this session. This description is required; it is saved with the session and used to identify it in the Remote Sessions table and in Session History.
3. Click
Start Session. The Remote Session
window appears. This window displays the following text until a connection
is made: "Waiting for the asset to retrieve the Remote Session request."
If you want to cancel the session before it is connected, click Cancel Session. As indicated in
the window, the server updates the window with the latest information
every 5 seconds (by default).
If the session cannot be started for any reason
(for example, it is denied by Axeda Policy Server), a message
appears with the reason the session could not be started.
4. If the asset owner requires additional authentication (Agent-side Authentication), a message indicating the session cannot be started is shown. If this message appears, do the following:
In the displayed window, type the user name
and password for connecting to this remote application session, and click
Log in. What
happens next depends upon how the session was created and configured on
the Agent asset. There are two types of Remote Application access sessions:
automatic and manual (as configured from the Model
Remote Interfaces page of the Configuration application).
If this remote access session is configured for automatic connection, a security warning
window appears. Trust the content, and agree to install and run the Axeda
Application Bridge. The Remote Access Application applet window appears
with the name of the asset for this session, the Remote Application Name
(name of the selected session as defined in the Agent project), the current
session status, the configured communication ports, and a session ID created
by the Platform.
If this remote access session is configured for manual connection, the Remote Access Application
applet window appears showing the session ID created by the Platform,
the name of the asset for this session, and the name of the selected remote
application session (as defined in the Agent project).
5. Run the Application Bridge. If you do not have the Application Bridge installed on your machine, it can be downloaded from the "Click to download the Remote Application Bridge" link. When the Application Bridge is installed and started, the Remote Application Bridge window appears showing the current status of the session shows the status of the session (such as "Remote connection ready "), the asset communication ports defined for this session (configured in the Agent project), and the Session ID created by the Platform. Once the Application Bridge is running and configured with the session ID, the connection is complete and active.
Note: The Application Bridge applet will not run properly if your browser is using an incompatible Java Plug-in or a Java Plug-In is not found. You will need to install a compatible version of the Java Plug-in. See the Troubleshooting topic for more information.
6. Start your local application (this application will connect with the Platform side application), and if necessary configure it to use the communication port(s) listed in the Application Bridge window (the listening port for the bridge). You can connect to the remote server side application through the Application Bridge support.
Notes: 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, if 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.
In the Remote Access Application applet window, click End Session. (It is recommended that you do not manually stop the AppBridge.jar from the command prompt.)