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.
About this task
This set of scenarios all use a parent queue manager called QM1, and two child queue managers called QM2, and QM3.
Scenario 1 is split into smaller sections to make the process easier to follow.
Figure 1. Topology diagram showing the relationship between queue managers in a typical publisher/subscribe hierarchy.
Scenario 1 part 1: Create the queue managers
Procedure
Create and start three queue managers called QM1, QM2, and QM3 using the following commands:
Scenario 1 part 2: Point-to-point channel connections
About this task
Establish point-to-point channel connections between queue managers using a queue manager alias with the same name as the parent queue manager.
Procedure
Define a transmission queue and queue manager alias on QM2 to QM1. Define a sender channel to QM1 and a receiver channel for the sender channel created on QM1 for QM2:
Define a transmission queue and queue manager alias on QM3 to QM1. Define sender channel to QM1 and a receiver channel for the sender channel created on QM1 for QM3:
Define a transmission queue and queue manager alias on QM1 to QM2 and QM3. Define sender channel to QM2 and QM3, and a receiver channel for the sender channels created on QM2 and QM3 for QM1:
