| Author |
Message
|
| ivanachukapawn |
 Posted: Tue Dec 01, 2009 12:13 pm Post subject: sender vs server channel |
 |
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
| The info center on 2 types (sender and server) channels says both are used to send messages to another queue manager and both need to be paired with a receiver channel with the same name. (and both can be used with a requester channel). What are the principle differences between sender and server channels? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Tue Dec 01, 2009 12:46 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
The Intercommunication Manual has a good discussion on this topic. Take a look and quote any passages that you have follow up questions on.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| ivanachukapawn |
| Posted: Tue Dec 01, 2009 1:11 pm Post subject: |
|
|
Knight
Joined: 27 Oct 2003
Posts: 561
|
in the intercommunication manual I found
| Quote: |
A server channel can also initiate the communication and send messages to a
requester, but this applies only to fully qualified servers, that is server channels that
have the connection name of the partner specified in the channel definition |
However, this explanation is puzzling to me for several reasons, one being that I have always specified connection name including port in sender channel definitions anyway and another being the unknown rationale for having server channels. Is it the case that in all the configurations that I've used SDR/RCVR channels I could just as well have used SVR/RCVR channels and obtained the same functionality? |
|
| Back to top |
|
|
| mvic |
| Posted: Tue Dec 01, 2009 2:03 pm Post subject: |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
With a SVR you would pair it with a RQSTR and allow the RQSTR to start the channel. Or the SVR can start the channel to the RQSTR if needed. In that case you need to define a CONNAME in the SVR channel def.
With a SDR/RCVR pairing the SDR must start the channel. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Dec 01, 2009 8:10 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
|
| Back to top |
|
|
| friedl.otto |
| Posted: Sun Apr 04, 2010 4:14 pm Post subject: |
|
|
Centurion
Joined: 06 Jul 2007
Posts: 116
|
I have a feeling the question is still unresolved:
http://www.mqseries.net/manuals/intercommunication/csqzae060f.htm
Yields:
| Quote: |
Sender-receiver channels
A sender in one system starts the channel so that it can send messages to the other system. The sender requests the receiver at the other end of the channel to start. The sender sends messages from its transmission queue to the receiver. The receiver puts the messages on the destination queue. Figure 5 illustrates this. |
Almost verbatim from here
And:
| Quote: |
Server-receiver channel
This is similar to sender-receiver but applies only to fully qualified servers, that is server channels that have the connection name of the partner specified in the channel definition. Channel startup must be initiated at the server end of the link. The illustration of this is similar to the illustration in Figure 5. |
Almost verbatim from here
The question did not involve RQSTR channels at all. Since they obviously
allow the 'receiving end' to initiate connections, and where the differences
between a SDR and SVR channels are more apparent (SVR does
callbacks, SDR doesn't).
The question was: what (if any), is the difference between a simple SDR
and a SVR channel (if in both cases the CONNAME is set) when the
opposite end is a simple RCVR?
So the following holds for both SDR-RCVR and SVR-RCVR channels:
1. Connections can only be initiated from the non-RCVR end
2. Messages flow from SDR/SVR to RCVR.
3. CONNAME must be populated with the details of the RCVR host.
From what I can see, the SVR channel makes little sense when the
opposite end is a simple RCVR. Only if the opposite end is a RQSTR does
it enable the receiving host to dynamically change hostname (or port),
since the CONNAME on the SVR is optional, and the RQSTR will be
initiating the connection.
_________________
Here's an idea - don't destroy semaphores unless you're certain of what you're doing!  -- Vitor |
|
| Back to top |
|
|
| dauckKaw |
| Posted: Tue Apr 06, 2010 2:22 am Post subject: sender vs server channel |
|
|
Newbie
Joined: 05 Apr 2010
Posts: 2
|
| It means you are running sender callout. Try to remove it in WHM / EXIM configuration. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Apr 06, 2010 2:45 am Post subject: Re: sender vs server channel |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| dauckKaw wrote: |
| It means you are running sender callout. Try to remove it in WHM / EXIM configuration. |
Can you please elaborate on what you mean by WHM/EXIM ?
_________________
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: Tue Apr 06, 2010 10:58 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The primary difference between a SERVER and SENDER channel: SERVER is unattended, and therefore nobody there to issue START CHL.
_________________
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 |
|
|
| cgache |
| Posted: Thu May 04, 2017 7:08 pm Post subject: |
|
|
Apprentice
Joined: 27 May 2013
Posts: 28
Location: Sydney, AUS
|
Not sure if its the correct post but it's somewhat related and hoping someone can help me out.
I have a server-requester pair, both have con name fields populated. When the server channel is initiated by application it goes into retrying state saying remote host not available but the remote host server is fine and running. The requester channel on the remote host is inactive, when i manually start the requester channel on the remote host it starts the server channel, any pointers on what is happening to make the server think the remote host is unavailable?
TIA |
|
| Back to top |
|
|
| exerk |
| Posted: Fri May 05, 2017 1:25 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| cgache wrote: |
I have a server-requester pair, both have con name fields populated. When the server channel is initiated by application it goes into retrying state saying remote host not available but the remote host server is fine and running. The requester channel on the remote host is inactive, when i manually start the requester channel on the remote host it starts the server channel, any pointers on what is happening to make the server think the remote host is unavailable?
TIA |
Only that you should think of it as REQUESTER/SERVER, not the other way around 
_________________
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: Fri May 05, 2017 3:43 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
A REQUESTER-SERVER channel type implies that the SERVER end will be STARTed by an inbound request from the REQUESTER end of the channel.
Think of a large batch of messages that accumulate at the REQUESTER qmgr, that need to flow to a consuming app at the SERVER, but the SERVER app wants the messages in bulk, at midnight, not dribbling in throughout the day.
This channel-pair type presumes that the decision to start the message flow from R->S will made at the REQUESTER end - through a timer or job-scheduler or some other process.
_________________
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 |
|
|
| cgache |
| Posted: Sun May 07, 2017 3:27 pm Post subject: |
|
|
Apprentice
Joined: 27 May 2013
Posts: 28
Location: Sydney, AUS
|
| exerk wrote: |
| cgache wrote: |
I have a server-requester pair, both have con name fields populated. When the server channel is initiated by application it goes into retrying state saying remote host not available but the remote host server is fine and running. The requester channel on the remote host is inactive, when i manually start the requester channel on the remote host it starts the server channel, any pointers on what is happening to make the server think the remote host is unavailable?
TIA |
Only that you should think of it as REQUESTER/SERVER, not the other way around |
Noted, but my REQUESTER/SERVER still needs manual intervention to resolve the retrying state of the server  |
|
| Back to top |
|
|
| cgache |
| Posted: Sun May 07, 2017 3:35 pm Post subject: |
|
|
Apprentice
Joined: 27 May 2013
Posts: 28
Location: Sydney, AUS
|
| bruce2359 wrote: |
A REQUESTER-SERVER channel type implies that the SERVER end will be STARTed by an inbound request from the REQUESTER end of the channel.
Think of a large batch of messages that accumulate at the REQUESTER qmgr, that need to flow to a consuming app at the SERVER, but the SERVER app wants the messages in bulk, at midnight, not dribbling in throughout the day.
This channel-pair type presumes that the decision to start the message flow from R->S will made at the REQUESTER end - through a timer or job-scheduler or some other process. |
Hi Bruce,
Thanks for your reply. So I guess the only way around this is to put in some process to start the Requester at a certain point during the day? Was hoping there would be a different way around it  |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sun May 07, 2017 4:33 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
|
|
