• Welcome
• Take our Survey
• Getting Starting
• FAQ's
• Creating Applications
• Setting up a Portal
• User Pages
• Email Notifications
• Item Routing
• Applications
• Administration
• Access Rights & Permissions
• intraNET Installation
  • Windows Installation
  • Preparing MS SQL
  • Preparing MSDE
  • Linux Installation
    • Installing JRE
    • Installing PostgreSQL
• Active Directory Sync
• ActiveX Components

Installing Java Runtime Environment

1. Download JRE
In order to run intraNET V5, you need to install Java Runtime Environment (JRE), Standard Edition. To begin performing these steps, login as the “root” user. You can download JRE for Linux from Sun Microsystems® through the following link: http://java.sun.com/j2se/1.4.2/download.html

From the JRE download, select “Linux GNUZIP Tar shell script”. Select "Accept" on the Binary Code License Agreement to proceed to the download page. Right click on the link named “Download j2re-1_4_2-linux-i386.bin” and choose “Save Target As…” (Internet Explorer) or “Save Link As…” (Netscape) to save the file to your local disk.

2. Install JRE
Now you can install the package. In this example installation directory is /opt (recommended). Copy the “j2re-1_4_2-linux-i386.bin” file to the /opt directory and change access rights to add the possibility to execute the file and then run the script:
bash# chmod u+x j2re-1_4_2-linux-i386.bin
bash# ./j2re-1_4_2-linux-i386.bin
When the installation is finished the directory “/opt/j2re1.4.2” will be created with all files from JRE 1.4.2.

3. Test JRE
Test Java server VM. If everything is ok you should see the version information:
  bash# /opt/j2re1.4.2/bin/java -server -version
java version "1.4.2"
java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b92)
Java HotSpot(TM) Server VM (build 1.4.2-b92, mixed mode)
If this command displays an error
Error: failed /opt/j2re1.4.2/lib/i386/server/libjvm.so,
Because libstdc++-libc6.1-1.so.2: cannot open shared object
file: No such file or directory
you must check for proper library version and provide symbolic link to it. On Red Hat 7.2 process should look like this:
bash# cd /usr/lib
bash# ls -x libstdc++-libc*.so.*
libstdc++-libc6.2-2.so.3
bash# ln -s libstdc++-libc6.2-2.so.3 libstdc++-libc6.1-1.so.2
Now repeat the previous test. Java VM should properly display options and the error should not appear. If this is the case, Java VM is ready. If not, check your link again – you could easily have misspelled the library names (use copy/paste if available in your terminal emulation).