| Author |
Message
|
| RAS-NR |
 Posted: Wed Feb 26, 2003 7:44 am Post subject: Controlling outbound ports on Linux Client? |
 |
|
Newbie
Joined: 26 Feb 2003
Posts: 4
Location: London
|
Can anyone point me to documentation/information that indicates how one can control the outbound ports that a MQSeries 5.2. Linux client uses.
I have breifly looked over the MA86 and MS81 support PACs and breifly reviewed the Intercommunication and Systems documentation. I have also check IBM support information.
There are various suggestions for various platforms around configuring:
- qm.ini (TCP and TCPConfig)
- setting MQTCPSDRPORT to certain values
However, none of these seem to specifically state if they apply to a client installation even though there is a QM.INI file?
This is necessary as the channels response (from 1414) comes back on the outbound port that is used - which has unacceptable firewall implications.
MQSeries 5.2 Linux to MQSeries 5.2 on OS/390 and
MQSeries 5.2 Linux to MQSeries 5.2.1 on NT
Thanks in advance.
Richard |
|
| Back to top |
|
 |
| mrlinux |
| Posted: Thu Feb 27, 2003 7:19 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
Are you wanting to another port other than 1414 ????
If so you need to create a listener on the qmanger side for a different port. Also you need to specify the port on the client side, this is dependent
on how you setting up the Communication, are you using Java or JMS ??
If you are using JMS you can add the port attribute to the QCF definition.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| RAS-NR |
| Posted: Thu Feb 27, 2003 9:29 am Post subject: |
|
|
Newbie
Joined: 26 Feb 2003
Posts: 4
Location: London
|
Hi Jeff
The Q Mgr (Mainframe side) is configured to listen on 1414 and the C language program on the Linux MQ Client side knows to send to that IP/port - the problem is the port that the client itself uses.
The trace output below is taken on the Q Mgr (Mainframe side) - edited somewhat i.e. the left hand side (of the ->) is the Q MGR side (mainframe) and the right hand side (of the ->) is the Linux Client.
tcp 171.28.18.50(1414) -> 192.168.74.57(36744), 1 packet
tcp 171.28.18.50(1414) -> 192.168.74.57(36744), 49 packets
tcp 171.28.18.50(1414) -> 192.168.74.57(39771), 1 packet
tcp 171.28.18.50(1414) -> 192.168.74.57(39771), 1374 packets
tcp 171.28.18.50(1414) -> 192.168.74.57(39771), 273 packets
tcp 171.28.18.50(1414) -> 192.168.74.57(42660), 1 packet
tcp 171.28.18.50(1414) -> 192.168.74.57(42660), 29 packets
tcp 171.28.18.50(1414) -> 192.168.74.57(42666),
etc
Linux program is C language.
As you can see the ports used by the Linux MQ client vary and this is what we would like to control - but how?
Thanks |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Feb 27, 2003 11:47 am Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
This is the typical TCP application behavior the response port is always a hi port number. This is not an MQSeries thing this is a TCP thing.
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Feb 27, 2003 12:44 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I know that you can update the registry on a Windows box to make the client use a port in a specific range. I would guess that setting the environment variable (not sure about the ini file) would work on your Linux box. Have you tried it? |
|
| Back to top |
|
|
| mrlinux |
| Posted: Thu Feb 27, 2003 1:38 pm Post subject: |
|
|
Grand Master
Joined: 14 Feb 2002
Posts: 1261
Location: Detroit,MI USA
|
MQseries is not picking the port number. The hi port number is returned from the TCP Call. IF there are any settings it would be an OS Level or TCP Setting
_________________
Jeff
IBM Certified Developer MQSeries
IBM Certified Specialist MQSeries
IBM Certified Solutions Expert MQSeries
Last edited by mrlinux on Thu Feb 27, 2003 1:47 pm; edited 1 time in total |
|
| Back to top |
|
|
| RAS-NR |
| Posted: Thu Feb 27, 2003 1:42 pm Post subject: |
|
|
Newbie
Joined: 26 Feb 2003
Posts: 4
Location: London
|
| It looks like I'll have to do some further research on this on - thanks anyway. I'll post the soln once I get it. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Feb 27, 2003 2:07 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Some success! There is a localaddr parameter on the define channel. It is used to control what a channel uses for its outbound ip address and port. It is only on sender channels, so you can't set it on a svrconn channel (which is probably what you are using with java). Knowing that the java client performs its own tcp/ip calls (rather than going through the C client), I'm not sure that you can use the environment variables, ini file, etc. to tell it what port to use.
To be honest, I vaguely remember this coming up (somewhere) before, and I think the answer is that it works with C clients but not java. |
|
| Back to top |
|
|
|
|
