Table of Contents
Advertisement
Chapter 4. Using JBoss Application Server
so no file conflicts shall exist.
For more flexibility in the configuration of the different servers, you may want to create full
copies of
JBOSS_HOME
sure you use the
command's
cp
Then, in
/etc/sysconfig/service-name
variable.
Optionally, you can just uncomment and change the value of
so as to specify an empty or non-existent directory and the script will automatically create a
copy of the RPM-installed
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
Note
Starting the server this first time may take a little longer due to the file copying.
There are 2 ways to run additional instances of JBoss Application Server and avoid port
conflicts:
• By using different sets of ports
• By binding to different local IP addresses
5.1. Running multiple instances of JBoss Application Server
using different sets of ports
Using different sets of ports
The BindingManager in JBoss Application Server can be used to dynamically override service
configurations (e.g. port numbers). Jbossas has some pre-configured overrides, namely
,
and
ports-01
ports-02
/var/lib/jbossas/docs/examples/binding-manager/sample-bindings.xml
overrides can be used when multiple instances of JBoss Application Server must be started.
Please follow these steps when multiple instance of JBoss Application Server need to be
started:
1. Create a new file
/etc/init.d/service-name
16
. This is described in
Creating copies of JBOSS_HOME
switch to preserve the
p
, uncomment and update the value of the
/var/lib/jbossas
. The configuration file can be found at
ports-03
user and group ownership.
jboss
JBOSS_HOME
(original
JBOSS_HOME
.
jboss
which is a symlink to
above -- make
JBOSS_HOME
as described above
) for you when the service is
. These sets of
/etc/init.d/jbossas
,
Advertisement
Table of Contents
