| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ Configuration |
« View previous topic :: View next topic » |
| Author |
Message
|
| solomon_13000 |
 Posted: Mon Jul 21, 2008 6:20 pm Post subject: MQ Configuration |
 |
|
Master
Joined: 13 Jun 2008
Posts: 284
|
| According to the MQ Configuration manual things like hub and spoke, star, clustering was mentioned. In the context of MQ is this known as a network topology?. Are they being used to setup MQ?. So basically if I have setup a gateway to a cluster, now this will be refered to as a "star" or "spoke and hub" setup?. Also within a cluster I have the full repository and the partial repository, now is this also known as a "star" or "hub and spoke" setup?. Are there Bus and Ring setup?. |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jul 22, 2008 7:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Briefly:
You can use the terms topology and/or configuration to describe how you have configured your queue managers. The physical network topology may or may not be configured the same way.
Hub-and-spoke = star. In this configuration, all qmgrs connect to a central hub qmgr. The hub is responsible for forwarding messages to one of the other qmgrs connected to the hub. Often, this is the only function of a hub qmgr - no application programs execute on the hub; but this is not necessarily so.
Bus topology describes a qmgr network where each qmgr is connected daisy-chain style to the next qmgr in the in the network.
WMQ channels are point-to-point. So, in the case of a hub-and-spoke topology, all qmgrs have a point-to-point channel pair (sender-receiver) to the hub. A message sent from one qmgr (spoke) arrives at the hub; and then the hub routes the message to the destination qmgr on a spoke.
In a bus topology, all qmgrs have a channel pair to the next nearest qmgr(s). In this configuration, a message may have to traverse one or more qmgrs to arrive at its destination qmgr.
Clusters are groups of qmgrs that can perform the same workload. Clusters are used for workload balancing, and to a small extent, application failover. (This aspect of clusters is discussed in many posts here.) We usually refer to clusters as architecture, rather than topology.
In clusters, each qmgr must have a CLUSSDR channel to a full repository. Some (two) of the qmgrs may be designated (by qmgr attribute) to be full repositories. Those qmgrs not designated to be full repositories are partial repositories. Repositories hold information about objects designated (by object attribute) to be part of the cluster (available to all qmgrs in the cluster). Message flow is point-to-point from sending qmgr to receiving qmgr.
You may architect isolated clusters (clusters that don't interact with other clusters), interconnected clusters (where a gateway qmgr can see other clusters), and overlapping clusters.
IBM course MQ250 Architecting WMQ Clusters is a wonderful, hands-on lab course, for those responsible for designing and supporting clusters.
You can impllement any or all of these configurations in your qmgr network.
Refer to the WMQ Intercommunications manual, and the WMQ Queue Manager Clusters manual.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
