| Red Hat Application Server: JOnAS User Guide | ||
|---|---|---|
| Prev | Chapter 33. Distributed Message Beans in JOnAS 4.1 | Next |
The JORAM servers are part of a single JORAM platform, described by the following a3servers.xml configuration file:
<?xml version="1.0"?>
<config>
<domain name="D1"/>
<server id="0" name="S0" hostname="hostA">
<network domain="D1" port="16301"/>
<service
class="org.objectweb.joram.mom.proxies.ConnectionManager"
args="root root"/>
<service
class="org.objectweb.joram.mom.proxies.tcp.TcpProxyService"
args="16010"/>
<service
class="fr.dyade.aaa.jndi2.distributed.DistributedJndiServer"
args="16400 0"/>
</server>
<server id="1" name="S1" hostname="hostB">
<network domain="D1" port="16301"/>
<service
class="org.objectweb.joram.mom.proxies.ConnectionManager"
args="root root"/>
<service
class="org.objectweb.joram.mom.proxies.tcp.TcpProxyService"
args="16010"/>
<service
class="fr.dyade.aaa.jndi2.distributed.DistributedJndiServer"
args="16400 0 1"/>
</server>
</config> |
This configuration describes a platform made of two servers, "s0" and "s1", hosted by machines "hostA" and "hostB", listening on ports 16010, providing a distributed JNDI service (more information on JORAM's JNDI can be found at http://joram.objectweb.org/current/doc/joram4_0_JNDI.pdf).
Each JOnAS server must hold a copy of this file in its conf/ directory. In their respective jonas.properties files, each must declare joram_for_jonas_ra.rar as a resource to be deployed and each should remove jms from its list of services.