| Author |
Message
|
| mq4474 |
 Posted: Wed Oct 26, 2005 3:53 am Post subject: rumqlsr port number 443 |
 |
|
Newbie
Joined: 05 May 2005
Posts: 8
|
Can anyone help answer this question ?
Can I run a queue manager to listen on port 443 (which is normally used for https) ?
In other words, can I start the runmqlsr program and make it listen on port 443 ?
Are there any potential problems with this approach?
runmqlsr -t tcp -p 443 -m QM1 |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 26, 2005 3:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can run any service you want on any port number you want.
You can not accept HTTPS traffic with an MQ Listener.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mq4474 |
| Posted: Wed Oct 26, 2005 4:00 am Post subject: rumqlsr port number 443 |
|
|
Newbie
Joined: 05 May 2005
Posts: 8
|
Hi Jeff,
Thanks for your response.
My idea is to run a client which would connect to an MQ server using SSL encryption.
I am currently making the client software connect to the MQ server (a SVRCONN channel) using SSL - over port 1414.
Would this still work if I shifted the port to 443.
I do not intend to run any https traffic on this port on this server.
Thanks |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 26, 2005 4:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
SSL encryption in MQ is handled by changing the channel definitions, not by changing the port that the listener is running on.
In fact, SSL encryption in HTTP is handled by changing the server definition, not by changing what port the server uses.
443 is, however, the "well known port" for HTTPS traffic - the default port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| MQ_Dude |
| Posted: Wed Sep 12, 2007 7:06 am Post subject: |
|
|
Newbie
Joined: 31 Aug 2007
Posts: 1
|
Sorry to bring this back up but it's exactly what we're trying to do.
We'd like to use only port 443 for MQ traffic. Of course, we will be using SSL for MQ by doing what the previous poster said, change the server definitions, etc. We will not be conducting other HTTPS activities using 443 on the server, only MQ.
So is this scenario possible?
Thanks. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 12, 2007 7:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can use any port you want for an MQ Listener.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Sep 12, 2007 9:06 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| MQ_Dude wrote: |
Sorry to bring this back up but it's exactly what we're trying to do.
We'd like to use only port 443 for MQ traffic. Of course, we will be using SSL for MQ by doing what the previous poster said, change the server definitions, etc. We will not be conducting other HTTPS activities using 443 on the server, only MQ.
So is this scenario possible?
Thanks. |
I'd strongly suggest against using any port < 1024 for your MQ listener.
Typically processes opening ports < 1024 have to be started by the root user.
This poses a whole different set of problems especially if root is not member of the mqm group and by default and design it should not be....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
