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
PuTTY or
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.
You should now be logged into 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.
- Open up another command-line window.
- Start the RLI by enterring: java -jar RLI.jar
- At this point, we just want to see if the RLI will talk to
the Central Resource Daemon.
So, this step will result in an error message but hopefully
the one we expect.
Add one host by selecting in the RLI:
Topology => Add host.
- Request ONL to commit resources by selecting:
File => Commit
One of three things will happen:
- You will get a prompt for you password.
Enter your password and select Enter.
You should get a Commit Error message
saying Reservation Not Found.
This is OK at this point since it indicates
that you were able to communicate with the Central
Resource Daemon.
Select OK.
A Make Reservation dialogue box will appear.
Select Cancel, and exit the RLI by selecting
File => Exit.
- You get a dialogue box that contains the error message
Unable to connect: couldn't get I/O for 127.0.0.1.
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).
- 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.
Revised Dec 5, 2005