| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Connecting to remote queue mgr |
« View previous topic :: View next topic » |
| Author |
Message
|
| kprime |
 Posted: Tue Jul 24, 2001 5:49 am Post subject: |
 |
|
Newbie
Joined: 23 Jul 2001
Posts: 3
|
*ahem* I tried to send messages from a queue manager on a box to another one on another box unsuccessfully (both running v5.2 on NT)
I followed the instructions given in the intercomm manual (creating remote queue definition, sender channel, local queue, receiver channel etc...), but it didn't work. Actually, they never say where to specify the IP of the remote box to be accessed !
And there is no such field either in the remote queue definition nor in the sender channel one 
May someone help me ?
dash (the main question is: where to specify the remote IP where the remote qmgr sits) |
|
| Back to top |
|
 |
| ChrisW |
| Posted: Tue Jul 24, 2001 6:17 am Post subject: |
|
|
Voyager
Joined: 20 May 2001
Posts: 78
Location: UK
|
| The IP Address is specified on the sender channel in the CONNAME parameter. Remember to add the port number as well. |
|
| Back to top |
|
|
| bduncan |
| Posted: Tue Jul 24, 2001 7:58 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
Yes, if you simply provide an ip address or hostname, MQSeries assumes port 1414. For example:
CONNAME('ns1.yahoo.com')
CONNAME(192.168.1.10)
To provide a different port number:
CONNAME('ns1.yahoo.com(5555)')
CONNAME('192.168.1.10(5555)')
Notice that on the last example, where I used an IP address and non-standard port I had to put ' ' around it, whereas using an ip address on a standard port didn't require it. This is because when you wrap the port number in parantheses, MQSeries will interpret it incorrectly - you must wrap it all in apostrophes...
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator
[ This Message was edited by: bduncan on 2001-07-24 09:01 ]
[ This Message was edited by: bduncan on 2001-07-24 09:02 ] |
|
| Back to top |
|
|
| kprime |
| Posted: Wed Jul 25, 2001 12:44 am Post subject: |
|
|
Newbie
Joined: 23 Jul 2001
Posts: 3
|
Ok, I entered the ip address of the peer on which resides the remote queue in the Connection name field of the Sender channel.
But when I attempt start this channel, it still fails
I have a receiver channel attached to the target queue manager on the peer, with a listener running on port 1414...
As advised in the MQ doc (intercommunication), I specified the name of the remote queue manager in the Transmission queue field when defining the Sender channel. Could it be the problem ?
Thx a lot !
dash |
|
| Back to top |
|
|
| kprime |
| Posted: Wed Jul 25, 2001 1:12 am Post subject: |
|
|
Newbie
Joined: 23 Jul 2001
Posts: 3
|
Yeap that was the problem seemingly...I created a local transmission queue and specified it in the channel properties and it just worked fine, both channels started.
Thx for your help !
dash |
|
| Back to top |
|
|
| pazhanikumart |
| Posted: Mon Aug 13, 2001 1:10 am Post subject: |
|
|
Apprentice
Joined: 12 Aug 2001
Posts: 32
Location: Chennai,India
|
we created all the Channels and Transmission queues.When we try to start the Sender Channel it is showing BINDING state and then retries .
Details of Queue
for Queue_Manager_1
Sender_channel,Receiver Channel,Remote Queue definition ,Transmission Queue
for Queue_Manager_2
Receiver Channel,Queue
Should we start the runmqlsr for every queue Manager?
Is it enough if we post the message in the transmission queue?
Please help me in this issue
|
|
| Back to top |
|
|
| kolban |
| Posted: Mon Aug 13, 2001 3:58 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
For each queue manager that is going to receive queues, a distinct MQSeries listener must be associated with that queue manager. Even if two queue managers are coresident on the same machine, you will still need to listeners. Each listener needs exclusive access to a TCP/IP port. This means that if you run two listeners on the same machine, each will have to be configured with a different port (default 1414).
Make sure that on the connection name on the sender, if a port other than 1414 is in use on the target queue manager that the connection name also includes the target port. As a matter of convention, I always code the port number, even if default of 1414 is being used.
(*** Posting moved to separate thread on this topic ***)
[ This Message was edited by: kolban on 2001-08-13 05:01 ] |
|
| 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
|
|
|
|
