Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. down load the files from the java download site. Keep them all in   to /tmp. You will use gtar -C <path> or execute *.bin to put the files to the directory.
  2. check space availablity for each target directory by running checkQuota
  3. make sure you are in the shadow directory, e.g. /afs/.slac...  and not /afs/slac (no dot)
  4. IF you get an executable (*.bin) then use the installJava script and you create the jdk-* subdirectory under each OS directory first, e.g. linux, solaris, etc.
  5. IF you get a zipped tarball make sure zipped tarballs use the installJava7 script which uses gtar -C is used to unpack and install the directories.
  6. change the patch variable in the installJava script install script (installJava or installJava7) to the latest patch number
  7. cd to the place where you downloaded all the files, e.g. /tmp on glastlnx07
  8. Make sure to change the patch number before running the script.
  9. Edit the install script and check that the new version names will unpack properly. Run the installJava* script.
  10. run the release script to deploy the new versions to the read-only disk.
  11. restart the test server and check that everything still works
  12. restart all the other servers. Use the server monitoring page to do this. If that doesn't work, logon to the machine and run the stop/start scripts.
  13. update the web page (see url address below)
  14. announce to mailing lists (see list names below)

...

Use the mkdir command to create the new directory, if needed; for example for patch 26:

...

/afs/.slac.stanford.edu/package/java/common/install/installJava

cd to the place /tmp where you should have downloaded all the files and execute installJava(7) from there. If using tarballs then cd to /tmp on glastlnx07.

Deploy the new versions

The script /afs/slac.stanford.edu/package/java/build/release is a bourne shell script that assembles the names of the volumes in the java directory that will be updated and then makes calls to the vos_release command which in turn calls vos commands to update a release.  The same script is in the shadow directory but it refers to the visible path when building the package list.

...