3.8 Determining the configuration for asynchronous communication between servers

This section describes the system configuration when there is an asynchronous communication between servers using a Message-driven Bean. The Message-driven Bean is the access point.

System configurations where a Message-driven Bean is used for asynchronous communication include the system configurations using Cosminexus JMS provider, system configurations using TP1/Message Queue, and system configurations using Cosminexus RM. JMS provider and Cosminexus RM are component software of Application Server. In a system using Cosminexus RM, you cannot distribute loads using the instance pool of the Message-driven Bean.

Organization of this section
3.8.1 Configuration in which a Message-driven Bean is used as the access point (when using Cosminexus JMS provider)
3.8.2 Configuration in which a Message-driven Bean is used as the access point (when using TP1/Message Queue)
3.8.3 Configuration when using a Message-driven Bean as an access point (when using Cosminexus RM)
3.8.4 Load balancing using the Message-driven Bean instance pool (when using TP1/Message Queue)