Publish/subscribe hierarchy scenarios

Publish/subscribe hierarchy scenarios

Three scenarios that demonstrate use of publish/subscribe hierarchies. Each of the three scenarios sets up the same simple publish/subscribe topology. In each scenario, the queue managers rely on a different method for connecting to their neighboring queue managers in the hierarchy.

The available publish/subscribe hierarchy scenarios are described in the following subtopics:

Publish/subscribe hierarchy scenario 1: Using point-to-point channels with queue manager name alias
This is the first in a set of three scenarios that set up a publish/subscribe hierarchy in different ways to establish the connection between queue managers. This scenario sets up a publish/subscribe hierarchy that uses point-to-point channels with queue manager name alias.
Publish/subscribe hierarchy scenario 2: Using point-to-point channels with same name for transmission queue and remote queue manager
This is the second in a set of three scenarios that set up a publish/subscribe hierarchy in different ways to establish the connection between queue managers. This scenario sets up a publish/subscribe hierarchy that uses point-to-point channels with the transmission queue name the same as the remote queue manager.
Publish/subscribe hierarchy scenario 3: Using a cluster channel to add a queue manager
This is the third in a set of three scenarios that set up a publish/subscribe hierarchy in different ways to establish the connection between queue managers. This scenario uses a cluster channel to add a queue manager to a hierarchy.
Parent topic: Publish/subscribe scenarios

Related information

Publish/subscribe hierarchies