| Author |
Message
|
| maxy_14in |
 Posted: Wed Apr 14, 2010 11:40 am Post subject: Recieving on TCP |
 |
|
Apprentice
Joined: 07 Nov 2008
Posts: 43
|
I need suggestions regarding my issue:
Working on SOLARIS environment a QMGR has to listen on either the TCP/IP listener (INETD) or the WebSphere MQ listener.
Presently the QMGR is listening on INETD
1.The etc/services file has => MQSeries 1414/tcp
2.The inetd.conf file has the added line required
MQSeries stream tcp nowait mqm /mqmtop/bin/amqcrsta amqcrsta [-m QM1]
where QM1 is the queue manager name.
Now, we want to use the WebSphere MQ Listener rather than TCP/IP Listener. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Apr 14, 2010 11:49 am Post subject: Re: Recieving on TCP |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| maxy_14in wrote: |
| I need suggestions regarding my issue: |
What issue? You want to use the supplied listener (a really, really good idea on any version past v53), you have the port number (which you could have inferred from other sources) so just set up the listener.
There's no issue I can see from what you've said.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| maxy_14in |
| Posted: Wed Apr 14, 2010 6:39 pm Post subject: |
|
|
Apprentice
Joined: 07 Nov 2008
Posts: 43
|
we are using MQ v 7.0.1.
i have referred the MQ intercommunication documents, it says we are supposed to use any 1 of the method for listening.
1.According to that are we supposed to edit the qm.ini, inetd.conf, etc/services ... i.e., remove the TCP/IP port info from the respected files
2.Create a Listener on the QMGR and give the control as QMGR START ?
3.Recycle the QMGR.
Please correct me if i'm wrong following the steps. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Apr 14, 2010 7:05 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| maxy_14in wrote: |
| Please correct me if i'm wrong following the steps. |
Have faith in the documentation and yourself. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 15, 2010 6:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
I would leave the MQ entries in /etc/services just so that no other app thinks that these ports are up for grabs...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| maxy_14in |
| Posted: Thu Apr 15, 2010 7:54 am Post subject: |
|
|
Apprentice
Joined: 07 Nov 2008
Posts: 43
|
| oh ohk we have to reserve the ports so other apps dsn't use the ports ... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Apr 15, 2010 8:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| maxy_14in wrote: |
| oh ohk we have to reserve the ports so other apps dsn't use the ports ... |
This is standard TCP/IP - only one application can use the port at a given time. Leaving the entry (even though WMQ doesn't use it) reminds other apps not to use it. It doesn't stop another piece of software that uses ports but like WMQ doesn't use that method establishing a connection.
So you could "reserve" the port and still set 2 queue managers to use the port, discovering later that one of them won't work.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
