Getting Started

Follow these steps:

• Get the RLI jar file

You can do this by either following the Get RLI.jar Web link or by logging into any onl host and copying the file RLI.jar from ~onl/export/RLI.jar to your remote host.

• Install JRE (Java Run-time Environment) 1.4.2 (May not be necessary)
• First determine if you can avoid this step by seeing if you are already running JRE 1.4.2 or higher. Enter: java -version . If the response says that you are already running some version that is atleast 1.4.2, you can skip this step.
• If you need to install JRE 1.4.2, go to the Java download page http://java.sun.com/j2se/1.4.2/download.html and download the JRE for your platform by following the instructions posted at the Sun site.
• Verify that you can run an ssh client on your host
• If you know you have an ssh client, you can go on to the next step. Otherwise, continue ....
• Open up a command-line window and enter: ssh -V
  This should display the version number of your ssh. Furthermore, it should indicate that you are running version 2 and not the older version 1. If this fails, you see your system administrator or get an ssh client from the Web. Try Open SSH.
• Verify that you can run the RLI on your remote host
• Follow the instructions for setting up an ssh tunnel to the ONL Central Resource Daemon. See RLI SSH Tunneling.
• Open up a command-line window
• Start the RLI by enterring: java -jar RLI.jar
• Add one host by selecting in the RLI: Topology => Add host.
  We just want to see if the RLI will talk to the Central Resource Daemon. Do NOT try to add a cluster at this time.
• Request ONL to commit resources by selecting: File => Commit
  One of three things will happen:
  • The commit progress bar will show that something is happening and after about 3 minutes, all of the icons will "light up" indicating that the cluster has been allocated to you.
  • You will get an error message saying that there are no hosts available. This would be unusual but is OK since it indicates that you were able to communicate with the Central Resource Daemon.
  • You get a dialogue box that contains the error message heading Main ONL Connection Failed. This indicates that your ssh tunnel to the Central Resource Daemon is not working. If you can not fix the problem, send email to testbed-ops@onl.arl.wustl.edu for assistance. Include your phone number (just in case we have to contact you by phone).
• Verify that you can login to the host allocated above.
• Determine the actual hostname assigned to your host by right clicking the host icon.
• FIRST, ssh to onl03.arl.wustl.edu. Note that for now, onl03.arl.wustl.edu is the ONLY ONL host that you can access from outside of the testbed.
• SECOND, ssh from onl03 to the actual host. Note that you should be able to ssh to the actual host without password authentication.
• If all has been successful, release the host back to the testbed by selecting: File => Exit. If you encounter problems that you can not resolve, send email to testbed-ops@onl.arl.wustl.edu.

Congratulations!

Please note the following:

• If you want to change your password, you should do so through the web interface and not on the ONL hosts. Although there is nothing to stop you from changing your password by entering the passwd command while logged into one of the ONL hosts, your password on the hosts and your password in the database will be different.