How to Setup Multiple JBoss Instances on a Single Server

splattersquadSecurity

Nov 17, 2013 (3 years and 8 months ago)

97 views

JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
1

of
20




























How to Setup Mul
tip
le JBoss Instances on a Single Server


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
2

of
20




Precision Software Limited



Precision software products are copyrighted and all rights are reserved by Precision Software
Limited.


This document is copyrighted and all rights are reserved. No part of this document may be
rep
roduced, transmitted, adapted, translated or electronically stored without the prior written
consent of Precision Software Limited.


TRAXi3



i3
S
hip



i3
T
rade



i3Comply


and XM4


and are registered trademarks of
Precision Software Limited.

Progress


is

a registered trademark of Progress Software Corporation.


Precision Software Limited shall not be liable for errors contained herein or for incidental or
consequential damage or loss in connection with the use of this document. Whilst every effort is
made

to eliminate errors, Precision Software Ltd. cannot be held liable for erroneous information
contained herein.

JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
3

of
20


Document Control


Issue Control


Issue


Date


Changes Made

1.0


23

Aug

0
6

Created

1.1


2 October 2006

Extended to include all setup involved.











Cross Reference





Change Summary


Nr.

Description

Date

By whom

1.0

Created

23
/
08
/0
6

Peter Evans

1.1

Extended to include all setup involved.

2/10/06

Peter Evans











JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
4

of
20



Contents


D
OCUMENT
C
ONTROL

................................
................................
................................
................................
.

3

I
NSTALL

................................
................................
................................
................................
......................

5

Notes:

................................
................................
................................
................................
.....................

5

TCP/IP Setup:

................................
................................
................................
................................
.........

5

iTRAX Install:

................................
................................
................................
................................
.........

5

H
IGHWAY
C
ONSIDERATIONS

................................
................................
................................
.......................

8

Highway Database:

................................
................................
................................
................................

8

JBoss:

................................
................................
................................
................................
.....................

9

JMS Database:

................................
................................
................................
................................
......
11

cTRAX Listener:

................................
................................
................................
................................
....
14

iTRAX:

................................
................................
................................
................................
...................
16

Windows Services:

................................
................................
................................
................................
.
16

Miscellaneous:

................................
................................
................................
................................
.......
20

Notes:

................................
................................
................................
................................
....................
20















JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
5

of
20


Install


Notes
:


In certain places it may be necessary to specify the IP address rather than the logical hostname.
The reason for this is currently unknown and may be configuration

problem with the test machine.
The host name should be used by default and the IP address specified only if this is found not to
work.


If there is more than one network card in the server then you need to be careful how
machine names are mapped to IP add
resses. The DNS server may not always may the
machine to the same IP address in which case bind exceptions may occur with the JBoss
deployment or lookup problems may arise at run time.
In these cases it may not be
possible to use machine names, or machine
names the are managed by the DNS server.


TCP/IP Setup
:

Server has been multihomed.


Two IP addresses used


192.168.11.155

itrax_production

192.168.11.156

itrax_test




iTRAX Install
:

Install the “Production” version of iTRAX to “
\
TRAXi3_Production
\
iTRAX
” using the iTRAX
installer.


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
6

of
20




Specify the “Production” hostname for the JBoss server.




Specify the JDBC and 4GL connection details for the production database.


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
7

of
20


Install the “Test” version of iTRAX to “
\
TRAXi3_Test
\
iTRAX” using the iTRAX installer.


Specify the test hostname (“itrax_test”) for the JBoss server.


Specify the JDBC and 4GL connection details for the test database.





You should now have shortcuts for both the Production and Test Environments.




The install routine will have over
writ
ten the Windows service entries and some registry entries for
the production environment. This will be corrected manually later.


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
8

of
20


Highway Considerations


Highway Database:

1. Start Multiple Instances:

runServer.bat should be modified to include the
correc
t
server i
p

address. This can be done using
the “
-
address” switch. “
-
port” can be used to change the port used. By default this is 9001.


Single Instance Command:

@java
-
classpath %1
\
lib
\
db
\
hsqldb.jar org.hsqldb.Server
-
database
highwaydb
-
silent true
-
tr
ace false


Multiple Instance Command:

@java
-
classpath %1
\
lib
\
db
\
hsqldb.jar org.hsqldb.Server
-
database
highwaydb
-
address 192.168.11.123
-
port 9001

-
silent true
-
trace false



Modify “
\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
runServer.bat
” so the java command
run is:

@java
-
classpath %1
\
lib
\
db
\
hsqldb.jar org.hsqldb.Server
-
database
highwaydb
-
address itrax_production
-
port 9001

-
silent true
-
trace
false


Modify “
\
TRAXi3_Test
\
iTRAX
\
highway
\
db
\
runServer.bat
” so the java command run is:

@java
-
classpath %1
\
lib
\
db
\
hsqldb.jar org.hsqldb.Server
-
database
highwaydb
-
address itrax_test
-
port 9001

-
silent true
-
trace false


Modify

\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
WrapperHighwayDatabaseService.conf

so that the additional application parameters are specified:

wrapper.
app.parameter.1=org.hsqldb.Server

wrapper.app.parameter.2=
-
database highwaydb

wrapper.app.parameter.3=
-
silent true

wrapper.app.parameter.4=
-
trace false

wrapper.app.parameter.5=
-
address itrax_production

wrapper.app.parameter.6=
-
port 9001


Modify “
\
TRAXi3_Te
st
\
iTRAX
\
highway
\
db
\
WrapperHighwayDatabaseService.conf

so that the additional application parameters are specified:

wrapper.app.parameter.1=org.hsqldb.Server

wrapper.app.parameter.2=
-
database highwaydb

wrapper.app.parameter.3=
-
silent true

wrapper.app.para
meter.4=
-
trace false

wrapper.app.parameter.5=
-
address itrax_test

wrapper.app.parameter.6=
-
port 9001


Modify

\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
runManager.bat


so the java
command run i
uses “
itrax_production


rather than “localhost”

java
-
classpath
%1
\
li
b
\
db
\
hsqldb.jar;%DLC%
\
java
\
jdbc.jar;%1
\
lib
\
db
\
ojdbc14.jar;%1
\
lib
\
d
b
\
sqljdbc.jar;%1
\
lib
\
db
\
jt400.jar org.hsqldb.util.DatabaseManager
-
driver org.hsqldb.jdbcDriver
-
url
JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
9

of
20


jdbc:hsqldb:hsql://
itrax_production:9001

-
user highway
-
password
highway


Modify “
\
TRAXi3
_Test
\
iTRAX
\
highway
\
db
\
runManager.bat
” so the java command run
iuses “itrax_test” rather than “localhost”

java
-
classpath
%1
\
lib
\
db
\
hsqldb.jar;%DLC%
\
java
\
jdbc.jar;%1
\
lib
\
db
\
ojdbc14.jar;%1
\
lib
\
d
b
\
sqljdbc.jar;%1
\
lib
\
db
\
jt400.jar org.hsqldb.util.DatabaseMana
ger
-
driver org.hsqldb.jdbcDriver
-
url jdbc:hsqldb:hsql://
itrax_test:9001

-
user highway
-
password highway



2. Change “highway.properties”

All connections to the Highway database are made by using the connection details in
highway.properties.


Single Insta
nce Detail:

highway.db.url=jdbc:hsqldb:hsql://
localhost


Multiple Instance Detail:

highway.db.url=jdbc:hsqldb:hsql://
192.168.11.123:9001



Modify “
\
TRAXi3_Production
\
iTRAX
\
highway.properties
” so that the property
“highway.db.url” points to the “itrax_produ
ction” logical server:

highway.db.url=jdbc:hsqldb:hsql://
itrax_production


Modify “
\
TRAXi3_Test
\
iTRAX
\
highway.properties
” so that the property “highway.db.url”
points to the “itrax_test” logical server:

highway.db.url=jdbc:hsqldb:hsql://
itrax_test


Modify

\
TRAXi3_Production
\
iTRAX
\
highway.properties
” so that the property

highway.xslpath
” points to the
IP address rather than the logical server name
:

highway.xslpath=http://
192.168.11.155
:8080/HighwayConsole/xsl/


Modify “
\
TRAXi3_Production
\
iTRAX
\
highway.prop
erties
” so that the property

highway.xslpath
” points to the
IP address rather than the logical server name
:

highway.xslpath=http://
192.168.11.15
6
:8080/HighwayConsole/xsl/


JBoss
:


JBoss needs to be started with a “
-
b” switch which will inform JBoss as to
which IP it is to bind to.


Modify “
\
TRAXi3_Production
\
iTRAX
\
jboss
\
bin
\
run.bat
” so the line details the
itrax_production server as the bind address:

"%JAVA%" %JAVA_OPTS% "
-
Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%"
-
Dproperties.dir=%ITRAX_HOME%
-
Dfile.enc
oding=UTF
-
8
-
Djboss.partition.name=itrax_test %STARTHIGHWAY%
-
classpath
"%JBOSS_CLASSPATH%" org.jboss.Main %*
-
b itrax_production


Modify “
\
TRAXi3_Test
\
iTRAX
\
jboss
\
bin
\
run.bat
” so the line details the itrax_test server
as the bind address:

"%JAVA%" %JAVA_O
PTS% "
-
Djava.endorsed.dirs=%JBOSS_ENDORSED_DIRS%"
-
Dproperties.dir=%ITRAX_HOME%
-
Dfile.encoding=UTF
-
8
-
JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
10

of
20


Djboss.partition.name=itrax_test %STARTHIGHWAY%
-
classpath
"%JBOSS_CLASSPATH%" org.jboss.Main %*
-
b itrax_test


Modify “
\
TRAXi3_Production
\
iTRAX
\
service
\
WrapperJBossService.conf” so there is a bind
parameter specified:

# Application parameters. Add parameters as needed starting from 1

wrapper.app.parameter.1=org.jboss.Main

wrapper.app.parameter.2=
-
Dproperties.dir=%ITRAX_HOME%

wrapper.app.parameter.3=
-
Djb
oss.partition.name=itrax_production

wrapper.app.parameter.4=
-
Dstart.highway=YES

wrapper.app.parameter.5=
-
Dfile.encoding=UTF
-
8

wrapper.app.parameter.6=
-
Dperform.file.cleanup=yes

wrapper.app.parameter.7=
-
Dcleanup.xml.file=%ITRAX_HOME%
\
data
\
cleanup
\
FilesToBeR
emoved.xml

wrapper.app.parameter.8=
-
b itrax_production


Modify “
\
TRAXi3_Test
\
iTRAX
\
service
\
WrapperJBossService.conf” so there is a bind parameter
specified:

# Application parameters. Add parameters as needed starting from 1

wrapper.app.parameter.1=org.jbo
ss.Main

wrapper.app.parameter.2=
-
Dproperties.dir=%ITRAX_HOME%

wrapper.app.parameter.3=
-
Djboss.partition.name=itrax_production

wrapper.app.parameter.4=
-
Dstart.highway=YES

wrapper.app.parameter.5=
-
Dfile.encoding=UTF
-
8

wrapper.app.parameter.6=
-
Dperform.file.c
leanup=yes

wrapper.app.parameter.7=
-
Dcleanup.xml.file=%ITRAX_HOME%
\
data
\
cleanup
\
FilesToBeRemoved.xml

wrapper.app.parameter.8=
-
b itrax_test



Both the file “
\
TRAXi3_Production
\
iTRAX
\
jboss
\
server
\
default
\
deploy
\
jms
\
uil2
-
service.xml
” and “
\
TRAXi3_Test
\
iTRAX
\
j
boss
\
server
\
default
\
deploy
\
jms
\
uil2
-
service.xml
” should be modified so that the line:


<attribute name="BindAddress">localhost</attribute>


is replaced with …


<attribute name="BindAddress">
${jboss.bind.address}
</attribute>


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
11

of
20


JMS Database:

The embedded dat
abase is what is used by default to persist JMS messages. This database is
created and started when JBoss starts and is hosted within the JBoss JVM. By default the
database is available on port 1701.


1. Change “
TRAXi3_Production
\
iTRAX
\
jboss
\
server
\
default
\
deploy
\
hsqldb
-
ds.xml


This file

details the default datasource to be used by JBoss.


Change the line:

<connection
-
url>jdbc:hsqldb:hsql://127.0.0.1:1701</connection
-
url>


to

<connection
-
url>jdbc:hsqldb:hsql://
192.168.11.155
:1701</connection
-
url>


When JBos
s starts up it can be made bind to an IP using the
-
b switch. To make use of this you
need to add the line in bold as shown below to the existing mbean definition in hsqldb
-
ds.xml:


<mbean code="org.jboss.jdbc.HypersonicDatabase"


name="jboss:service=
Hypersonic">


<attribute name="Port">1701</attribute>


<attribute name="BindAddress">${jboss.bind.address}</attribute>


<attribute name="Silent">true</attribute>


<attribute name="Database">default</attribute>


<attribute name="Trace">f
alse</attribute>


<attribute name="No_system_exit">true</attribute>


</mbean>


2. Change “
TRAXi3_Test
\
iTRAX
\
jboss
\
server
\
default
\
deploy
\
hsqldb
-
ds.xml


This file details the default datasource to be used by JBoss.


Change the line:

<connection
-
url>jdb
c:hsqldb:hsql://127.0.0.1:1701</connection
-
url>


to

<connection
-
url>jdbc:hsqldb:hsql://
192.168.11.156
:1701</connection
-
url>


When JBoss starts up it can be made bind to an IP using the
-
b switch. To make use of this you
need to add the line in bold as show
n below to the existing mbean definition in hsqldb
-
ds.xml:


<mbean code="org.jboss.jdbc.HypersonicDatabase"


name="jboss:service=Hypersonic">


<attribute name="Port">1701</attribute>


<attribute name="BindAddress">${jboss.bind.address}</attrib
ute>


<attribute name="Silent">true</attribute>


<attribute name="Database">default</attribute>


<attribute name="Trace">false</attribute>


<attribute name="No_system_exit">true</attribute>


</mbean>



[Technical Notes:
http://jira.jboss.com/jira/browse/JBAS
-
2371;jsessionid=41FFD80EDCDEA685385B436ED2292B3E?page=all
]


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
12

of
20


Need to upgrade a JBoss file



hsqldb
-
plugin.jar
”.


Replace

\
TRAXi3_Production
\
iTRAX
\
jboss
\
server
\
default
\
lib
\
hsqldb
-
plugin.jar
” and
TRAXi3_
Test
\
iTRAX
\
jboss
\
server
\
default
\
lib
\
hsqldb
-
plugin.jar
” with “
hsqldb
-
plugin.jar
” found at


ftp://www.precision.ie/releases/iTRAX/Release
-
1.5/service
-
packs/SP7/hsqldb
-
plugin.jar


Alternative Options:

(a)

Use different ports for each instance of JBoss.

(b)

Use an Oracle or MS SQL database to persist messages.



3
. Modify Highway Settings
:

Highway connects to this embedded database in order to count the messages on a queue.
Changing the above xml file will require changing the following Highway settings.


PERSISTENCE_LOCATION

If the bind address or port is changed then the URL to connect t
o the HSQL database
should be modified accordingly.

The value in the “Production” and “Test” database should
be changed accordingly.




If the database is changed to be an Oracle or MS SQL database then the URL also need
to change.


(a)

PERSISTENCE_TYPE

If th
e database is changed to be an Oracle or MS SQL database then the value needs to
change to DATABASE_ORACLE or DATABASE_MSSQL.


4. Modify Highway Server Details:

The server records detail the hostname to be used when connecting to a JMS queue. By default
th
ese will be localhost but should be changed to point to the logical server name. Production and
Test values should be changed.


JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
13

of
20




JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
14

of
20


cTRAX Listener
:

The cTRAX listener uses entries in the registry to detail how it should connect to JBossMQ. In
cases where
there is a need to define different connections one can suffix the Properties with a
broker id code. The system value that defines the target the listener should connect to should
also have a broker id specified using the property key “BROKER_ID”.


Single
Instance:





JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
15

of
20


Multiple Instances:





Tip: To create the new registry entries you can export the exiting registry values to a text file,
update the text file and then import (or double click in file explorer) to get the new values into the
registry.

Be
low is an export of the Production and Test Property registry values.


Windows Registry Editor Version 5.00


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION]


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION
\
java.nami
ng.factory.initial]

@="org.jnp.interfaces.NamingContextFactory"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION
\
java.naming.factory.url.pkgs]

@="org.jboss.naming:org.jnp.interfaces"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Proper
ties
-
PRODUCTION
\
java.naming.provider.url]

@="itrax_production:1099"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION
\
java.naming.rmi.security.manager]

JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
16

of
20


@="yes"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION
\
jndi]

@=
"yes"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
PRODUCTION
\
queue.connectionfactory.name]

@="ConnectionFactory"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST]


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST
\
ja
va.naming.factory.initial]

@="org.jnp.interfaces.NamingContextFactory"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST
\
java.naming.factory.url.pkgs]

@="org.jboss.naming:org.jnp.interfaces"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Prope
rties
-
TEST
\
java.naming.provider.url]

@="itrax_test:1099"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST
\
java.naming.rmi.security.manager]

@="yes"


[HKEY_LOCAL_MACHINE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST
\
jndi]

@="yes"


[HKEY_LOCAL_MACH
INE
\
SOFTWARE
\
HighwayConnector
\
Properties
-
TEST
\
queue.connectionfactory.name]

@="ConnectionFactory"



iTRAX
:


Modify “
\
TRAXi3_Production
\
iTRAX
\
itrax
.properties
” so that the property

trax
.xslpath
” points to the
IP address rather than the logical server name
:

trax
.xslpath=http://
192.168.11.155
:8080/
trax
/xsl/


Modify “
\
TRAXi3_Production
\
iTRAX
\
itrax
.properties
” so that the property

trax
.xslpath
” points to the
IP address rather than the logical server name
:

trax
.xslpath=http://
192.168.11.15
6
:8080/
trax
/xsl/



Win
dows Services
:

The iTRAX installer will not have added separate windows services for the two instances of
JBoss. Instead the first set of services will have been overwritten by the second install. In fact it
would appear the JBoss and Highway Database serv
ices are overwritten but the cTRAX Listener
services are not. It is best to remove all iTRAX service entries and add them manually.


1. Remove the installed services.

Run “
\
TRAXi3_Production
\
iTRAX
\
service
\
WrapperUninstallJBossService.bat
”.

This removes the


iTRAX
-
(JBoss)
” service.


Run

\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
WrapperUninstallHighwayDatabaseServ
ice.bat
”.

JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
17

of
20


This removes the “
iTRAX
-
(Highway_Database)
” service.


The cTRAX Listener services can be removed by running a Window command window, changing
d
irectory to “
\
TRAXi3_Production
\
iTRAX
\
highway
\
connectors
\
Service
” and running
the “
svc
” utility.



This will remove the
iTRAX
-
(TRAX_Highway_Listener_
[N]
)

services, where [N] can be 01


10.


Once finished there should be no services beginning with “iTRAX”

listed in the Services windo.




2. Add the JBoss services.


Modify “
\
TRAXi3_Production
\
iTRAX
\
service
\
WrapperJBossService.conf” so the service name and
display name include the word “PRODUCTION”.


# Name of the service

wrapper.ntservice.name=iTRAX
-
[PRODU
CTION]
-
(JBoss)


# Display name of the service

JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
18

of
20


wrapper.ntservice.displayname=iTRAX
-
[PRODUCTION]
-
(JBoss)


Run “
\
TRAXi3_Production
\
iTRAX
\
service
\
WrapperInstallJBossService.bat
”.

This adds the “iTRAX
-
[PRODUCTION]
-
(JBoss)” service.



Modify “
\
TRAXi3_
Test
\
iTRAX
\
service
\
WrapperJBossService.conf” so the service name and
display name include the word “
TEST
”.


# Name of the service

wrapper.ntservice.name=iTRAX
-
[
TEST
]
-
(JBoss)


# Display name of the service

wrapper.ntservice.displayname=iTRAX
-
[
TEST
]
-
(JBoss)


Run “
\
TRAX
i3_
Test
\
iTRAX
\
service
\
WrapperInstallJBossService.bat
”.

This adds the “iTRAX
-
[
Test
]
-
(JBoss)” service.



3. Add the Highway services.


Modify “
\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
WrapperHighwayDatabaseService.conf
” so the
service name and display name includ
e the word “PRODUCTION”.


# Name of the service

wrapper.ntservice.name=

iTRAX
-
[PRODUCTION]
-
(Highway_Database)


# Display name of the service

wrapper.ntservice.displayname=

iTRAX
-
[PRODUCTION]
-
(Highway_Database)


Run

\
TRAXi3_Production
\
iTRAX
\
highway
\
db
\
Wrap
perInstallHighwayDatabaseService.bat
”.

This adds the “iTRAX
-
[PRODUCTION]
-
(
Highway_Database
)” service.



Modify “
\
TRAXi3_
Test
\
iTRAX
\
highway
\
db
\
WrapperHighwayDatabaseService.conf
” so the service
name and display name include the word “
TEST
”.


# Name of the s
ervice

wrapper.ntservice.name=

iTRAX
-
[
TEST
]
-
(Highway_Database)


# Display name of the service

wrapper.ntservice.displayname=

iTRAX
-
[
TEST
]
-
(Highway_Database)


Run “
\
TRAXi3_
Test
\
iTRAX
\
highway
\
db
\
WrapperInstallHighwayDatabaseService.bat
”.

This adds the “iTRAX
-
[
TEST
]
-
(
Highway_Database
)” service.



4. Add the cTRAX Listener services.


Add the Production Listener services by opening a Windows command window and changing
directory to “
\
TRAXi3_Production
\
iTRAX
\
highway
\
connectors
\
Service
”.


Run the following command




JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
19

of
20


srvstart install iTRAX
-
[PRODUCTION]
-
(TRAX_Highway_Listener_
[
n
]
)
-
c
E
:
\
TRAXi3_Production
\
iTRAX
\
highway
\
connectors
\
Service
\
listener
[N]
\
traxlistenerservice.cf


where [n] can be “1” to “10”.

where [N] can be “01” to “10”.



Add the
Test

Listener services b
y opening a Windows command window and changing directory
to “
\
TRAXi3_
Test
\
iTRAX
\
highway
\
connectors
\
Service
”.


Run the following command …


srvstart install iTRAX
-
[
TEST
]
-
(TRAX_Highway_Listener_
[n]
)
-
c
E
:
\
TRAXi3_
Test
\
iTRAX
\
highway
\
connectors
\
Service
\
listene
r
[N]
\
traxlistenerservice.cf


where [n] can be “1” to “10”.

where [N] can be “01” to “10”.



JBoss How To
How to Setup Mulpil
e JBoss Instances on a Single Server

Issue 1.
1


Page
20

of
20


Miscellaneous
:

1.

The following Highway Settings should be updated to point to the correct instance of
JBoss Web and the JBoss install.


HIGHWAY_CONSOLE_URL

NOTIFY_E
RROR_LOG_ATTACHMENT



Follow Up
Notes
:


A fix to the installer will be added so that the need to manually remove and add new Windows
Services will no longer be necessary.