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 » General Discussion » ONe client to many qmgrs

Post new topic  Reply to topic
 ONe client to many qmgrs « View previous topic :: View next topic » 
Author Message
ishu_123
PostPosted: Sun Oct 19, 2014 11:57 am    Post subject: ONe client to many qmgrs Reply with quote

Newbie

Joined: 18 Oct 2014
Posts: 1

Hi,

How to configure one MQ client to communicate to many qmgrs in client server architecture.
Back to top
View user's profile Send private message
bruce2359
PostPosted: Sun Oct 19, 2014 12:06 pm    Post subject: Re: ONe client to many qmgrs Reply with quote

Poobah

Joined: 05 Jan 2008
Posts: 9399
Location: US: west coast, almost. Otherwise, enroute.

ishu_123 wrote:
Hi,

How to configure one MQ client to communicate to many qmgrs in client server architecture.

By communicate, do you mean MQCONNect to multiple qmgrs? Or, do you mean for a single MQ client to connect to one qmgr, and have message go from there to other qmgrs?

You might want to begin your quest by searching here and google for 'mq distributed queuing'.
_________________
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
View user's profile Send private message
PaulClarke
PostPosted: Sun Oct 19, 2014 8:31 pm    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

If you are asking how you can make a client application choose which of a set of back-end Queue Managers to connect to then the simplest approach is to configure a Client Channel Definition Table (CCDT). There are other mechanisms though but to advise we would need to know what your exact requirements are since each method it suitable for different situations. Of course these are all well described in the MQ documentation,

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
ankurlodhi
PostPosted: Wed Oct 22, 2014 2:38 pm    Post subject: Reply with quote

Master

Joined: 19 Oct 2010
Posts: 266

Paul what are the other ways .. will you share.
other then binding and using client connection channel table.
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Oct 22, 2014 10:01 pm    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5849
Location: UK

You should aim to connect your client application to ONE QM, and then arrange for remote queues between that and any others.

Connecting to many QMs at once (or even in series), unless you are coding a MQ tool, would be an unusual and almost certainly a bad design.

Also - aim to keep your connection handle and open queue handles for long periods, don't keep re-connecting. Don't poll queues either. Use MQGET with WAIT or MQ call back.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
PaulClarke
PostPosted: Wed Oct 22, 2014 10:08 pm    Post subject: Reply with quote

Grand Master

Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand

Well, there are a number of ways of getting a client to connect to different backend Queue Managers. These aren't secret, they are fully documented in the manuals.

  • Application specified
    The itself can provide the full channel definition on the MQCONNX verb itself. This gives the client full power about who to connect to and when. It is therefore the most flexible since the Application can get its configuration from anywhere you like.

  • Active Directory
    If your client is on Windows then you can stiore your channel definitions in Active Directory. I don't get the impression that this is used a great deal but for some people it may be just what is required.

  • Preconnect Exit
    MQ provides a preconnect exit which will read the client channel definitions from an LDAP repository. The advantage of this is that it allows central administration and doesn't require you to code anything. However, you could write your own Preconnect Exit that can read the channel definitions from wherever you like. Again it has the advantage of being dynamic since the set is queried at every connect time.


I hope that helps,

Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » ONe client to many qmgrs
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.