Red Hat Application Stack V.2.0 Release Notes

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.

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.

JBoss Application Server can be started, stopped, and configured to start automatically at boot time either from the command line or using a graphical tool.

You can start and stop the jbossas service using the service command as root on a console window (as is typical of a network service):

service jbossas start
...
service jbossas stop

The behavior at boot can be controlled with the chkconfig command, as any other Linux service (see chkconfig man page).

Alternatively, you can issue the command system-config-services to activate the graphical Red Hat Service Configuration Tool, which can also be activated from the main menu. Select:

System Settings > Server Settings > Services

JBoss Application Server is configured with its internal servlet engine to listen for HTTP traffic on port 8080. Once the jbossas service has been started, you can verify that it is running by pointing your web browser to:

http://localhost:8080/web-console

You can use the Web Console to administer JBoss Application Server.

The entire JBoss Application Server suite runs under a new jboss system user. It may be necessary to use the 'su -s /bin/bash jboss' system command to deposit .ear / .war / .jar files under the JBoss Application Server deployment directory, due to file system permissions. Alternatively, a developer can be listed in the jboss user group by the system administrator. The best approach is to use the Web Console (URL above) to deploy the application.

To create additional JBoss Application Server configurations besides the provided 'default', 'minimal', 'all' and 'production', you must create a new directory for your configuration as follows (note the switches given to the cp command):

export JBOSS_BASE=/var/lib/jbossas
cd $JBOSS_HOME
cp -pL -R server/default server/myownconfig

You can then change the configuration and request it to be used by setting the JBOSSCONF variable in the file:

/etc/sysconfig/jbossas

Optionally, you can just set the JBOSSCONF variable in /etc/sysconfig/jbossas to a non-existent subdirectory (existing parent with write access by the jboss user) or an empty directory (with write access by jboss) and the init script will create a new configuration directory tree for you based on the current "production" configuration when the service is first started. You can then stop the service, adjust the configuration as desired, and start it again.

For development, you can activate the JBoss Application Server with the familiar run.sh command as usual. The jbossas RPM installs the JBOSS_HOME in

/var/lib/jbossas

So, you can cd to /var/lib/jbossas/bin and use run.sh from there.

If you wish to use a different JVM than the one that alternatives points to, you will need to set JAVA_HOME first.

To create additional JBoss Application Server configurations besides the provided 'default', 'production', 'minimal' and 'all', you must create a new directory for your configuration as follows (note the switches given to the cp command):

JBOSS_BASE=/var/lib/jbossas
cd $JBOSS_HOME
cp -pL -R server/default server/myownconfig

You can then change the configuration and request it to be used by specifying it in the -c flag to run.sh, as usual.

The analog of unzipping another copy of JBoss Application Server in a different directory is to make a copy of the RPM-installed JBOSS_HOME, located at /var/lib/jbossas.

You probably want this copy to have your own userid and group, so use:

cp -L -R /var/lib/jbossas my_new_jboss_home_directory

If you want to retain the jboss user and group ownership, use instead:

cp -pL -R /var/lib/jbossas my_new_jboss_home_directory

To run multiple servers simultaneously you will need to adjust the configuration to avoid port conflicts, as described in the JBoss Application Server documentation. Refer to Running multiple instances of JBoss Application Server for more information.

Most of the commands found in $JBOSS_HOME/bin have equivalents in /usr/bin with names like jbossas-command, where command is the original JBoss Application Server command name. So, for instance, there is a jbossas-run command that is available from any directory.

To use these commands, however, you must set two environment variables:

export JBOSS_HOME=/var/lib/jbossas
export JAVA_HOME=/usr/lib/jvm/java

where the value you give for JAVA_HOME is the location of your installed Java VM.

The description here is restricted to running multiple instances of the JBoss Application Server Linux service. Running multiple instances with run.sh is already described elsewhere in the JBoss Application Server documentation.

You can administer multiple SysV services that run JBoss Application Server by creating additional service scripts. The process basically consists of:

For more flexibility in the configuration of the different servers, you may want to create full copies of JBOSS_HOME. This is described in Creating copies of JBOSS_HOME above -- make sure you use the cp command's p switch to preserve the jboss user and group ownership. Then, in /etc/sysconfig/service-name, uncomment and update the value of the JBOSS_HOME variable.

Optionally, you can just uncomment and change the value of JBOSS_HOME as described above so as to specify an empty or non-existent directory and the script will automatically create a copy of the RPM-installed /var/lib/jbossas (original JBOSS_HOME) for you when the service is first started. The current "minimal", "production", "default" and "all" configurations will be copied. Make sure the parent directory, in case of a new directory, or the directory itself, if already existent, have write permissions for the user jboss.

There are 2 ways to run additional instances of JBoss Application Server and avoid port conflicts:

More general documentation for JBoss Application Server is available under /usr/share/doc/jbossas-4.2.0.