Red Hat APPLICATION STACK 2.2 RELEASE Instruction Manual

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

Release Notes
Red Hat Application Stack 2.2 Release Notes
for Use with Red Hat Application Stack 2.2
Edition 1.0
Copyright © 2008 Red Hat

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 yum / RHN (Preferred Method) ................................................................ 4
2.2.2. Using yum / DVD .............................................................................................. 4
3. Installing Red Hat Application Stack 5
4. Using JBoss Application Server 9
4.1. Using the Linux service (production) ............................................................................ 9
4.2. Using run.sh (development) ....................................................................................... 10
4.3. Creating copies of JBOSS_HOME ................................................................................. 11
4.4. Using the jbossas-* commands from any directory .................................................. 12
4.5. Running multiple instances of JBoss Application Server ............................................... 12
4.5.1. Running multiple instances of JBoss Application Server using different sets of
ports ....................................................................................................................... 13
4.5.2. Running multiple instances of JBoss Application Server binding to different local
IP addresses ........................................................................................................... 14
4.6. More Information ....................................................................................................... 15
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 (TM) platforms.
1.2. Installation Prerequisites
• Red Hat Application Stack V.2.2 has been tested and certified on Red Hat Enterprise Linux 5
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 5 before installing Red Hat Application
Stack V.2.2.
• Red Hat Application Stack V.2.2 is available for 32- and 64-bit Intel architectures only (i386 and
x86_64).
• Red Hat Application Stack V.2.2 includes JBoss Enterprise Application Platform 4.2, for running
web applications in a standard middleware environment. Note that the JBoss Enterprise Application
Platform uses an embedded Tomcat and does not require a stand-alone Tomcat. Before installing
and running the JBoss Application Server (the application server component of JBoss Enterprise
Application Platform 4.2), 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 Application Server.
• 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 . 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 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 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.
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 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.
As root, issue the following command:
/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.

Chapter 2. Configuring the Java Environment
4
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 yum / RHN (Preferred Method)
1. Update your Red Hat Enterprise Linux 5 installation and install the JVM as described above.
2. Subscribe to the Enterprise Application Platform child channel:
e.g: jbappplatform-4-i386-as-5-rpm or jbappplatform-4-x86_64-as-5-rpm
3. Install JBoss Application Server:
• For the Application Server (which includes an embedded Tomcat), run:
yum install jbossas
Refer also to Chapter 4, Using JBoss Application Server below.
2.2.2. Using yum / DVD
To install using yum / DVD:
1. Update your installation and install the JVM as described above.
2. Mount the Red Hat Application Stack V.2.2 DVD.
3. Create a new file in /etc/yum.repos.d/ with the following contents to update directly from the
RPMs on the disk:
[stacksv2]
name=Red Hat App Stack
baseurl=file:///path/to/mounted/DVD/Stacks/
enabled=1
4. Install JBoss Application Server:
• For the Application Server (which includes an embedded Tomcat), run:
yum install jbossas
5. After the installation is complete, remove the file you added in /etc/yum.repos.d/ in Step 3 (or
set enabled=0 in that file). Failure to do this will result in yum exiting with an error whenever it is
run again without mounting the Red Hat Application Stack V.2.2 DVD.
Refer also to Chapter 4, Using JBoss Application Server below.

Chapter 3.
5
Installing Red Hat Application Stack
To install Red Hat Application Stack V.2.2:
1. If you have an existing database, back up your data and shut down the database:
• If you are using PostgreSQL:
Back-up your database. For example, run:
su -
rm -rf /tmp/pg.backup
su - postgres
/usr/bin/pg_dumpall > /tmp/pg.backup
exit
• If you are using MySQL:
Backing-up your database is optional but recommended. Run as root:
mysqldump --all-databases -p > /tmp/mysqldumpfile.sql
2. Stop the daemons:
/sbin/service httpd stop
• To shut down MySQL:
/sbin/service mysqld stop
• To shut down PostgreSQL:
/sbin/service postgresql stop
3. Install the software:
• Option 1. To install from RHN, which is the preferable option to avoid dependency issues:
• Subscribe to the Red Hat Application Stack child channel:
e.g: rhel-x86_64-5-appstk-2 or rhel-i386-5-appstk-2
• Subscribe to the Enterprise Application Platfrom child channel:
e.g: jbappplatform-4-i386-as-5-rpm or jbappplatform-4-x86_64-as-5-rpm
• Run as root: yum update
• Run as root: yum groupinstall stacks

Chapter 3. Installing Red Hat Application Stack
6
• Option 2. To install from RPMs on Disk:
Follow the instructions in Section 2.2.2, “Using yum / DVD” to mount the DVD and set up the
local RHN channel (steps 1-3). Then as root run:
yum update
Followed by:
yum groupinstall stacks
After the installation is complete, remove the file you added in /etc/yum.repos.d/ (or set
enabled=0 in that file). Failure to do this will result in yum exiting with an error whenever it is run
again without mounting the Red Hat Application Stack V.2.2 DVD.
Note
You may need to install the following packages to satisfy dependencies before
executing the above command, if they are not already installed:
•apr-devel
•apr-util-devel
•libc-client
•mx
•pcre-devel
Note
You can also install specific components of the stack via the yum groupinstall
directive specified in Section 3. In addition to "stacks", the following groups are
defined:
j2ee - Installs jbossas, jboss-seam, mod_jk and database jdbc drivers
lamp - Installs httpd, mysql, php and all components related to mysql
lapp - Installs httpd, postgresql, php and all components related to postgresql
docs - Installs documentation for various components
When using the groupinstall directive, you can specify multiple groups at the
same time (even if they share packages).
Analogous to groupinstall, you can use the "groupremove" directive to
remove all the packages in a group. The groupremove directive will only remove
packages in the group; not the dependencies that the package install may have
brought in.
4. Restore your database:
• For PostgreSQL: