Available for Models running Axeda Gateway, Axeda Connector, or Axeda Agent Embedded only
This page lists the remote interfaces for a selected model. It also provides access to the page where you can set up a new launch command for an Application or a Desktop type of remote session for the assets of the selected model. For existing remote interfaces, the Actions column provides an Edit link that allows you to edit the command. For details on setting up the launch command, refer to the topic, Editing Remote Interfaces.
Notes: To set up connection
types for models of assets, use the Model wizard, Model Connection Types
page.
For Remote Application sessions as of Summer '11 Release that use the <$HOST>
variable and a range of ports (so that the Application Bridge increments
if a port is not available), make sure that you have cleared
the Java Plug-in cache. Otherwise, the Application Bridge will not
increment port numbers.
For applications such as the Axeda® Deployment Utility, you can set up the application to launch automatically once the remote connection is established with the asset. You can then connect to the Axeda Agent to modify its configuration as needed.
For Desktop sessions, the default behavior for the system when a remote session is requested is to determine which desktop server is running on the asset (Axeda® Desktop Server or Axeda® Access Remote), then, if necessary, download the appropriate Axeda viewer, and launch the appropriate viewer for the server. This feature is referred to as Quick Launch.
If you want to use your own desktop viewer, this page enables you to specify the launch command for that viewer and its location on the Axeda® Platform (for downloading). No matter which viewer you are using, you can also specify whether remote desktop sessions should be launched automatically with the viewer and whether they should be stopped automatically.
Note: Any viewers that you want to make available for downloading through Quick Launch must be copied to the installation directory, ServiceLink_home/applications/stage/drm/downloads on the machine running the Platform. (This path assumes the Platform is running in the default clustered setup; if you are running a single server, then the files need to be copied to the ../drm/downloads directory of the bea_home/user_projects/applications/servicelink/ directory.)
The table on this page shows the following information for a configured application or desktop viewer:
o Interface Type - Application, Terminal, Browser, or Desktop (you cannot edit this field)
o Name - Except for "Desktop," this field displays the name assigned to the remote session in the project (using Axeda Builder). You cannot edit this field. For example, if the configure Remote Application is called, "Deployment Utility," in the project, that name is displayed here.
o Launch Command - The command that starts the application.
For example:
"<$ENV:programfiles>"\\Axeda\\Desktop\\Viewers\\AxedaDesktopViewer_v5226.exe
<$HOST>:<$PORT>
or for a remote application:
mstsc.exe /v:<$HOST>:<$PORT>
Note: The Launch command must contain the complete file name, including the extension.
o Launch Error Message - The message displayed if the application cannot be started.
o Launcher Download Location - The path to the executable on the Platform (from which the application can be downloaded). This field applies to remote desktop viewers only.
o Auto Launch - When this option is selected (Yes), the Platform launches remote sessions automatically using the specified application.
o Stop Session - When this option is selected (Yes), the Platform stops this type of remote session automatically.
To specify your own desktop viewer or to change the settings for a desktop viewer or an application, click Edit in the Actions column. The Remote Interface page appears.