Networks

 

---

So far this book has covered creating channels between your system and any other system with which you need to have communications, and creating multi-hop channels to systems where you have no direct connections.

 

Channel and transmission queue names

You can give transmission queues any name you like, but to avoid confusion, you can give them the same names as the destination queue manager names, or queue manager alias names, as appropriate, to associate them with the route they use. This gives a clear overview of parallel routes that you create through intermediate (multi-hopped) queue managers.

All channel names may still contain their transmission queue names, but they must be qualified to make them unique.

For example, at LONDON, there is a AMSTERDAM channel coming from PARIS, and a AMSTERDAM channel going to AMSTERDAM. To make the names unique, the first one may be named 'AMSTERDAM_from_PARIS', and the second may be named 'AMSTERDAM_from_LONDON'. In this way, the channel names show the transmission queue name in the first part of the name, and the direction and adjacent queue manager name in the second part of the name.

Example of channel names

Route name	Queue managers hosting channel	Transmission queue name	Suggested channel name
PARIS	PARIS & LONDON	PARIS (at LONDON)	PARIS.from.LONDON
PARIS	LONDON & AMSTERDAM	PARIS (at AMSTERDAM)	PARIS.from.AMSTERDAM
PARIS_fast	PARIS & LONDON	PARIS_fast (at LONDON)	PARIS_fast.from.LONDON
PARIS_relief	PARIS & LONDON	PARIS_relief (at LONDON)	PARIS_relief.from.LONDON
PARIS_relief	LONDON & AMSTERDAM	PARIS_relief (at AMSTERDAM)	PARIS_relief.from.AMSTERDAM
LONDON	PARIS & LONDON	LONDON (at PARIS)	LONDON.from.PARIS
LONDON_fast	PARIS & LONDON	LONDON_fast (at PARIS)	LONDON_fast.from.PARIS
AMSTERDAM	PARIS & LONDON	AMSTERDAM (at PARIS)	AMSTERDAM.from.PARIS
AMSTERDAM	LONDON & AMSTERDAM	AMSTERDAM (at LONDON)	AMSTERDAM.from.LONDON
AMSTERDAM_relief	PARIS & LONDON	AMSTERDAM_relief (at PARIS)	AMSTERDAM_relief.from.PARIS
AMSTERDAM_relief	LONDON & AMSTERDAM	AMSTERDAM_relief (at LONDON)	AMSTERDAM_relief.from.LONDON

You are strongly recommended to name all the channels in your network uniquely.

 

Network planner

This chapter has discussed application designer, systems administrator, and channel planner functions. Creating a network assumes that there is another, higher level function of network planner whose plans are implemented by the other members of the team.

If an application is used widely, it is more economical to think in terms of local access sites for the concentration of message traffic, using wide-band links between the local access sites.

In this example there are two main systems and a number of satellite systems (The actual configuration would depend on business considerations.) There are two concentrator queue managers located at convenient centers. Each QM-concentrator has message channels to the local queue managers:

1. QM-concentrator 1 has message channels to each of the three local queue managers, PARIS, LONDON, and AMSTERDAM. The applications using these queue managers can communicate with each other through the QM-concentrators.

2. QM-concentrator 2 has message channels to each of the three local queue managers, QM4, QM5, and QM6. The applications using these queue managers can communicate with each other through the QM-concentrators.

3. The QM-concentrators have message channels between themselves thus allowing any application at a queue manager to exchange messages with any other application at another queue manager.