Noel Enete
Get Jini Binaries


This is how to get the Jini code and how to setup your environment. If you use the suggested directory names, the examples work right out of the box.

Note: Since Java was first introduced, I have attempted to use the default names of the directories for the various Java products (JDK, JDBC, Jini, etc) hoping that a naming convention would take hold and help me organize my Java development directories. I guess the teams inside Sun are moving at such a rapid pace that there is no time to iron out this relatively minor issue (half a decade has elapsed and the conventions are still inconsistent). So I decided to go with my own convention.

Directory Tree


My directory tree for Java development is:

    java/
      |
      +--java.120/    (or java.122 for /NT)
      |    |
      |    +--docs/
      |
      +--jini.100/
      |
      +--jinitck.100/
      |
      +--nuggets/

Microsoft Windows


Create a base directory to receive all the Jini code:
  • Open a command line and create the following directory: \java.
  • If you haven't already done so, expand the nuggets.zip file into this \java directory.

This version on Nuggets uses Java 2 (aka JDK 1.20 FCS):

  • Download the windows Java Developer Kit (JDK 1.2) big bundle (~20MB) and expand it into the \java directory.
  • Rename the directory from \java\jdk1.2.2 to \java\java.122 (use the ren command).
  • Download the JDK HTML documentation (JDK 1.2) big bundle (~16MB). It expands into the directory jdk1.2.2\docs. Move or copy the docs directory to java.122\docs then discard the original expansion.

To get Jini:

  • If you are not already a member of the Java Developer Connection (JDC), take a moment and register. This is required to download the Jini software.
  • The order of the following steps is important. The documentation is included in the various kits and some of the HTML files overlay previous HTML files. If the zip files are expanded out of order, some documentation will be lost. :(
  • Fill out the survey and download
    • the Jini Starter Kit (jini10.zip)
    • the TCK (Technology Compatibility Kit) (jinitck10.zip) -- this file is not required, but you might as well pick it up while your are here.
    • the JSTK (JavaSpaces Technology Kit) (jstk1_0.zip)
  • 1st Expand jini10.zip into the \java directory (making the ./jini1_0 subdirectory).
  • 2nd Expand jstk1_0.zip into the \java directory (adding to the ./jini1_0 subdirectory). Answer 'A' to overwrite all duplicated file expansions.
  • 3rd Expand jinitck10.zip into the \java directory (making to the ./jinitck1_0 subdirectory).
  • 4th Rename \java\jini1_0 to \java\jini.100 and \java\jinitck1_0 to \java\jinitck.100.

Setup PATH:

  • Add an entry in your path for the directory \java\java.122\bin.

Red Hat Linux v. 6.0


Remove the Kaffe Java that comes with the distribution (Kaffe is not as mature as blackdown).

  • Logon to root.
  • From a command line, invoke GNU's package installer and uninstaller gnorpm
  • Under the Development section, open the Languages subsection.
  • Select the Kaffe package and uninstall it.

Create a base directory to receive all the Jini code:

  • Open a command line and create the following directory: ~/java.
  • If you haven't already done so, expand the nuggets.zip file into this ~/java directory.

This version of the Nuggets runs fine on blackdown's Java 2 distribution:

  • Download the Linux Java Developer Kit (JDK 1.2) from one of the mirror sites. Choose the i386 branch and the filename is jdk1.2pre-v2.tar.bz2 (~19MB).
  • After downloading the JDK, expand it with Linux's bunzip utility into the ~/java directory. If you need help with bunzip2, type bunzip --help. For more information about bzip2 check here.
  • After expanding the JDK, rename the directory to ~/java/java.120 (use mv).
  • Download the JDK HTML documentation (JDK 1.2) big bundle (~16MB) from Sun. It expands into the directory jdk1.2.0/docs. Copy the docs directory to ~/java.120/docs (you can use cp -R to do that) then discard the original expansion.

To get Jini:

  • If you are not already a member of the Java Developer Connection (JDC), take a moment and register. This is required to download the Jini software.
  • The order of the following steps is important. The documentation is included in the various kits and some of the HTML files overlay previous HTML files. If the zip files are expanded out of order, some documentation will be lost. :(
  • Fill out the survey and download
    • the Jini Starter Kit (jini10.zip)
    • the TCK (Technology Compatibility Kit) (jinitck10.zip) -- this file is not required, but you might as well pick it up while your are here.
    • the JSTK (JavaSpaces Technology Kit) (jstk1_0.zip)
  • 1st Expand jini10.zip into the ~/java directory (making the ~/java/jini1_0 subdirectory).
  • 2nd Expand jstk1_0.zip into the ~/java directory (adding to the ~/java/jini1_0 subdirectory).
  • 3rd Expand jinitck10.zip into the ~/java directory (making to the ~/java/jinitck1_0 subdirectory).
  • 4th Rename ~/java/jini1_0 to ~/java/jini.100 and ~/java/jinitck1_0 to ~/java/jinitck.100.

Setup PATH and DISPLAY:

  • If you have not conditioned your DISPLAY variable for X yet, add the following line to your .bashrc or other logon script: DISPLAY=:0.0
  • Add an entry in your path for the directory ~/java/java.120/bin.
  • Or, if you are using several versions of Java, code scripts to set the path as needed. I use the 12 script below to set the path for JDK 1.20. If you use a dot (.) and a space on the command line before the name of the script, the path adjustments in the script apply to your current shell.
  • Also, in the script below, the dot (.) directory is added to the path as a personal preference for my java terminal sessions. It allows me to issue the command r1 rather than the command ./r1 to invoke a script.
    #!/bin/sh
    #
    #  Script in home directory called 12 -- Sets path to JDK 1.2
    #
    #  Use a dot (.) to set the path in your current shell:
    #    . 12
    #
    PATH=~/java/java.120/bin:.:$PATH
    PS1="1.20 [\u@\h \W]\\$ "

Linux & Windows/NT Specifics


The examples in these nuggets were first developed using Windows/NT. Then I switched the OS of my primary development station from NT to Linux. Now, I do all my work under Linux (I just wanted to see if it was possible to do my work Gates-free). I have attempted to maintain a parallel set of scripts and .bat files so the examples should continue to work on either NT or Linux.

Since I do not personally spend too much time on /95 or /98 (though some of my team members do and give me feedback from time to time) the nugget examples may have to be tweeked a bit to run properly on those OS's. In particular, /98 may need to be adjusted to accommodate the large space needed to store environment variables (at least until I can think of a better way to do it).



by Noel Enete . . . www.enete.com . . . noel@enete.com