| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries for Windows Workstation NT and AS/400 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Yuri |
 Posted: Mon Apr 29, 2002 3:12 pm Post subject: |
 |
|
Newbie
Joined: 10 Apr 2002
Posts: 5
Location: U.S.A.
|
Hi,
I will work with MQSeries for Windows Workstation NT and AS/400, my client give me the next information:
Queue Manager: I400MIAMI.RIBS
Request Queue: MI.RIBS.REQUEST ( This is for OSystem to send their request to )
Reply Queue : MI.RIBS.REPLY ( This is for OSystem to receive reply from )
Please tell me, for this squeme a need define a Receiver Channel and Sender Channel for each queue for the AS/400 side and Workstation NT?
Please give yours suggest or How a need to work, my client never work with MQseries As400 and I only read about MqSeries Windows NT.
With Regards.
Yuri |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Apr 29, 2002 6:36 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Where is this I400MIAMI.RIBS Queue Manager located? Is it on the AS400 or on the NT Workstation? Where does the app that puts the requests exist, on the NT workstation? Is there going to be a queue manager on both the AS400 and the NT box? Or can you use the MQClient for one of them?
That aside, when dealing with a queue manager on each box, Sender/Reciever channel pairs only need to be defined between queue managers, not between queues. So 1 pair handles messages going from Queue Manager#1 (QM1) to Queue Manager#2 (QM2), and another pair handles messages going from QM2 to QM1.
On QM1, define a sender channel to QM2, and a reciever channel from QM2. On QM2, define a sender channel to QM1, and a reciever channel from QM1. Usually you name these channels after the QMs they go between, so a sender from QM1 to QM2 would be called QM1.QM2. (Unfortunatly, channel names can only be 20 bytes long, and your client picked a QM name longer than 9 bytes, so if we consider I400MIAMI.RIBS to be QM1, then you only have 4 bytes for whatever QM2 is going to be, or you break the convention and call the channel whatever.)
On QM1, define an XMIT queue called QM2 (in other words name it after the queue manager it is going to) and associate it with a sender channel going to QM2.
On QM2, define an XMIT queue called QM1 and associate it with a sender channel going to QM1.
Now if you only have the queue manager on one box, you can get away with using the client on the other. In this case, you can skip all of the above. Just create a SVRCONN channel on the QM (or use the default) to accept the client connection request. Be aware that using Clients has its own set of pluses and minuses. Read the Client manual or search this site for discussions on Clients to determine if this will work for you.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| 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
|
|
|
|
