| Author |
Message
|
| mquickenton |
 Posted: Tue Jul 16, 2013 10:57 am Post subject: MQIPT across a firewall on port 80 |
 |
|
Newbie
Joined: 16 Jul 2013
Posts: 4
|
Good afternoon.
I have been working on getting MQIPT(2.0) set up to pass messages across a firewall on port 80 via HTTP. I have read the manual but I am getting a bit confused. I can't seem to get it to work.
Layout - MQ .NET Client -> MQIPT >firewall> MQIPT -> Queue Manager
My security requirement is HTTP through the firewall. Security will not open any other port for me.
MQ.NET Client box CONF
[route]
Name=Net1.TO.Net2
ListenerPort=1400
Destination=10.16.30.177
DestinationPort=80
OutgoingPort=0
RouteRestart=false
IdleTimeout=60
Trace=1
HTTP=true
HTTPServer=10.16.30.177
HTTPServerPort=80
Net2 MQIPT
Name=Net2.TO.QueueManager
ListenerPort=80
Destination=MyQueueServerName
DestinationPort=5010
OutgoingPort=0
Trace=1
I have looked at the traces and log files. It looks like the final hop to the MQServer is failing. "MQCPI130 Connection to caller closed due to connection failure to destination" This is on the MQIPT instance in Net2.
Just wondering if anyone sees anything glaring with my configuration. I don't want anyone to do my homework for me but I am a developer that is stumped.
Last edited by mquickenton on Wed Jul 17, 2013 5:55 am; edited 1 time in total |
|
| Back to top |
|
 |
| exerk |
| Posted: Wed Jul 17, 2013 2:02 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
So, if I understand this correctly:
.NET Client -> MQIPT -> FIREWALL -> MQIPT -> |
Where | represents the terminated connection? Have you checked that there is a valid network path from the machine within the firewall to the machine hosting the queue manager?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| mquickenton |
| Posted: Wed Jul 17, 2013 5:53 am Post subject: |
|
|
Newbie
Joined: 16 Jul 2013
Posts: 4
|
You understand correctly.
I have my sys admins confirming the route through the firewall.
I was just wondering if my conf entries looked correct. I think I have my head wrapped around the routes. Just need some validation.
I am a developer doing sysadmin work. Please be gentle.  |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Jul 17, 2013 6:01 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mquickenton wrote: |
| I am a developer doing sysadmin work. Please be gentle. |
No worries. Welcome to the world of "...what do you mean you've never heard of it? You have now because you're the one who's going to be administering it!..." 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jul 17, 2013 7:02 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
| A recent and seemingly significant update of MQIPT has taken place and I would imagine it would be better to use the current version (2.1). |
|
| Back to top |
|
|
| mquickenton |
| Posted: Thu Jul 18, 2013 9:16 am Post subject: |
|
|
Newbie
Joined: 16 Jul 2013
Posts: 4
|
Ok, I think we got this up and running.
One more question.
My SysAdmins would like to put MQIPT on a box running IIS. We have bound all sites on the IIS box to port 80 on a specific IP, and I have set MQIPT to bind to port 80 on an alternate address we configured on that box.
MQIPT refuses to bind to port 80 on either address we set LocalAddress to.
Am I missing something? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jul 18, 2013 9:21 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Refused why? Some kind of error msg?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| mquickenton |
| Posted: Thu Jul 18, 2013 9:22 am Post subject: |
|
|
Newbie
Joined: 16 Jul 2013
Posts: 4
|
| Route startup failed on port 80 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 18, 2013 7:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mquickenton wrote: |
| Route startup failed on port 80 |
Most probably because you need system superuser permission to open any port below 1024.
Have it open port 8080 (or any port over 1024) under the same user and see if that works.
What you should really do in this case is set up an http proxy at both ends in front of the MQIPT and reference the local http proxy in your conf. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
