| Author |
Message
|
| new_321 |
 Posted: Sat Sep 23, 2006 12:57 am Post subject: Is second listener necessary for remote administration? |
 |
|
Novice
Joined: 18 Jul 2006
Posts: 10
|
We already have default listeners "LISTENER.TCP" on
both of source and target of queue managers, <<MQSystem Administration Guide>> mentioned defining
listeners on both of them respectively, such as LISTENER('source.queue.manager') and LISTENER('target.queue.manager'),
are they the same as default ones or not?
Thanks |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Sep 23, 2006 6:23 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
We seldom use the default listeners -- leeds to too much confusion.
Make your listeners explicit even if they use default settings:
| Code: |
| def listener(qmgr_port) trptype(tcp) port(myport#) control(qmgr) |
Remember each qmgr on the same machine needs a listener on a different port. You can use one or multiple listeners per qmgr. The reason for multiple listeners on a qmgr can be for traffic separation. So if you kill all outside connections (in a denial of service attack) your inside network using the other listener is not affected...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat Sep 23, 2006 7:23 am Post subject: |
|
|
Guest
|
| A second listener is not needed for remote admin. |
|
| Back to top |
|
|
| new_321 |
| Posted: Sun Sep 24, 2006 4:31 am Post subject: Re: |
|
|
Novice
Joined: 18 Jul 2006
Posts: 10
|
Thank all of you.
I set up channels and transmission queues on local and remote QMs respectively, local QM is on MQ windows 6.0, remote is on MQ 5.3, solaris 5.8. but administering remote queue manager failed.
Following actions were done on remote qm:
ping CHANNEL(target.to.source)
6 : ping CHANNEL(target.to.source)
AMQ8020: Ping WebSphere MQ channel complete.
start listener
8 : start listener
AMQ8021: WebSphere MQ Listener program started.
start channel(target.to.source)
9 : start channel(target.to.source)
AMQ8018: Start WebSphere MQ channel accepted.
$ strmqcsv REMOTE.queue.manager
WebSphere MQ command server started.
Following actions were done on local qm:
ping channel source.to.target successful.
C:\WINDOWS\system32>runmqsc -w 300 REMOTE.QUEUE.ANAGER
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager REMOTE.QUEUE.MANAGER.
dis qmgr
1 : dis qmgr
AMQ8416: MQSC timed out waiting for a response from the command server.
Local status of QM ,command server and listener are all running.
How to fix it?
Thanks again. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Sep 24, 2006 5:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
check out the messages on the dead letter queues.
make sure your windows qmgr is the default qmgr
make sure there is a default path to each of the qmgrs (from win to solaris and from solaris to win) see intercommunications manual and qmgr alias info...
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Mon Sep 25, 2006 4:39 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
Make sure your xmitqs are named the same as the destination qmgrs, or look into qmgr aliases as fjb_saper mentioned.
Cheers
Steve |
|
| Back to top |
|
|
|
|
