| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Port Range used by MQ and Integration Nodes |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bichu |
 Posted: Thu Jul 14, 2016 3:11 am Post subject: Port Range used by MQ and Integration Nodes |
 |
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
Hi Guys,
I would like to know the range of ports used by a QM and a Broker.
I know 1414 is the default listener TCP/IP port of a QM. But I have changed that in my previous projects to 1415 also. I would like to know is there any defined range of ports as we have for Integration Server HTTP/HTTP(S) ports spanning from 7800-7842 and 7843-7884.
Also, apart from the ports mentioned above used by Integration Server, I used to see the ports 7800 and 7843 that a Broker HTTP/S listens to.
Why I have this requirement is I need to have access to IIB Pre-prod and Prod environments. Hence I need to raise a request for opening the ports. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Jul 14, 2016 3:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Each MQ listener uses a fixed port.
There's only one well known port for MQ and that's 1414. I think 1415 is actually a well known port for something else.
But there's no reason to use any specific port # for MQ at all. You don't even need to use a single listener.
There are pros and cons to using more than one listener. It's very situation-ally dependant.
You can't just randomly raise a request to open port XYZ and expect it to point to a queue manager or an HTTP port on IIB. Or etc. etc. etc.
You have to know the configuration of the queue manager and of the HTTP endpoints for IIB.
I'd be surprised if you were given access to the production environment.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jul 14, 2016 4:38 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
The range is defined by whomever installs the QM and broker - assuming that they always customise it.
It's best to choose non-default ports to avoid conflicts if running more than one QM or broker on the same host.
In broker, one can also assign a port range for auto allocation by EGs, but I prefer to fix ports per execution group so that their value is predictable.
The broker listener and EG listeners will have different ports, you can display those in use with various report commands, although you would have to list every EG to be sure of capturing any EG level listener.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jul 14, 2016 4:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| zpat wrote: |
| In broker, one can also assign a port range for auto allocation by EGs, but I prefer to fix ports per execution group so that their value is predictable. |
Especially when you have to open a firewall. Better to open a specific port than open a range, and leave unused ports for an intruder to use.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Bichu |
| Posted: Thu Jul 14, 2016 5:02 am Post subject: |
|
|
Centurion
Joined: 16 Oct 2011
Posts: 124
Location: London
|
|
| 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
|
|
|
|
