| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| One Channel or More |
« View previous topic :: View next topic » |
| Author |
Message
|
| mikiu |
 Posted: Wed May 11, 2011 9:55 am Post subject: One Channel or More |
 |
|
Acolyte
Joined: 23 Jul 2002
Posts: 61
Location: toronto
|
Hello wise and gentle MQ masters,
The application is written in C with MQI it is deployed on AIX 5.3 with MQ clients V5.3 connecting to an AIX queue manager V6.0.1. Each of the > 200 AIX servers, with their respective C binaries has a config file that has information about the queue manager, IP address, channels name, etc. The message volume is not terribly high (~300.000 /day).
In your opinion, is there a lot to gain from creating a number of channels to be used by this type of an application v. all using the same channel?
I am looking forward for your answer and the discussion to follow, in my experience with this forum it will be instructive and witty.
regards,
Mocco |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed May 11, 2011 10:22 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
If I've understood your post, you have 200+ AIX boxes, each intending to run a single client-bindings MQ application, and you have a Client Channel Definition Table (CCDT) with all of the possible connections defined on each AIX box.
And, you are asking if 300,000 messages flowing to one SVRCONN channel is OK.
Did I understand your question?
_________________
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 |
|
|
| mvic |
| Posted: Wed May 11, 2011 10:23 am Post subject: Re: One Channel or More |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
Hi there.
Use more channels if you think it will help.
Is there a problem you are trying to solve? |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed May 11, 2011 10:35 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the 200 MQ Client servers all connect to the same QM over the same client channel name, you will actually have 200 separate instances of that same channel name.
Use separate and different channel names if you have separate and different channel requirements, like different SSL certs, or MCAUSER ID values, or any other parameters, that for some reason needs to be different for some or each of the 200 clients
You could create 200 separate channel definitions, and have each of the 200 MQ Clients use their own. But if you go that route for some reason, then you have to insure each client can only connect to its own channel, so that means unique SSL or Security Exits for each.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Wed May 11, 2011 10:46 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
I remember one of such scenarios, where vb and c client apps were trying to connect to primary server mq qmgr, and they used to use separate client/server conn. channels to connect to it (using ccdt) , each of them had unique mcauser on it.
as message vol. is not too high on your system ( ~ 300 per day ) , you can use the same channel (unless you are facing some issues on it with connection) Or you can have separate channels for each of those as Peter suggested.
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed May 11, 2011 3:35 pm Post subject: Re: One Channel or More |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mikiu wrote: |
Hello wise and gentle MQ masters,
The application is written in C with MQI it is deployed on AIX 5.3 with MQ clients V5.3 connecting to an AIX queue manager V6.0.1. Each of the > 200 AIX servers, with their respective C binaries has a config file that has information about the queue manager, IP address, channels name, etc. The message volume is not terribly high (~300.000 /day).
In your opinion, is there a lot to gain from creating a number of channels to be used by this type of an application v. all using the same channel? |
MQ will happily work with thousands of remote Clients all connecting in on the same SVRCONN channel. There are no restrictions or effeciency considerations that you really need to be concerned about, other than some memory and CPU usage on the Queue Manager to manage each connection. See the MQ Performance Report SupportPacs.
Typical reasons for using multiple channels are based on segregation of roles or location of the client apps. Role based segregation will usually have each SVRCONN running with a different MCA UserId or SSL settings to control what queues they can access. Location based segregation could be based on state, city or office. This makes it easier to diagnose network problems and forceably disconnect groups of users if this is ever required.
HTH,
_________________
Glenn |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed May 11, 2011 3:42 pm Post subject: Re: One Channel or More |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9470
Location: US: west coast, almost. Otherwise, enroute.
|
| gbaddeley wrote: |
| mikiu wrote: |
Hello wise and gentle MQ masters,
The application is written in C with MQI it is deployed on AIX 5.3 with MQ clients V5.3 connecting to an AIX queue manager V6.0.1. Each of the > 200 AIX servers, with their respective C binaries has a config file that has information about the queue manager, IP address, channels name, etc. The message volume is not terribly high (~300.000 /day).
In your opinion, is there a lot to gain from creating a number of channels to be used by this type of an application v. all using the same channel? |
MQ will happily work with thousands of remote Clients all connecting in on the same SVRCONN channel. There are no restrictions or effeciency considerations that you really need to be concerned about, other than some memory and CPU usage on the Queue Manager to manage each connection. See the MQ Performance Report SupportPacs.
Typical reasons for using multiple channels are based on segregation of roles or location of the client apps. Role based segregation will usually have each SVRCONN running with a different MCA UserId or SSL settings to control what queues they can access. Location based segregation could be based on state, city or office. This makes it easier to diagnose network problems and forceably disconnect groups of users if this is ever required.
HTH, |
Instructive, yes; but not at all witty. 
_________________
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 |
|
|
| mikiu |
| Posted: Wed May 11, 2011 4:01 pm Post subject: thank y'all |
|
|
Acolyte
Joined: 23 Jul 2002
Posts: 61
Location: toronto
|
You have been a lot of help ... I am pleased.
It is now clear that we can use One Channel (not more).
M. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed May 11, 2011 4:22 pm Post subject: Re: One Channel or More |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| bruce2359 wrote: |
| Instructive, yes; but not at all witty. |
In 13 years of using, developing and supporting MQ at several large companies I could tell some real horror stories about MQ clients and channels, mostly due to bad app design. 
Java MQ client app: Knock knock
Queue Manager: Who's there?
Java MQ client app: no one in particular [blank userid]
Queue Manager: Oh really? Welcome.. You can have full access to everything.
_________________
Glenn |
|
| 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
|
|
|
|
