Red Hat APPLICATION STACK 2.1 - RELEASE NOTES Release Note page 18

Chapter 4. Using JBoss Application Server
Please see
information
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
necessary to use the '
files under the JBoss Application Server deployment directory, due to file system
.jar
permissions. Alternatively, a developer can be listed in the
administrator. The best approach is to use the Web Console (URL above) to deploy the
application.
Note
Depositing files for which the user
directory will cause the server to fail to deploy.
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
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
variable in the file:
/etc/sysconfig/jbossas
Optionally, you can just set the
non-existent subdirectory (existing parent with write access by the
directory (with write access by
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.
12
http://kbase.redhat.com/faq/FAQ_107_9963.shtm
su -s /bin/bash jboss
command):
cp
variable in
JBOSSCONF
) and the init script will create a new configuration directory
jboss
system user. It may be
jboss
' system command to deposit
user group by the system
jboss
has no read access in the deployment
jboss
/etc/sysconfig/jbossas
jboss
for more
.ear / .war /
JBOSSCONF
to a
user) or an empty