Defining classes of service
Imagine a university that has a queue manager for each member of staff and each student. Messages between members of staff are to travel on channels with a high priority and high bandwidth. Messages between students are to travel on cheaper, slower channels. We can set up this network using traditional distributed queuing techniques. WebSphere MQ knows which channels to use by looking at the destination queue name and queue manager name.
To clearly differentiate between the staff and students, you could group their queue managers into two clusters as shown in Figure 1. WebSphere MQ will move messages to the meetings queue in the staff cluster only over channels that are defined in that cluster. Messages for the gossip queue in the students cluster go over channels defined in that cluster and receive the appropriate class of service.
Parent topic:
Overlapping clusters
qc11270_
Home
