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 Browser 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 name shown in the Remote Sessions table, under Actions click Run. The Remote Session window opens. Need help troubleshooting browser problems?
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. 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.
3. Click Start Session.
4. Click
Open Remote Web Site.
Waiting
for connection
The Remote
Session description window opens. This window accepts and displays
standard Telnet commands passed to and from the asset. 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 Platform 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.
Asset-side authentication required
If the asset owner requires
additional authentication, a message indicating the session cannot be
started is shown. If this message appears, do the following:
a. Type your user name and password for the authentication server for that asset.
b. Click
Login. The
agent running on the asset passes your credentials to the local authentication
server. When the asset next connects to the Platform, the session should
be connected. You may be prompted to type your credentials a second time.
Connected
When the asset next contacts
the Platform, the session is connected and the window shows the message
"Connected."
5. In the displayed window, type the user name and password for connecting to this remote application session and click Log in (if prompted). A security-warning window will appear. Trust the context, and agree to install and run the Axeda Application Bridge.
Notes: 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
version 1.4.1 or later of the Java Plug-in. See the Troubleshooting
topic for more information.
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.
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.
6. Click the Open Remote Web Browser link to open a new window to the remote web server. Note that if the Remote web server is configured to be a Secure web server, or run on a port other than the standard HTTP port (80), you may have to adjust the Address in the new browser window to reflect the proper transport (HTTP/HTTPS) and port number.