| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Moving a full repository to another queue manager |
View previous topic :: View next topic |
| Author |
Message
|
| warrenJ |
 Posted: Tue Jan 10, 2006 3:45 am Post subject: Moving a full repository to another queue manager |
 |
|
Apprentice
Joined: 11 Jan 2004
Posts: 29
Location: AUSTRALIA
|
I’d like to clarify the task as described in the Clustering manual for “Moving a full repository to another queue manager” – as I have to do just that (actually I have to move both, but I’ll do them one at a time).
Step 2 – adds a CLUSSDR to point PARIS to the other full repository NEW YORK
Question: at this point doesn’t PARIS learn the full cluster repository details ?
Step 3 – adds a CLUSSDR at the existing NEW YORK to point to the new full repository at PARIS. The manual states only at this point does PARIS learn about the full repository.
After Step 2 wouldn’t NEW YORK know at this point that PARIS is now a full repository, and as it already holds a CLUSRCVR definition for PARIS wouldn’t it auto-define a CLUSSDR to PARIS and supply a complete list of Cluster definitions?
The Clustering Manual seems to contradict itself …..
In Chapter 4, Cluster Channels, it states:
“The CLUSSDR definitions made on the full repository queue managers are special. All the updates exchanged by the full repositories flow exclusively on these channels. The administrator controls the network of full repositories explicitly. The administrator must make the CLUSSDR definitions on full repository queue managers manually and not leave them to be auto-defined. “
Yet, in Chapter 4, What makes Clustering work ?, it states:
"Defining a cluster-sender channel has the effect of introducing a queue manager to one of the full repository queue managers. The full repository queue manager updates the information in its full repository accordingly. Then it automatically creates a cluster-sender channel back to the queue manager, and sends the queue manager information about the cluster. Thus a queue manager learns about a cluster and a cluster learns about a queue manager."
Just trying to understand how the Cluster channels think.
Cheers. |
|
| Back to top |
|
 |
| sebastianhirt |
| Posted: Tue Jan 10, 2006 6:50 am Post subject: |
|
|
Yatiri
Joined: 07 Jun 2004
Posts: 620
Location: Germany
|
| Quote: |
After Step 2 wouldn’t NEW YORK know at this point that PARIS is now a full repository, and as it already holds a CLUSRCVR definition for PARIS wouldn’t it auto-define a CLUSSDR to PARIS and supply a complete list of Cluster definitions?
|
It does know about the Cluster. But "Full Repository information" can only be exchanged on manually defined Cluster Sender Channels. Therefore you need to have manually defined Cluster Senders both ways, on Full Repository to Full Repository communications.
Try to set up a little cluster on a testsystem, and do some testing. This makes it way easier to understand.
Hope this helps
Sebastian |
|
| Back to top |
|
|
| Ivans |
| Posted: Wed Jan 11, 2006 4:37 am Post subject: |
|
|
Apprentice
Joined: 03 Jan 2006
Posts: 48
Location: Hursley
|
Before step 1 NEW YORK and PARIS both exist in the cluster. As NEW YORK is a full repos and PARIS a partial repos , there will be an auto-defined channel from NEW YORK to PARIS. So PARIS is aware that NEW YORK is a full repos and both queue managers are able to communicate.
After step 2, not much has changed, and no general cluster information can be sent from NEW YORK to PARIS as there is no manually defined channel from NEW YORK to PARIS. Full repositories only share general cluster information via manually defined cluster channels.
Once the channel from NEW YORK to PARIS is defined (step 3), NEW YORK shares all the cluster information with PARIS.
Now to explain the contradiction... Actually, full repositories do use auto-defined cluster sender channels to share cluster information, but only where a manually defined channel exists too. This type of cluster sender is known as a CLUSSDRB, as detailed below (from MQSC reference manual)...
CLUSSDR
As a cluster-sender channel from an explicit definition.
CLUSSDRA
As a cluster-sender channel by auto-definition alone.
CLUSSDRB
As a cluster-sender channel by auto-definition and an explicit definition.
To access the definition type info use "DIS CLUSQMGR(*) DEFTYPE".
I hope this helps clarify the behaviour. Shout if it doesn't.
Cheers,
Ian
WebSphere MQ |
|
| 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
|
|
|
|
