Author |
Message
|
rajasudan |
Posted: Fri May 06, 2011 5:44 am Post subject: Channel establishing diffrences? |
|
|
 Newbie
Joined: 04 May 2011 Posts: 8
|
Hi
I need to knw the uses of
why we user SERVER - REQUESTER
and SENDER - REQUESTER ?
I knw about Sender - Receiver uses in mq..
Pls some 1 tell its uses in mqseries...  |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 06, 2011 5:49 am Post subject: Re: Channel establishing diffrences? |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
rajasudan wrote: |
I knw about Sender - Receiver uses in mq.. |
A sender / requester is exactly the same, except the transfer of messages is initiated from the receiving end not the sending end (the messages are "requested").
Conceptually it's a "pull" model where the sender / receiver is a "push" model. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
rajasudan |
Posted: Fri May 06, 2011 9:15 am Post subject: |
|
|
 Newbie
Joined: 04 May 2011 Posts: 8
|
Thanks vitor.
But still im little confused by the role of SERVER in channels..
• Server-receiver & • Requester-server - Can u explain with some example..
I cant clearly understand from books.. though im started studing mq by myself.. im geting confused.. pls.. |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 06, 2011 9:26 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
A server channel is a specialised form of sender channel. I can't give you an example because in over 14 years of working with WMQ I've never seen one used! Sitting here, I can't think of even a theoretical example where you'd use one.
(Someone more imaginative, or with wider experience than me, will be along in a minute)
I've actually only seen a requester channel used once in all that time & I was not convinced a sender / reciever pair couldn't have been used in it's place. As you can imagine, in the typical asyncronous message environment it's rare for a receiving system to know there's a message waiting & request it's delivery.
If you're starting out with WMQ I can offer you 2 pieces of advice:
- skate over server channels (and requester channels) for now. Get comfortable with the mainstream. You'll have enough trouble with channels when you get to clustering.
- set up a WMQ Sandbox, define a server / requestor pair & test it. See what happens.
("Set it up in a sandbox & test it" is quite good advice for learning any aspect of WMQ) _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 06, 2011 10:01 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
You might consider reading through the WMQ Intercommunications manual.
Briefly, channel types that start with the letter S can open transmission queues, extract messages, and send them along to channel types that start with the letter R.
A SERVER channel type implies that the qmgr is unattended (a server), and that the SERVER channel will (may, might) be started by a message arriving at a triggered transmission queue. This, however, is not always the case.
A REQUESTER type channel implies that the other end of the channel (SENDER or SERVER) will not start the channel. Rather, the REQUESTER will initiate the channel. Basically, it's a choice: which end will start the channel? _________________ 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 |
|
 |
PeterPotkay |
Posted: Fri May 06, 2011 10:37 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
bruce2359 wrote: |
Briefly, channel types that start with the letter S can open transmission queues, extract messages, and send them along to channel types that start with the letter R. |
SVRCONN? _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
PeterPotkay |
Posted: Fri May 06, 2011 11:06 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
Vitor wrote: |
A server channel is a specialised form of sender channel. I can't give you an example because in over 14 years of working with WMQ I've never seen one used! Sitting here, I can't think of even a theoretical example where you'd use one. |
A SERVER channel with a blank CONNAME will rely on the calling REQUESTER to tell it where it go. This offers some flexibility. Maybe too much.
A REQUESTER calling to a SENDER channel has the SENDER channel stop communications and start up again, using the (mandatory for SENDERs) CONNAME to tell it where to go to. This insures the attempt to send the messages only goes to where the CONNAME is coded for. The same thing can be insured if you fill in the CONNAME on a SERVER channel.
Vitor wrote: |
I've actually only seen a requester channel used once in all that time & I was not convinced a sender / reciever pair couldn't have been used in it's place. As you can imagine, in the typical asyncronous message environment it's rare for a receiving system to know there's a message waiting & request it's delivery. |
A SENDER / REQUESTER pair will operate normally like a SENDER / RECEIVER. But I have heard the SENDER(or SERVER) / REQUESTER pairing can be quite useful when dealing with B2B, where the MQ Admins on the receiving QM do not have control over the sending side. Imagine the receiving side is the company Vitor works for and the sending side is the company I work for. Vitor's QM is running on a small Windows server, with limited queuing ability, andhis app is currently down. I produce messages all day long to send to Vitor, but Vitor will only accept them once his app is up and his coffee is finished. I don't want to be bothered to trigger the channel manually, sitting and waiting for Vitor to finish his morning joe. But since he is using a REQUESTER channel, he can start up the channel pair anytime he is ready. Until then the channel stays inactive and the queuing occurs on my sending QM, where I may have much more space for queuing. _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 06, 2011 11:25 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
PeterPotkay wrote: |
Vitor's QM is running on a small Windows server, with limited queuing ability, andhis app is currently down. I produce messages all day long to send to Vitor, but Vitor will only accept them once his app is up and his coffee is finished. |
Where am I working, Hell?
If it's an Earthly site, that coffee will be fortified with some interesting substances.....  _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Fri May 06, 2011 11:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Vitor wrote: |
PeterPotkay wrote: |
Vitor's QM is running on a small Windows server, with limited queuing ability, andhis app is currently down. I produce messages all day long to send to Vitor, but Vitor will only accept them once his app is up and his coffee is finished. |
Where am I working, Hell?
If it's an Earthly site, that coffee will be fortified with some interesting substances.....  |
Is that what they told you in Iowa? |
|
Back to top |
|
 |
Vitor |
Posted: Fri May 06, 2011 11:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
mqjeff wrote: |
Vitor wrote: |
PeterPotkay wrote: |
Vitor's QM is running on a small Windows server, with limited queuing ability, andhis app is currently down. I produce messages all day long to send to Vitor, but Vitor will only accept them once his app is up and his coffee is finished. |
Where am I working, Hell?
If it's an Earthly site, that coffee will be fortified with some interesting substances.....  |
Is that what they told you in Iowa? |
Even Iowa wasn't small Windows machines. And I made it through with nothing but fully-loaded coffee, Red Bull and thermal underwear. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
bruce2359 |
Posted: Fri May 06, 2011 12:15 pm Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
PeterPotkay wrote: |
bruce2359 wrote: |
Briefly, channel types that start with the letter S can open transmission queues, extract messages, and send them along to channel types that start with the letter R. |
SVRCONN? |
Ah. I though I'd skipped one.
A SVRCONN is a channel type that is the destination for inbound client requests. It acts as a proxy for MQI (and equivalent) calls from client applications. _________________ 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 |
|
 |
rajasudan |
Posted: Fri May 06, 2011 10:55 pm Post subject: |
|
|
 Newbie
Joined: 04 May 2011 Posts: 8
|
Thanks to all.. Now i can figure it out some..
Also i want to know the Difference of Transmission protocols in MQ..
v TCP
v LU 6.2
v NetBIOS
v SPX |
|
Back to top |
|
 |
mqjeff |
Posted: Sat May 07, 2011 3:44 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
rajasudan wrote: |
Thanks to all.. Now i can figure it out some..
Also i want to know the Difference of Transmission protocols in MQ..
v TCP
v LU 6.2
v NetBIOS
v SPX |
The difference is that they use different network protocols to communicate.
If you don't know what anything other than TCP is, then you need never worry about these. If someone, some day, somewhere, comes to you and says "this channel needs to go over NetBIOS instead of TCP", you can say tell them to give you the fields that MQ needs and it will work.
This is a question that is fairly straight forward to answer by reading the documentation.
You will find that people get less cooperative the more you ask these kinds of questions. |
|
Back to top |
|
 |
bruce2359 |
Posted: Sat May 07, 2011 5:06 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
More specifically, please do some basic research on your own.
For example, go to Google, and type 'what is tcp', or 'what us lu62'. _________________ 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 |
|
 |
azmishz |
Posted: Fri Sep 16, 2011 10:26 pm Post subject: |
|
|
Newbie
Joined: 16 Sep 2011 Posts: 1
|
very usefull for us…thanks.
by exerk: spammer content removed and user reported to site admin |
|
Back to top |
|
 |
|