CS 696 Emerging Technologies: Java Distributed Computing Spring Semester, 1999 Jini on Rohan |
||
---|---|---|
© 1999, All Rights Reserved, SDSU & Roger Whitney San Diego State University -- This page last updated 01-Apr-99 |
Jini on Rohan & Moria
Jini is installed on rohan.sdsu.edu and moria.sdsu.edu in /opt/jini1_0/. The Jini 1.0 jar files are located in /opt/jini1_0/lib/.
Jini Jar files
jini-core.jar |
outrigger-dl.jar |
space-examples.jar |
jini-examples-dl.jar |
outrigger.jar |
sun-util.jar |
jini-examples.jar |
pro.zip |
tools.jar |
jini-ext.jar |
reggie-dl.jar |
transient-outrigger.jar |
mahalo-dl.jar |
reggie.jar |
mahalo.jar |
space-examples-dl.jar |
|
|
Server
Side
|
Client
Side
|
Description |
jini-core.jar |
none |
Core
Jini platform interfaces and classes
|
jini-ext.jar |
none |
Jini
platform extension interfaces and classes
|
reggie.jar |
reggie-dl.jar |
Jini
Lookup service implementation
|
mahalo.jar |
mahalo-dl.jar |
Jini
Transaction implementation
|
outrigger.jar, transient-outrigger.jar |
outrigger-dl.jar
|
JavaSpaces
technology implementation
|
jini-examples.jar |
jini-examples-dl.jar
|
Lookup
Browser and Service GUI examples
|
space-examples.jar |
space-examples-dl.jar
|
JavaSpaces
technology examples
|
tools.jar
|
none |
ClassServer,
DepencyChecker, SerializationChecker
|
sun-util.jar
|
none
|
Development
utilities
|
pro.zip
|
none
|
ODI
classes needed by Outrigger
|
Standard Extensions
The following jar files are standard extensions to the JDK 1.2 on rohan and moria. This means you do not have to place them on your classpath to use any of the classes in these jar files.
jini-core.jar |
jini-ext.jar |
mahalo.jar
|
outrigger.jar |
reggie.jar |
sun-util.jar |
transient-outrigger.jar |
Running rmid, class server & reggie
In order to run reggie you need to be running rmid. If you want proxy classes downloaded to your client you need an http server. You can use the web server running on www-rohan. See http://www-rohan.sdsu.edu/hpguide.html for more information on using that web server. On rohan and moria you will not be able to run rmid or the http server on the standard ports. When you run reggie you need to provide the port numbers you are using for rmid and the http server.
rmid
rmid -port portnumber &
will start rmid
class server
The following will start the HTTP server on rohan running on port 8888. The default port is 8080
java -jar /opt/jini1_0/lib/tools.jar -port 8888 -dir /opt/jini1_0/lib/Options
[-port port] [-dir dir] [-trees] [-verbose]
-dir
reggie
You need to provide reggie a policy file, a log directory, and a code base for downloading client code. When you start reggie, it will pick a random port if the standard reggie port is not available. The only way to find the port used by reggie is to use mutlicast discovery, search for your reggie group, and print out its port. Once you have the service registrar for the lookup service, get the LookupLocator. It will give you the port of the lookup service. The general form to start reggie is:
java -jar <lookup-server-jarfile> <lookup-client-codebase> <lookup-policy-file> <output-log-dir> <lookup-service-group>
An example setting a non-standard port for rmid:
java –Djava.rmi.activation.port=5678 -jar /opt/jini1_0/lib/reggie.jar http://fargo.sdsu.edu:8888/reggie-dl.jar /opt/jini1_0/example/lookup/policy /tmp/reggie_log whitney.cs.sdsu.edu
Copyright ©, All rights reserved.
1999 SDSU & Roger Whitney, 5500 Campanile Drive, San Diego, CA 92182-7700 USA.
OpenContent license defines the copyright on this document.
Previous    visitors since 01-Apr-99