A cluster bus member with multiple messaging engines
This scenario assumes that all the appservers in the cell belong to one cluster. Multiple messaging engines have been defined for the cluster.
The pros of this topology are:
- The messaging engines in the cluster are highly available.
- The cluster bus member is capable of messaging workload management. A queue point assigned to the cluster bus member is partitioned onto every messaging engine in the cluster and messages delivered into the cluster are distributed between the partitions.
The drawback is that there are some restrictions on the workload management of client connections directly into a cluster.