| Author |
Message
|
| vandemon |
 Posted: Tue Jun 22, 2010 5:55 pm Post subject: client-server VS sender-receiver |
 |
|
Apprentice
Joined: 14 Jun 2010
Posts: 32
|
Which type of connection is better?
In terms of secure, speed n reliability? |
|
| Back to top |
|
 |
| exerk |
| Posted: Tue Jun 22, 2010 11:07 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
It depends on the requirements of the application(s) and above all how stable your network is...your question is one of the 'is the glass half full, or half empty' type.
_________________
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 |
|
|
| vandemon |
| Posted: Tue Jun 22, 2010 11:13 pm Post subject: |
|
|
Apprentice
Joined: 14 Jun 2010
Posts: 32
|
Ok.. I'll clarify...
There is one server n probably multiple clients.
All of them are spread around(as in not conencted as LAN)
So izit better that i joined them using client-server, or use sender-receiver to connect each client with server?
Which one will be more secure, reliable, faster? |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jun 22, 2010 11:21 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Your clarification leads to more obscuration 
If your "...multiple clients..." are just that, WMQ clients, you cannot use a SDR/RCVR pair as they are for queue-manager-to-queue-manager intercommunication. I'm also intrigued by what you mean by "...as in not connected as LAN..."
_________________
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 |
|
|
| vandemon |
| Posted: Tue Jun 22, 2010 11:45 pm Post subject: |
|
|
Apprentice
Joined: 14 Jun 2010
Posts: 32
|
the multiple client also installed with MQ, each client will have a program that will interact with its own MQ.
not connected as LAN which means all the clients are spread accross state. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Jun 22, 2010 11:58 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
My previous comment regards your clarification still holds good 
| vandemon wrote: |
| the multiple client also installed with MQ, each client will have a program that will interact with its own MQ. |
So a 'physical' server has WMQ Server/Client installed, and the application connects to the queue manager configured on it via WMQ Client? And each queue manager needs to connect to the other queue managers? What was the solution designer smoking/drinking/insert-predilection-here when he/she came up with this design?
| vandemon wrote: |
| ...not connected as LAN which means all the clients are spread across state. |
By client here do you mean client queue managers? By "...spread across state..." do you mean a WAN?
_________________
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 |
|
|
| vandemon |
| Posted: Wed Jun 23, 2010 12:18 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2010
Posts: 32
|
| exerk wrote: |
| So a 'physical' server has WMQ Server/Client installed, and the application connects to the queue manager configured on it via WMQ Client? And each queue manager needs to connect to the other queue managers? What was the solution designer smoking/drinking/insert-predilection-here when he/she came up with this design? |
I think I'll explain in this way.
program a is a listener program on server side
program b is a listener program on client side
b is putting msg into client side WMQ
client side WMQ will send msg to server side WMQ using sender-receiver or client-server
a will process the receiving msg and put it back into queue in server side WMQ
b will listen on response queue at client side WMQ
Note:It will be a lot client conencting to the server
Question:So sender-receiver or client-server is better in terms of secure, reliable n speed?
| exerk wrote: |
| By client here do you mean client queue managers? By "...spread across state..." do you mean a WAN? |
Yes.. I meant WAN |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 23, 2010 2:27 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can not use CLNTCONN/SVRCONN channel pairs to connect two queue managers.
You can only use CLNTCONN/SVRCONN channel pairs to connect an application to a queue manager. That application is then known as a "client".
There are several flavors of MQ channels that can be used to connect queue managers. There are no security or speed differences between them. The only case where some flavours are more reliable is when there are special conditions regarding which side of a channel pair is allowed to start the flow of messages.
It is a perfectly reasonable thing to do to design your MQ network with every queue manager being connected by two sender-receiver pairs, and then make changes to use requester-sender or requester-server channel pairs or etc. where you specifically need to use them. |
|
| Back to top |
|
|
| vandemon |
| Posted: Wed Jun 23, 2010 3:51 am Post subject: |
|
|
Apprentice
Joined: 14 Jun 2010
Posts: 32
|
Thanks mqjeff... Appreciate for ur advise...  |
|
| Back to top |
|
|
|
|
