Starting the Remote Control

The Remote Control GUI tool enables administrators to connect to remote server systems and manage the server processes running. The Remote Control communicates with Server Managers using XML-RPC commands over HTTP. That means that any other XML-RPC client may be used to control Server Managers, too.

Starting the Remote Control requires an OODT software installation as well as a display capable of showing a graphic user interface. If you've not yet installed the OODT software on your desktop system, do so now. Otherwise, run the Remote Control from a local server installation and display it to your desktop (on systems that support remote displays).

Additionally, you will need to know the installation directory of your OODT software. This is usually something like /usr/local/edrn , c:\Program Files\EDRN , /usr/local/pds , or c:\Program Files\PDS . Check your installation for details.

A subdirectory of the installation directory, lib , contains the jar files necessary to run the Remote Control.

Here is an example of starting the Remote Control on a Windows instalation of the EDRN software:

      
     C:\
   
     >
   
    
      
     java -Djava.ext.dirs="C:\Program Files\EDRN\lib" jpl.eda.gui.ManagerImpl
   
    
   
    

On Windows, you can use fo rward slashes, / , or backslashes \ , to identify the path.

Note: If the installation directory path contains spaces, as in the above example, you must quote the argument, otherwise the command will be launched incorrectly.

Here is an example of starting the Remote Control on a Linux installation of the PDS software:

      
     bash$ 
   
    
      
     java -Djava.ext.dirs=/usr/local/pds/lib jpl.eda.gui.ManagerImpl
   
    
   
    

Startup Options

You can use command line arguments to start the Remote Control in certain ways. One such use is to have the GUI start up with a Server Manager already in its connection list. To do so, add three command-line arguments:

1. The URL of the Server Manager
2. The user name to use on it
3. The password that authenticates the user name

Caution: On some systems, command line arguments, including the password, are visible to other users or may be stored in command history files. Use this command only on systems which you control completely.

Instead of entering the URL, user name, and password to a single server, you can pass the -restore option on the command line. This instructs the Remote Control to restore all connections previously saved using the GUI's Manager > Save current connections menu item.

Making a Shortcut

Entering the command to start the Remote Control will grow tiresome quickly, so we recommend you create a shortcut to the command so you can start the Remote Control quickly.

Unix users should create either an alias or shell script.