Using Run.sh (Development); Creating Copies Of Jboss_Home - Red Hat APPLICATION STACK 1.2 - RELEASE NOTES Release Note

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.

2. Using run.sh (development)

For development, you can activate the JBoss AS server with the familiar
usual. The RPM installs the
jbossas
/var/lib/jbossas
So, you can to
cd /var/lib/jbossas/bin
If you wish to use a different JVM than the one that alternatives points to, you will need to set
JAVA_HOME first.
Tip
JAVA_HOME
may not want to have
to use the
this global setting of
If you still need to set
alternatives
JAVA_HOME=/usr/lib/jvm/java
IMPORTANT
The entire JBoss AS suite runs under a new
necessary to use the
server, change configuration, deploy etc., due to file system permissions.
Alternatively, a developer can be listed in the
administrator.
Yet another possibility is to create a personal copy of JBOSS_HOME (see

Creating copies of JBOSS_HOME

To create additional JBoss AS configurations besides the provided 'default', 'production',
JBOSS_HOME
and use
can be set system-wide in
JAVA_HOME
-selected one instead. These users may be affected by
alternatives
.
JAVA_HOME
JAVA_HOME
-selected SDK is in
su -s /bin/bash jboss
Using run.sh (development)
in
from there.
run.sh
. But beware, some users
/etc/profile
set to this same SDK. Also, some may prefer
for some other reason, the
, so a export
/usr/lib/jvm/java
will do.
system user. It may be
jboss
system command to run the
user group by the system
jboss
below).
command as
run.sh
13