Chapter 4. Using JBoss AS
12
http://localhost:8080/web-console
You can use the Web Console to administer JBoss AS.
The entire JBoss AS 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
AS 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.
Note
Depositing files for which the user
jboss
has no read access in the deployment
directory will cause the server to fail to deploy.
To create additional JBoss AS 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.
Note
Please note that automated updating of configurations created using method above is
not supported. If you create custom configurations, you will manually have to port files /
changes from a new update to that configuration.
4.2. Using run.sh (development)
For development, you can activate the JBoss AS 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.
