This subsection describes the load balancing according to the instance pool count of Message-driven Beans for each J2EE server, when the access point component is a Message-driven Bean.
Load balancing with this configuration is possible only when you access Message-driven Beans using TP1/Message Queue. When accessing Message-driven Beans using Cosminexus RM, the load balancing with the instance pool of Message-driven Beans is not possible.
In this configuration, the access point of the application running on the J2EE server is a Message-driven Bean, and this configuration can be used for message-driven systems. When the message from the Message Queue client arrives in TP1/Message Queue on the Message Queue server, the Message-driven Bean is invoked depending on the number of instances of Message-driven Beans pooled on the J2EE server.
The following figure shows an example of the configuration of load balancing for Message-driven Beans:
Figure 3-45 Example of configuration of load balancing for Message-driven Bean
Note: For other legend items, see 3.2 Description of the system configuration.
The required software and processes to be started when balancing the load using the instance pool of Message-driven Beans is the same as for configurations in which a Message-driven Bean is used as the access point. For details, see 3.8.2 Configuration in which a Message-driven Bean is used as the access point (when using TP1/Message Queue).