Red Hat APPLICATION STACK 2.1 RELEASE, Release Note

Page: 9 / 26

Configuring the Java Environment
JBoss Application Server relies on an installed JVM, such as those by Sun, or BEA. Both JVMs
are available from the Red Hat Enterprise Linux 5 Supplementary channels.
THIS RELEASE HAS BEEN CERTIFIED WITH THE SUN
AND BEA JVMS.
Currently Red Hat Application Stack is certified with the Sun JVM version 1.5.0
update 15 or later and the latest BEA JVM available through RHN. This may
change in future releases.
With Red Hat Enterprise Linux 5 there are 1.5 versions of the BEA (JRockit), IBM and SUN
SDKs.
We have adopted the jpackage.org style for the packaging of our Java offerings. This requires
that the
jpackage-utils
rpm be installed on your system. A JPackage-style JVM must be
installed via
yum
(see channel details below) and
jpackage-utils
will be automatically brought
in as a dependency.
1. Install a supported SDK
1.1. Installing a BEA, IBM or Sun SDK
1. Install a Java SDK from RHN
Java SDKs are provided by the Red Hat Enterprise Linux 5 Supplementary channel for your
Linux variant and architecture. Depending on the architecture, the channel names are:
rhel-i386-server-supplementary-5 and rhel-x86_64-server-supplementary-5
The
java-1.5.0-bea
,
java-1.5.0-ibm
and
java-1.5.0-sun
SDKs are available from these
channels. Make sure you also install the
-devel
subpackages.
2. Selecting
alternatives
for
java
,
javac
and
java_sdk_1.5.0
(setting
java_sdk_1.5.0
is
optional).
This is only needed if you want to use the SysV service script and/or want this installed SDK
to be the default java and javac in the system. This choice can often be overridden by setting
the
JAVA_HOME
environment variable.
The
alternatives
system allows different versions of Java, from different sources to
co-exist on your system. You should make sure the desired one is selected so that the
service script uses the one you want.
Chapter 2.
3