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
- check that the new versions were unpacked properly
- run the release script to deploy the new versions
- restart the test server and check that everything still works
- restart all the other servers. Use the server monitoring page to do this.
- update the web page
- announce to mailing lists
The download url may change but currently the download page is
http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html
Download to /tmp, the set of files that match the pattern:
Pattern |
Example |
---|---|
jdk-*-linux-i586.bin |
jdk-6u26-linux-i586.bin |
jdk-*-solaris-sparc.sh |
jdk-6u26-solaris-sparc.sh |
jdk-*-linux-x64.bin |
jdk-6u26-linux-x64.bin |
jdk-*-solaris-sparcv9.sh |
jdk-6u26-solaris-sparcv9.sh |
Make sure there is sufficient space in the target directories by running
/afs/.slac.stanford.edu/package/java/common/install/checkQuota
if not, clean up by deleting old releases in:
- /afs/.slac.stanford.edu/package/java/i386_linux2
- /afs/.slac.stanford.edu/package/java/amd64_linux
- /afs/.slac.stanford.edu/package/java/sun4x_55
Old releases should not have links to them and their release number should be several levels lower than a current release.
If you still need more space put in an afs request
Use the mkdir command to create the new directory; for example for patch 26:
cd /afs/.slac.stanford.edu/package/java/i386_linux2
mkdir jdk1.6.0_26
Target Directories - Readonly and Shadow Version
visible path = /afs/slac/package/java/directory_name
shadow path = /afs/.slac/package/java/directory_name (note the dot in the path; the ls command will not show this dir)
directory_name |
afs volume of visible path |
afs volume of shadow path |
---|---|---|
i386_linux |
pkg.java.i386_linux2.read |
pkg.java.i386_linux2 |
amd64_linux |
pkg.java.amd64_linux.read |
pkg.java.amd64_linux |
*sun4x_55 |
pkg.java.sun4x_55.readonl |
pkg.java.sun4x_55 |
*If a download release contains two files one ends up in the target directory under bin
Install the new versions
Change the patch number by editing the script installJava located in
/afs/.slac.stanford.edu/package/java/common/install/installJava
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. The same script is in the shadow directory but it refers to the visible path when building the package list.
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). Use the path plus index.html in the browser location window to view your changes. Once the code is released the web page will also be updated with the copy in the shadow directory.
If you need to make changes to the web page only then rerun the release script using common as the argument:
/afs/slac.stanford.edu/package/java/build/release common
The common directory, containing the web page index.html will be updated. View the changes on line using the url
http://www.slac.stanford.edu/comp/java/index.html
Announce via Mailing Lists
Email Address |
Type |
Authorization Needed |
Comment |
---|---|---|---|
slac-java@slac.stanford.edu |
majordomo |
no |
|
lcd-l@slac.stanford.edu |
majordomo |
no |
|
comp-change |
majordomo |
yes |
unix-admin can post so email your message to them and ask them to post it. |
Fermi datalist |
campus list |
yes |
need to be Fermi collaborator. Post via the web url: |