Chapter 33. Distributed Message Beans in JOnAS 4.1
JOnAS release 4.1 dramatically simplifies the use of a distributed JORAM platform from within JOnAS servers. Such a configuration allows, for example, a bean hosted by JOnAS instance "A" to send messages on a JORAM queue, to which a Message-Driven Bean (MDB) hosted by JOnAS instance "B" listens.
The reasons for this progress are:
The JORAM Resource Adapter allows much finer configuration than the JMS service did.
JORAM provides a distributed JNDI server that enables JOnAS instances to share information.
 | Note |
|---|---|
Before you proceed with this chapter, you should review Section 3.7.1 JORAM Resource Adapter. |
33.1. Scenario and General Architecture
The following scenario and general settings are proposed:
Two instances of JOnAS are run (JOnAS "A" and JOnAS "B"). JOnAS A hosts a simple bean that provides a method for sending a message on a JORAM queue. JOnAS B hosts a Message-Driven Bean that listens on the same JORAM queue.
Each JOnAS instance has a dedicated, collocated JORAM server: server "s0" for JOnAS A, "s1" for JOnAS B. Those two servers are aware of each other.
The queue is hosted by JORAM server s1.
An additional JNDI service is provided by the JORAM servers. This service is used for storing the shared information (basically, the queue's naming reference).