You can configure multiple service integration messaging
engines to distribute workload across multiple application servers.
This allows you to scale out your system to handle larger workloads.
Subtopics:
Workload sharing with queue destinations
If you add a server cluster to a service integration bus
and deploy one or more messaging engines to the cluster, you can configure
the cluster bus member for scalability. The messaging engines in the
cluster bus member share the messaging workload associated with queue
destinations deployed to the cluster.
Workload sharing with publish/subscribe messaging
In publish/subscribe messaging, the messaging system sends
one copy of every published message to each matching subscription.
Subscribers, that is, applications that consume publish/subscribe
messages, consume those messages from an individual subscription.
To balance workload across multiple instances of an application, for
example when an application runs in a server cluster, all instances
of the application must use the same subscription.