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

Chapter 4. Using JBoss AS
Please see
information
JBoss AS 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 AS.
The entire JBoss AS suite runs under a new
'
su -s /bin/bash jboss
JBoss AS deployment directory, due to file system permissions. Alternatively, a developer can
be listed in the
jboss
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 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 command):
cp
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
' system command to deposit
user group by the system administrator. The best approach is to use the
variable in
JBOSSCONF
) and the init script will create a new configuration directory
jboss
system user. It may be necessary to use the
jboss
.ear / .war / .jar
has no read access in the deployment
jboss
/etc/sysconfig/jbossas
jboss
for more
files under the
JBOSSCONF
to a
user) or an empty