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 » MQ client channel connectivity questions

Post new topic  Reply to topic
 MQ client channel connectivity questions « View previous topic :: View next topic » 
Author Message
thindk00
PostPosted: Wed Oct 19, 2005 2:57 am    Post subject: MQ client channel connectivity questions Reply with quote

Voyager

Joined: 16 May 2001
Posts: 75
Location: UK

Hi,

We're thinking of providing a central WMQ server to our business to allow WMQ client channels to connect to it, rather than them having to need local WMQ servers that their channels need to connect to.

Questions that spring to mind:

1) The WMQ client channels will come in over a WAN link rather than over a LAN link, is this a problem? Is there something that we need to consider? E.g. is there a timeout for the client connection channel that we need to be aware of?
2) We could have hundreds/thousands of client connections to the server. Is there a limit on the number of client connections? Can this be tuned? We're running on Solaris.

TIA,

Kulbir.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Oct 19, 2005 3:22 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You should read the Intercommuncations manual, at least some sections of it, and the Clients manual.

I personally do not feel comfortable with MQ client connections coming in from business partners. I much prefer knowing that they have at least one QM on their side because it implies a certain amount of MQ knowledge and because it provides a larger degree of reliability and isolation.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
PGoodhart
PostPosted: Wed Oct 19, 2005 3:28 am    Post subject: Reply with quote

Master

Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA

"I personally do not feel comfortable with MQ client connections coming in from business partners. I much prefer knowing that they have at least one QM on their side because it implies a certain amount of MQ knowledge and because it provides a larger degree of reliability and isolation."
- Unless I supply/configure the MQ client software I agree completely. There are too many things to go wrong that you get into a "what-does-this-button-do" duel with the other side's developers. This doesn't mean it isn't possible, just possibly ill advised. Read the manuals Jeff suggested and see if you agree....
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin
Back to top
View user's profile Send private message
thindk00
PostPosted: Wed Oct 19, 2005 3:38 am    Post subject: Reply with quote

Voyager

Joined: 16 May 2001
Posts: 75
Location: UK

Thanks Guys, I'll run through the manuals.

The client connections would be from internal business applications that would be tested thoroughly prior to entering the relevant environments. I'm just trying to find technical reasons for why it may cause a problem (e.g. use of WAN link, # of connections, etc).

Cheers.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Oct 19, 2005 3:44 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Client connections are, by nature, less reliable than bindings connections and subject to network issues. If your network is stable, and your WAN links are reasonably reliable, you might be fine. If your WAN links are slow, you're much better off putting at least gateway QMs on each end.

Also, it is not possible to do two-phase commit with a client connection. You have to pay for the Extended Transactional Client, and that costs the same as a qmgr. This could be a complete show stopper for using clients for all applications.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
thindk00
PostPosted: Wed Oct 19, 2005 3:48 am    Post subject: Reply with quote

Voyager

Joined: 16 May 2001
Posts: 75
Location: UK

Thanks.

I should have mentioned this, the applications are currently using client connections to communicate with regional WMQ servers and we're looking at replacing the regional servers with a Central server.

We're already using the WAN links to do server <--> server connections and now looking to use the same WAN links for client <--> server.
Back to top
View user's profile Send private message Send e-mail
jefflowrey
PostPosted: Wed Oct 19, 2005 4:07 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Ah.

That's a whole other ball of wax.

You'll need to tune your QM to support the maximum number of connections you need.

And you should run tests to make sure your client connections are reliable enough over the WAN. I want to say lots of tests, but it's probably not that bad.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Tim
PostPosted: Wed Jun 21, 2006 4:58 am    Post subject: Reply with quote

Newbie

Joined: 14 Oct 2005
Posts: 4

Hi,
we are exactly in the same situation since a few years. We have a central MQ server, and external clients connect to us over a WAN
Untill a few months ago this worked perfectly : even over slow iVPN connections. However we recently had serious troubles with a client connecting over ISDN, and the ISDN line was going up and down.
The client application was in a state where it did got an error message (RC 2009) when sending a messages, although the message was send to the MQ server. Client resend the message, resulting in doubles etc. etc.

conclusion : if you want a fully waterproof solution over a WAN, go for the MQ server of transactional client
Back to top
View user's profile Send private message Send e-mail
zpat
PostPosted: Wed Jun 21, 2006 5:09 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Client channels are actually very similar operationally to server channels and work fine over a WAN. However MQ applications which rely on client connections MUST be coded to deal with disconnections (MQ RC 2009).

The apps should retry after about 30 secs when RC 2009 is received - if they retry in a tight loop it will severely impact your network and QM.

As a rule of thumb I would trust a Windows based QM to work well with up to 500 concurrent clients, a Unix QM to work with up to 2000 clients and a mainframe to work with up to 10,000 clients.

These are not architectural limits, just my opinions.
Back to top
View user's profile Send private message
thindk00
PostPosted: Wed Jun 21, 2006 5:52 am    Post subject: Reply with quote

Voyager

Joined: 16 May 2001
Posts: 75
Location: UK

Tim - Did you log your problem with IBM? What version of WMQ are you on and which platform?

Thanks.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » MQ client channel connectivity questions
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.