| Author |
Message
|
| cspodapati |
 Posted: Thu Feb 04, 2010 5:26 am Post subject: which channel pairs we have to use and why? |
 |
|
Novice
Joined: 12 Jan 2010
Posts: 20
|
Hi All,
When ever we are defining the channels we have to follow these combinations
Sender-receiver
Requester-server
Requester-sender (callback)
Server-receiver
can any one clarifies in which situation we have to choose which pair, some description is written in intercommunication. Can any one tell me while designing and configuring applications which pair we have to use and WHY?
thanks in advance |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Thu Feb 04, 2010 6:03 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| Can any one tell me while designing and configuring applications which pair we have to use and WHY? |
Read all about this subject in the WMQ Intercommunications manual.
_________________
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 |
|
|
| cspodapati |
| Posted: Thu Feb 04, 2010 7:26 am Post subject: |
|
|
Novice
Joined: 12 Jan 2010
Posts: 20
|
| I red intercommunication, in that it is mentioned how each pairs work, but my question is in which situation these pairs will be used, why we cant use sender-receiver combination for every requirement. in which conditions we will use other pairs. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Feb 04, 2010 7:33 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
every channel combination has special features, like the "callback" which you wrote in your first post in this thread.
if you want to use that feature, you have to use that channel combination. if not, then use the simple "sender - receiver" combination.
there is no global rule for "every requirement"
_________________
Regards, Butcher |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Feb 04, 2010 7:34 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| cspodapati wrote: |
| ...why we cant use sender-receiver combination for every requirement... |
Because it may not be appropriate to the solution for the project.
| cspodapati wrote: |
| ...in which conditions we will use other pairs? |
When the solution for the project demands it.
_________________
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 |
|
|
| bruce2359 |
| Posted: Thu Feb 04, 2010 8:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
This is all in the Intercomm manual:
Briefly, channel-types that start with the letter 's' can get messages from transmission queues, and send them down a channel. Channel-types that start with the letter 'r' can remove messages from the channel, and put them in queues. Sender-receiver channel-type pair is an example.
So messages flow from 's' to 'r' channel-types.
A server channel-type implies that the qmgr is unattended - no one there to issue commands to start the channel, for example. A server-requester channel-type pair allows the 'r' end of the channel to request that the server end start the channel, and begin sending messages back to the requester.
The svrconn channel-type is a special-case. This type of channel services WMQ client applications.
The type of channel pairs you select needs to match your network design.
Again, refer to the Intercommunication manual for design guidelines.
_________________
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: Thu Feb 04, 2010 1:42 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| cspodapati wrote: |
| why we cant use sender-receiver combination for every requirement. |
SDR/RCVR is sufficient for most requirements.
If the SDR/RCVR pairing meets all your requirements, then look no further.  |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Feb 04, 2010 3:10 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mvic wrote: |
| If the SDR/RCVR pairing meets all your requirements, then look no further. |
You could look at MQ Clusters 
_________________
Glenn |
|
| Back to top |
|
|
| jhidalgo |
| Posted: Fri Feb 05, 2010 11:10 am Post subject: |
|
|
Disciple
Joined: 26 Mar 2008
Posts: 161
|
the MQ Cluster improved my quality of life !
|
|
| Back to top |
|
|
| mvic |
| Posted: Fri Feb 05, 2010 11:16 am Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| gbaddeley wrote: |
| mvic wrote: |
| If the SDR/RCVR pairing meets all your requirements, then look no further. |
You could look at MQ Clusters |
| jhidalgo wrote: |
the MQ Cluster improved my quality of life !
|
If all you need is a SDR/RCVR, then avoid clusters.
If, on the other hand, you need clusters, then use clusters.
Simple!  |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Fri Feb 12, 2010 9:44 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| mvic wrote: |
| gbaddeley wrote: |
| mvic wrote: |
| If the SDR/RCVR pairing meets all your requirements, then look no further. |
You could look at MQ Clusters |
| jhidalgo wrote: |
the MQ Cluster improved my quality of life !
|
If all you need is a SDR/RCVR, then avoid clusters.
If, on the other hand, you need clusters, then use clusters.
Simple! |
You can merge the both in a project/architecture by using sdr/rcvr and cluster sender/cluster receiver channels. you can check the functionality of queue manager alias by the way.
I agree, all depends on the kind of requirement. 
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
|
|
