The Remote Interface: <interface_name> page appears when you click Edit in the Actions column on the Model Remote Interfaces page. If you want to change the settings for automatically launching and closing remote desktop sessions or remote application sessions, you do so by editing the parameters displayed in this page. Variables are available for the Launch Command and Download Launcher From fields. For an example of configuring a remote application (PuTTY), click to show/hide it.
The following information for the selected remote interface cannot be changed:
o Remote Session Type - Desktop or Application
o Remote Session Name - Desktop (the name is the same for all remote desktop interfaces, whether you are using an Axeda viewer application or a third-party application). For Application interfaces, this field displays the name assigned to this Remote Application interface when the Agent project was configured using Axeda Builder.
You can change the following information for the remote interface:
o Launch Automatically - Select this check box if you want the Platform to launch this type of remote session automatically.
o Automatically Stop Session - Select this check box if you want the Platform to stop this type of remote session automatically.
o Launch Error Message - Type the message to display if the remote interface fails to launch.
o Download Launcher From - Type the
URL from which the remote interface application (an application or a desktop
viewer) can be downloaded. This URL should contain the path to the executable
file on the Axeda Platform. The Platform uses this path to download the
application to client computers.
If you do not know the Platform component of the URL, you can use the <$ENTERPRISE_HOST>
variable in this field so that the Platform finds the URL for the Platform
and substitutes that URL for the variable. Refer to Variables
for Quick Launch Configuration.
o Launch Command - Type the command that launches the remote interface (a desktop viewer or another application such as PuTTY). To specify the path, you have the following options:
§ Type an absolute path. If the path contains spaces, be sure to delimit the path using quotation marks (as in, "C:\Program Files\"). In addition, be sure to type the complete file name, including the extension. For example: C:\WINDOWS\system32\mstsc.exe /v:<$HOST>:<$PORT>
§ Use an environment variable to reference the path to the executable (see for details). If the path will contain spaces after the environment variable is expanded, delimit the variable using quotation marks.
§ Use the <$DOWNLOAD_TO> variable to retrieve the application-wide property value.
§ If the viewer executable can be found in the Platform path of the client machine, specify no path at all.
§ For applications that require multiple port numbers, the Platform supports %p1, $p2 %pn in the Launch Command field. %p1 is replaced by the first listening port, %p2 by the second available port, and so forth. The Platform also supports the use of a Java classpath (-cp or -classpath) in the arguments for the Launch Command (when specifying the Java versions of applications).
You can use the following variables with the Launch command (separate the variables with a space):
§ <$HOST> -- Hostname substitution. If you use this variable 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.
§ <$PORT> -- Port substitution.
§ <$AUTO> -- Full substitution.
§ <$ENV:env_var> -- Environment variable substitution.
§ <$DOWNLOAD_TO> -- Path substitution (Optional).
§ <$ENTERPRISE_HOST> -- Platform substitution (URL, optional)
For details about using these variables, including syntax information, and examples, refer to Variables for Quick Launch Configuration.
Important! When you enter values for the Launch Command and Download Launcher From fields, you are responsible for ensuring that those values work, whether or not you use the variables. The Launch Command field must reference an executable that can be invoked by the Application Bridge applet (either with a fully-qualified path to the executable or by finding the executable on the system path). The Download Launcher From field must be a correct URL, and the specified application executable must be available at that URL.
If remote desktop is enabled on an asset (in the configuration of the Axeda Agent) and you do not enter anything for the Launch Command or Download Launcher From fields, the Platform operates as if you had entered <$AUTO> for these fields. If you do not enter anything on this page at all, remote desktop still works by obtaining the automatic launch and download parameters, but remote sessions will not launch or close automatically (because no one has selected those options). For remote application sessions to invoke Quick Launch, you must configure them in this page.
To save your changes, click Save; to revert to the original settings, click Cancel.
Quick Launch -- refer to Quick Launch (Service application).
Starting remote desktop sessions -- refer to Service application - Remote Sessions - Starting a Remote Desktop session.
Downloading Axeda Desktop Viewer -- use the Axeda Service application, and refer to the topic, Download Desktop Viewer from Asset dashboard.
Axeda Desktop Viewer -- refer to the Axeda Desktop Viewer User's Guide.
Axeda Access Viewer -- refer to the Axeda Access Viewer User's Guide.