Basic Steps
...
- down load the files from the java download site. Keep them all in the same directory, e.g./tmp
- check space availablity for each target directory by running checkQuota
- create the jdk-* subdirectory under each OS directory, e.g. linux, solaris, etc.
- change the patch variable in the installJava script to the latest patch number
- cd to the place where you downloaded all the files
- run installJava
- test the new releasesversions
- deploy the new releasesversions
- update the web page
- announce to mailing list (?)
...
mkdir jdk1.6.0_26
...
Target Directories - Readonly and Shadow Version
...
visible path = /afs/slac/package/java/directory_name
...
*If a download release contains two files one ends up in the target directory under bin
...
Install the new versions
...
releasesEdit the script installJava located in
...
cd to the place where you downloaded all the files and execute installJava from there.
...
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 it finds 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. Note that the release script exists only in the visible directory not the shadow directory (no dot in the afs path).
Once you deploy the new version you must restart the servers so they can pick up the changes. The best way is to restart the test server and see if everything is ok there. If nothing breaks then restart the other servers.
...
Updating the Web Page
...
Update the web page in the shadow directory (the visible directory is read-only). Drag the path to index.html into the browser location window to see your changes. Once the code is released the web page will also be updated with the copy in the shadow directory.