Re: Reverse Proxy Servers and Web Services

Great suggestions Alan!



I see no errors in the iSeries Apache log and none in the iSeres Web
Services Server logs either.



I am unable to get onto the Reverse Proxy PC as another IT guy handles
access to that and he is not available so late at night.



I'm hoping he'll contact me tomorrow (I've sent him enough emails to get his
attention today!) so that he can look at that for me.



When testing the call to the Web Service through the public entry point
(Reverse Proxy Server PC) using SoapUI the error message I see is:
"Connection Refused".



To me that sounds like the two Apache servers cannot talk to each other over
under these conditions.



What is odd though is that I am able to retrieve the WSDL from the iSeries,
while NOT! On the VPN, and going THROUGH the Reverse Proxy Server. So I
can get the definition file, I just cannot get data requests through.



Earlier today I was looking at the generated WSDL files that the IIS server
created and I saw one thing I was not expecting.



Our Web Services Server listens on Port 10043. But within the WSDL file
itself, it points to port 10033.



So I'm wondering now if the Reverse Proxy Server needs to also map to port
10033 in addition to 10043 that it already maps to.



This stuff makes my head hurt trying to unravel it all.







From: Alan Seiden [mailto:alan@xxxxxxxxxxxxxx]
Sent: Saturday, March 03, 2012 11:29 PM
To: Web Enabling the AS400 / iSeries
Cc: Shannon ODonnell
Subject: Re: [WEB400] Reverse Proxy Servers and Web Services



Shannon,

Two questions to start, checking the Apache logs on both servers.

1. What is shown in the reverse proxy server's Apache access log? Can you
tell if proxy Apache is receiving and forwarding the request properly to the
IBM i?

2. Is the IBM i receiving the request correctly? The IBM i's Apache server
logs may contain useful information, too.

Alan