Red Hat APPLICATION STACK 1.4 RELEASE Instruction Manual

Red Hat Application
Stack 1.4
Release Notes
for Use with Red Hat Application Stack 1.4

Release Notes
Red Hat Application Stack 1.4 Release Notes
for Use with Red Hat Application Stack 1.4
Edition 1.0
Copyright © 2006-2008

iii
1. Introduction 1
1.1. Overview of This Release ............................................................................................. 1
1.2. Installation Prerequisites ............................................................................................... 1
1.3. Package-specific Notes ................................................................................................ 1
2. Configuring the Java Environment 3
2.1. Install a supported SDK .............................................................................................. 3
2.1.1. Installing a BEA, IBM or Sun SDK ..................................................................... 3
2.2. Install the jbossas package ....................................................................................... 4
2.2.1. Using up2date / RHN (Preferred Method) ......................................................... 4
2.2.2. Using up2date / DVD ..................................................................................... 4
3. Installing Red Hat Application Stack 7
4. Using JBoss AS 11
4.1. Using the Linux service (production) ........................................................................... 11
4.2. Using run.sh (development) ....................................................................................... 12
4.3. Creating copies of JBOSS_HOME ................................................................................. 13
4.4. Using the jbossas-* commands from any directory .................................................. 14
4.5. Running multiple instances of JBoss AS ..................................................................... 14
4.5.1. Running multiple instances of JBoss AS using different sets of ports .................. 15
4.5.2. Running multiple instances of JBoss AS binding to different local IP addresses
.................................................................................................................................. 16
4.6. More Information ....................................................................................................... 16
5. Export Control 17

iv

Chapter 1.
1
Introduction
1.1. Overview of This Release
Red Hat Application Stack is a set of software components that have been tested and certified to work
together in an integrated fashion. Red Hat Application Stack is designed for dynamic web applications
for both the LAMP and Java platforms.
1.2. Installation Prerequisites
• Red Hat Application Stack V.1.4 has been tested and certified on Red Hat Enterprise Linux 4 U5
systems. It is not certified for use with earlier versions of Red Hat Enterprise Linux. Please follow the
separate instructions for installing Red Hat Enterprise Linux 4 before installing Red Hat Application
Stack V.1.4.
• Red Hat Application Stack V.1.4 is available for 32- and 64-bit Intel architectures only (i386 and
x86_64).
• Red Hat Application Stack V.1.4 includes JBoss AS 4.2, for running web applications in a standard
middleware environment. Note that JBoss AS uses an embedded Tomcat and does not require a
stand-alone Tomcat. Before installing and running JBoss AS you will require a working installation of
Java 1.5. Currently Red Hat Application Stack is certified with the Sun JVM 1.5.0 update 15 or later,
and the latest BEA JVM available through RHN. Please refer to Chapter 2, Configuring the Java
Environment for instructions on configuring the Java environment for JBoss AS.
• If you intend to use the production config (started by default), you will need atleast 1.5GB of physical
memory.
1.3. Package-specific Notes
In most cases, Red Hat Application Stack contains more recent versions of packages than those that
are included in Red Hat Enterprise Linux. Installing Red Hat Application Stack may update/overwrite
these packages. Please ensure you review the complete package list before beginning the installation
process.

2

Chapter 2.
3
Configuring the Java Environment
JBoss AS relies on an installed JVM, such as those by Sun, or BEA. Both JVMs are available from the
Red Hat Enterprise Linux (AS/ES) Extras channel.
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 4 U6 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(TM) offerings. This requires
that the jpackage-utils rpm be installed on your system. A JPackage-style JVM must be installed
via up2date (see channel details below) and jpackage-utils will be automatically brought in as a
dependency.
2.1. Install a supported SDK
2.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 4 Extras channel for your Linux variant
and architecture. The channel names are as follows:
rhel-arch-variant-4-extras
where:
arch = i386 or x86_64 variant = as, or es
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.
As root, issue the following command:

Chapter 2. Configuring the Java Environment
4
/usr/sbin/alternatives --config java
and make sure the desired one is selected (marked with a '+'), or select it by entering its number
as prompted.
Make sure you do the same for javac and java_sdk_1.5.0. We recommend that all point to
the same manufacturer and version.
2.2. Install the jbossas package
2.2.1. Using up2date / RHN (Preferred Method)
1. up2date your RHEL4 installation and install the JVM as described above.
2. Subscribe to the Enterprise Application Platform child channel:
For example: jbappplatform-4-i386-as-4-rpm or jbappplatform-4-x86_64-as-4-rpm
3. Install JBoss AS:
• For the Application Server (which includes an embedded Tomcat), run:
up2date jbossas
Refer also to Chapter 4, Using JBoss AS below.
2.2.2. Using up2date / DVD
To install using up2date / DVD:
1. up2date your installation and install the JVM as described above.
2. Mount the Red Hat Application Stack V.1.4 DVD.
3. Add the following line to /etc/sysconfig/rhn/sources to use up2date directly on the RPMs
on the disk:
dir RedHat-Application-Stack-V1 path_to_mounted_DVD/RedHat/RPMS
4. Install JBoss AS:
• For the Application Server (which includes an embedded Tomcat), run:
up2date jbossas
5. After the installation is complete, remove the line you added to /etc/sysconfig/rhn/sources
in Step 3. Failure to do this will result in up2date producing warnings whenever you run up2date
again without mounting the Red Hat Application Stack V.1.4 DVD.

Using up2date / DVD
5
Refer also to Chapter 4, Using JBoss AS below.
If you are upgrading from version 1.1 of Red Hat Application Stack, please note that the "jbossas-
ejb3" package has now been obsoleted and it's contents merged into the main jbossas package. An
"up2date jbossas" command will upgrade everything correctly.

6