| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| General questions about FTE/MFT |
« View previous topic :: View next topic » |
| Author |
Message
|
| fswarbrick |
 Posted: Mon Sep 21, 2020 3:23 pm Post subject: General questions about FTE/MFT |
 |
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
Are the following statements all correct? If not, please correct them.
There are three types of MFT queue managers:
A single Coordination Queue Manager
A single Command Queue Manager
One or more Agent Queue Managers
An Agent may have its own specific queue manager, or it may use the coordination queue manager to hold its queues.
You can also have some agents with their own distinct queue managers, while others use the coordination queue manager.
Multiple agents could also share a single Agent queue manager.
One queue manager may function as all of the MFT queue manager types. (Coordination, Command and Agent)
Also, where does the Command QMGR fit in on the diagram on the following page? https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.2.0/com.ibm.mq.pro.doc/topology.htm |
|
| Back to top |
|
 |
| gbaddeley |
| Posted: Mon Sep 21, 2020 10:01 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The statements are all correct.
In other words, there are 3 different functions provided by qmgrs (agent, command, and coord). They may be on separate qmgrs, or combined in any fashion.
If you have a significant number of MFT agents, the coord qmgr usually sits on its own, so it doesn't house any agent or command queues.
The queues for each agent (5 of them, including the command queue) usually sit together on other qmgrs. For transfers to work, all the agent / command qmgrs need to have routing so that the agents can send msgs to each other.
Agents can be run as Clients, so the agent itself does not need to be running on the same host as its qmgr.
_________________
Glenn |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Mon Sep 21, 2020 10:05 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The top 2 boxes. These qmgrs have combined command queues and agent queues. Possibly indicated by the 2 queue symbols in each box.
_________________
Glenn |
|
| Back to top |
|
|
| fswarbrick |
| Posted: Tue Sep 22, 2020 3:19 pm Post subject: |
|
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Sep 23, 2020 3:35 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
The command queues (and agent queues) can be put anywhere, it doesn't matter, as long as the MFT agent app can put/get messages. Configuration convenience (network, physical location, existing MQ infrastructure, channels to/from other MFT agent / command qmgrs) is usually the governing factor.
ie. If the MFT agent is running on the same server as a queue manager, it can use that qmgr, and run in bindings mode. If there is no local qmgr, use a reasonably close qmgr on another server and run in client mode.
| Quote: |
| Or is it more correct to say that each queue manager that acts as an agent queue manager is also a command queue manager? |
This is normally the case, but it doesn't have to be. The main reason is convenience, to have the command queue on the same qmgr as the agent queues. All of the example topologies use this design.
There are actual implementations of 1000+ MFT agents running in client mode on 1000+ servers, and having all their queues on one central qmgr.
_________________
Glenn |
|
| Back to top |
|
|
| fswarbrick |
| Posted: Wed Sep 23, 2020 3:40 pm Post subject: |
|
|
Apprentice
Joined: 07 Jul 2014
Posts: 42
|
| Thanks, Glenn. I'm sure I'll have more questions as I play with this. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Sep 24, 2020 4:10 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| fswarbrick wrote: |
| Thanks, Glenn. I'm sure I'll have more questions as I play with this. |
I suggest that you come up with a design for MQ topology and agent names, and stick to it. Changing coord qmgr and agent / command qmgrs is non trivial, as the config for all the MFT agents needs to be rejigged, and the qmgr node name in transfer commands needs to be updated.
Also, completely separate production agents from other environments.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
