These instructions were written with reference to the Firefox browser, and
Redhat Eterprise Linux 5 / CentOS 5. They are primarily for users of
Bruker and Agilent NMR spectrometers who wish to allow someone from either of
these companies to run their spectrometer remotely for testing purposes.
To use WebEx your browser must be able to run Java applications. Once Java has been set up, I have never experienced any other problems. Just wait for your friendly Bruker or Agilent representative to email you an invitation to a meeting, click on the link (or paste it into your browser if your browser doesn’t open it automatically) and accept the invitation to the meeting. As far as I am aware, no modifications to your firewall are necessary.
If Java is not enabled you’ll probably need to
These notes assume you have root access. If you don’t, you might still be able to get it
running by downloading the tar.gz JRE archive, extracting it into a subdirectory of your home
directory, and following the instructions below to create the symbolic link. If the Firefox
plugins directory won’t let you create the symbolic link, you’ll have to download
the tar.bz2 Firefox archive and install that under your home directory as well. Then you will
need to create the symbolic link in this new Firefox, and test it to see if Java works on it.
Note: I have not tried this myself.
yum list installed |grep jre jre.i586 1.7.0_09-fcs installedFor the 64 bit version the response will be similar to...
jre.x86_64 1.6.0_29-fcs installed(Ignore any lines containing “jrefactory” - this is not the JRE).
locate libnpjp2.soThis will probably also show files belonging to the JRE installation which is part of Topspin or VnmrJ. I have not had success linking to these files, but there’s no harm in trying them. Note that if they work at all, they will only work for 32 bit browsers.
If "locate" doesn’t work on your system, have a look in /usr/local to see if there are
any directories with names starting “jre”. If it hasn’t shown up at this stage,
you can assume it’s not installed, and proceed with your own installation. Even if there
is an old JRE sitting in an obscure directory, it should not affect us.
However if you’re really keen to find an existing JRE installation, and don’t feel like getting “locate” working, type (as root)
find / -name libnpjp2.so -printand go and have lunch while it searches through all the disks on your system
|If the Java Runtime Environment is not installed on your system, check whether you need a 32 or 64 bit version as described below, then go to the Downloading the Java Runtime Environment section of these notes.|
uname -a Linux wolfgang 2.6.18-308.16.1.el5 #1 SMP Tue Oct 2 22:01:37 EDT 2012 i686 i686 i386 GNU/Linux Linux russell 2.6.18-308.20.1.el5 #1 SMP Tue Nov 13 10:15:12 EST 2012 x86_64 x86_64 x86_64 GNU/LinuxThe first response line above is from a 32 bit machine called wolfgang, and the second line is from a 64 but machine called russell.
A 32 bit machine can only run 32 bit software, so the version of Firefox must also be 32 it. A 64 bit machine can run either 32 bit or 64 bit software (assuming it has the necessary libraries installed), so you need to do a further test to see what version of Firefox is installed. Type about: in the address bar. At the bottom of the page that appears, you will see something like
Build identifier: Mozilla/5.0 (X11; Linux i686; rv:10.0.10) Gecko/20121026 Firefox/10.0.10for a 32 bit version of Firefox, or
Build identifier: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.10) Gecko/20121025 Firefox/10.0.10for a 64 bit version. (It’s the i686 or x86_64 part that interests us here).
Have a look here to check whether the link to the Java Runtime Environment exists.
cd /usr/lib64/mozilla/plugins ls -lIf it does, you’ll see something like
libnpjp2.so -> /usr/java/latest/lib/amd64/libnpjp2.soor slightly different for 32 bit versions. If you see this, do
ls -l /usr/java/latest/lib/amd64/libnpjp2.soto check that the symbolic link is really pointing at something that exists on disk, and has not been removed at some time.
If you select the rpm format, you should see a popup window offering you the option to either save the file, or open it with the software installer. You can save the file and install it later if you like, but it might be simpler to run the software installer straight away. If you do this, you will get another popup asking for the root password. Once you have supplied this, you need to click on Apply in the next popup window, and installation will proceed. It won’t get very far before it warns you that it is unable to verify the software. This is because it didn’t come from the Red Hat or CentOS repositories. Click on "Install anyway".
You should soon see a "Software installed successfully" popup, possibly with some warnings.
The final graphic above shows the window to save the tar.gz version. Remember you need the rpm or the tar.gz version, not both.
chmod 755 jre-6u37-linux-i586-rpm.bin ./jre-6u37-linux-i586-rpm.bin Unpacking... Checksumming... Extracting... UnZipSFX 5.50 of 17 February 2002, by Info-ZIP (Zip-Bugs@lists.wku.edu). inflating: jre-6u37-linux-i586.rpm error: can’t create transaction lock on /var/lib/rpm/__db.000 Done.The error above did not seem to affect anything.
# rpm -ivh jre-6u37-linux-i586.rpm Preparing... ########################################### [100%] 1:jre ########################################### [100%] Unpacking JAR files... rt.jar... jsse.jar... charsets.jar... localedata.jar... plugin.jar... javaws.jar... deploy.jar...
cd /usr/local tar xvf /home/chris/Downloads/jre-7u9-linux-i586.tar.gz
If you installed the tar.gz version, the symbolic link will be to a different directory. In the example above
cd /usr/lib/mozilla/plugins (or /usr/lib64/mozilla/plugins) ln -s /usr/local/jre1.7.0_09/lib/i386/libnpjp2.so .(The i386 above will be amd64 for a 64 bit installation).
* Note that each of the ln -s commands above ends with a “space dot”.
Finally, exit from your browser, open it again, return to this page, and click on one or both of the links at the top of this page to see if Java is now enabled. If all went well, it should now work. If not, check that the plugin is enabled as described in the Enabling the Plugin section of this page.
yum list installed |grep jreThen do
yum remove jre.i586replacing jre.i586 with whatever version of the package that yum found.
Loaded plugins: fastestmirror Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package jre.i586 0:1.7.0_09-fcs set to be erased --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Removing: jre i586 1.7.0_09-fcs installed 91 M Transaction Summary ================================================================================ Remove 1 Package(s) Reinstall 0 Package(s) Downgrade 0 Package(s) Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Erasing : jre 1/1 Removed: jre.i586 0:1.7.0_09-fcs Complete!If you installed the tar.gz version, you could leave it where it was installed, and just remove the symbolic link from the Firefox plugins directory. If you would prefer to remove it, change to the directory where you installed it...
cd /usr/local rm -r jre1.7.0_09
The method for installing it is the same as described above.
Download and install 32-bit Java for Linux
JRE 7 Installation for Linux Platforms
If you find any mistakes in this document, or have any suggestions, email me at Chris dot Blake at anu.edu.au and let me know.