ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Clustering » MQ Cluster configuration

Post new topic  Reply to topic
 MQ Cluster configuration « View previous topic :: View next topic » 
Author Message
samgunddi
PostPosted: Fri Aug 01, 2008 9:37 am    Post subject: MQ Cluster configuration Reply with quote

Acolyte

Joined: 17 May 2004
Posts: 54

We have four queue managers in a cluster CLUS01. Queue managers GTW01 & BRK01 are full repository, CFG01 & GTW30 are partial repository.

WBRK01 has cluster sender channel, TO.GTW01 to GTW01 and cluster receiver channel TO.BRK01.

GTW01 has cluster sender channel, TO.BRK01 to BRK01 and cluster receiver channel TO.GTW01.

CMG01 has cluster sender channel, TO.BRK01 to BRK01 and cluster receiver channel TO.CMG01.

GTW30 has cluster sender channel, TO.BRK01 to BRK01 and cluster receiver channel TO.GTW30.

BRK01 and CFG01 are message broker & configuration manager queue managers and are hosted on a BRK server. GTW01 is hosted on BRK server.

GTW30 serves the need of SAP by an SAP WBI adapter and is hosted on its server. Cluster queues are hosted on BRK01, GTW01 and GTW30. So they have to exchange message back and forth.

SAP server has a different maintains cycle then BRK server. In the event of a scheduled GTW30 down-time, all messages from BRK01 to GTW30 will be stuck on SYSTEM.CLUSTER.TRANSMIT.QUEUE of BRK01.

How do we configure the MQ infrastructure so the message going to GTW01 from BRK01 are not affected?

Thanks in Advance.
_________________
IBM Certified System Administrator
- WebSphere Message Queue V5.3
- WebSphere Message Broker v6.0


Last edited by samgunddi on Fri Aug 01, 2008 10:56 am; edited 1 time in total
Back to top
View user's profile Send private message
exerk
PostPosted: Fri Aug 01, 2008 9:54 am    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

The quick fix is to PUT disable the queue on GTW30, ensure all messages are consumed, then take down the queue manager (note: there must be at least one available queue instance available elsewhere in the cluster).

You might also want to look at...

Quote:
GTW01 has cluster sender channel, TO.BRK01 to BRK01 and cluster receiver channel TO.BRK01.


...but I am assuming this is a copy/paste error.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
sami.stormrage
PostPosted: Fri Aug 01, 2008 11:00 am    Post subject: Reply with quote

Disciple

Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore

And the Bind on Q's is set to NOTFIXED.
_________________
*forgetting everything *


Last edited by sami.stormrage on Fri Aug 01, 2008 11:08 am; edited 1 time in total
Back to top
View user's profile Send private message Yahoo Messenger
samgunddi
PostPosted: Fri Aug 01, 2008 11:06 am    Post subject: Reply with quote

Acolyte

Joined: 17 May 2004
Posts: 54

exerk, good catch it it was a copy/past error.

In case of SAP down (during maintenance) GTW30 will also be down. So i cannot disable the queue. Consider a scenario where message are generated by an app feeding to multiple targets.

One least available queue instance sounds interesting. I have the 2 concerns around it.

1. How/When should the message in this additional instance be routed to the destination queue.

2. Throughput might be reduced.
_________________
IBM Certified System Administrator
- WebSphere Message Queue V5.3
- WebSphere Message Broker v6.0
Back to top
View user's profile Send private message
sami.stormrage
PostPosted: Fri Aug 01, 2008 11:06 am    Post subject: Reply with quote

Disciple

Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore

And the usual practise is to Suspend the Qmgr first and see that all the channel activity seizes before bringing down the Qmgr, so that Qmgrs the Cluster are aware that a particular Qmgr in the network is no longer available.
_________________
*forgetting everything *
Back to top
View user's profile Send private message Yahoo Messenger
samgunddi
PostPosted: Fri Aug 01, 2008 11:10 am    Post subject: Reply with quote

Acolyte

Joined: 17 May 2004
Posts: 54

If I suspend the queue manage the app will still generate the message destined to the GTW30 cluster queue and land in DLQ.
_________________
IBM Certified System Administrator
- WebSphere Message Queue V5.3
- WebSphere Message Broker v6.0
Back to top
View user's profile Send private message
sami.stormrage
PostPosted: Fri Aug 01, 2008 11:13 am    Post subject: Reply with quote

Disciple

Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore

How long has it been since u have restarted ur Broker Qmgr?

And when u say application feeding multiple destinations.. Do u mean to say that u have a Distribution list or Pub-Sub configured?
_________________
*forgetting everything *
Back to top
View user's profile Send private message Yahoo Messenger
exerk
PostPosted: Fri Aug 01, 2008 1:35 pm    Post subject: Reply with quote

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

samgunddi wrote:
exerk, good catch it it was a copy/past error.

In case of SAP down (during maintenance) GTW30 will also be down. So i cannot disable the queue. Consider a scenario where message are generated by an app feeding to multiple targets.

One least available queue instance sounds interesting. I have the 2 concerns around it.

1. How/When should the message in this additional instance be routed to the destination queue.

2. Throughput might be reduced.


If there is only one instance of a queue within a cluster, therefore only one destination, any messages not transmitted before the queue/queue manager becomes unavailable will stack on the S.C.T.Q of the queue manager sending them. As a cluster is primarily aimed at load balancing, there is (generally) more than one instance of a queue within the cluster, hence my suggestion of put disabling the queue.

As far as I can see, if the SAP server is having maintenance applied, as there are no other instances of the queue in the cluster, whatever generates the messages will need to be shut down.

Is there scope to have two SAP servers, and load balance between them, and take them down one at a time for maintenance? (I've not encountered SAP and WMQ, so don't know if that is a stupid question, or not )

I missed this the first time I posted...

Quote:
How do we configure the MQ infrastructure so the message going to GTW01 from BRK01 are not affected?


Did you mean GTW30?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Clustering » MQ Cluster configuration
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.