Web Service with IIS Web server feasible?

Question

Hi all,
we have come up with the following architecture and would like to
know whether we have mis-interpret anything. We would also like
to know whether this architecture is feasbile or not.
     java client web page browser requesting for the WSDL
     application / of our web service.
          |
          |
     (Internet)
          |
          |
     Firewall 1 (only allow port 80 traffic)
          |
          |
     Microsoft IIS Web Server with iisproxy.dll installed.          
     (hostname : d3dpc1 port number : 80)
          |
          |
     Firewall 2 (only allow port 8100 traffic)
          |
          |
     WebLogic 7.1 Server with a web service deployed.      
     (hostname : d3dpc2 port number : 8100)
Assumed that we have constructed a certain web service through
the weblogic workshop and the web service page can be reached behind
the Firewall 2 via the following URL:
http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws
Next, we'd like to access the same web service outside the Firewall 1.
On our IS web server, we make use of the IIS plugin and wrote an
iisproxy.ini as follows:
WebLogicHost=d3dpc2
WebLogicPort=8100
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WLForwardPath=/weblogic
PathTrim=/weblogic
we insalled the IIS plugin accoring to the document
"Using Web Server Plug-ins with WebLogic Server", starting
with page 3-3, running through steps 1-7, 9-10.
As a result, through the web page browser on the
client machine outside the Firewall 1, we can
obtain the WSDL through the following URL
http://d3dpc1:80/weblogic/treasuryWebService/FileOperation/FileUpload.jws?WSDL
At the bottom of the attached WSDL, we found that it appears as
<service name="FileUpload">
- <port name="FileUploadSoap" binding="s0:FileUploadSoap">
<soap:address location="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws"
/>
</port>
- <port name="FileUploadHttpGet" binding="s0:FileUploadHttpGet">
<http:address location="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws"
/>
</port>
- <port name="FileUploadHttpPost" binding="s0:FileUploadHttpPost">
<http:address location="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws"
/>
</port>
</service>
It presents to us the address is "http://d3dpc2:8100...."
which is behind two of our Firewalls, which is, in turn,
cannot be directly accessed by our client applications.
As a result, if we run a java client applications to our web service by
making use of
http://d3dpc1:80/weblogic/treasuryWebService/FileOperation/FileUpload.jws?WSDL,
we may obtain the WSDL but the subsequent method calls to our web service
may be blocked. Are we mis-interpreting anything? Is it feasible
for us to setup an IIS web service in between our client applications
to our web service like that?
We are pleased to provide further information, like our simple
web service code, if not sufficient. Please offer help!
Kenneth
[FileUpload.wsdl]

Answer 1

Hi Kenneth,
You need to modify the file weblogic-jws-config.xml in your workshop project
folder before you genereate the WSDL file.
The <hostname> and <http-port> entity below will point to your webserver
address, in this case it would be: <hostname>d3dpc1</hostname> and
<port>80</port>
Here is an example of the XML file:
<config>
<protocol>http</protocol>
<hostname>d3dpc1</hostname>
<http-port>80</http-port>
<https-port>443</https-port>
<jws>
</jws>
</config>
Thanks,
Ninou Sarwono
"Kenneth Yue" <[email protected]> wrote in message
news:[email protected]...
>
>
Hi all,
sorry for the messy format. I don't why the texts
are present like this. Please kindly press the reply
link and in the reply window, you will see a
better format of my text. Sorry for any inconvenience
caused.
thanks
cheers,
Kenneth
"Kenneth Yue" <[email protected]> wrote:
Hi all,
we have come up with the following architecture and would like to
know whether we have mis-interpret anything. We would also like
to know whether this architecture is feasbile or not.
java client web page browser requesting for the WSDL
application / of our web service.
|
|
(Internet)
|
|
Firewall 1 (only allow port 80 traffic)
|
|
Microsoft IIS Web Server with iisproxy.dll installed.
(hostname : d3dpc1 port number : 80)
|
|
Firewall 2 (only allow port 8100 traffic)
|
|
WebLogic 7.1 Server with a web service deployed.
(hostname : d3dpc2 port number : 8100)
Assumed that we have constructed a certain web service through
the weblogic workshop and the web service page can be reached behind
the Firewall 2 via the following URL:
http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws
Next, we'd like to access the same web service outside the Firewall 1.
On our IS web server, we make use of the IIS plugin and wrote an
iisproxy.ini as follows:
WebLogicHost=d3dpc2
WebLogicPort=8100
ConnectTimeoutSecs=20
ConnectRetrySecs=2
WLForwardPath=/weblogic
PathTrim=/weblogic
we insalled the IIS plugin accoring to the document
"Using Web Server Plug-ins with WebLogic Server", starting
with page 3-3, running through steps 1-7, 9-10.
As a result, through the web page browser on the
client machine outside the Firewall 1, we can
obtain the WSDL through the following URL
http://d3dpc1:80/weblogic/treasuryWebService/FileOperation/FileUpload.jws?W
SDL
>>
At the bottom of the attached WSDL, we found that it appears as
<service name="FileUpload">
- <port name="FileUploadSoap" binding="s0:FileUploadSoap">
<soap:addresslocation="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws
/>
</port>
- <port name="FileUploadHttpGet" binding="s0:FileUploadHttpGet">
<http:addresslocation="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws
/>
</port>
- <port name="FileUploadHttpPost" binding="s0:FileUploadHttpPost">
<http:addresslocation="http://d3dpc2:8100/treasuryWebService/FileOperation/FileUpload.jws
/>
</port>
</service>
It presents to us the address is "http://d3dpc2:8100...."
which is behind two of our Firewalls, which is, in turn,
cannot be directly accessed by our client applications.
As a result, if we run a java client applications to our web service
by
making use of
http://d3dpc1:80/weblogic/treasuryWebService/FileOperation/FileUpload.jws?W
SDL,
we may obtain the WSDL but the subsequent method calls to our web service
may be blocked. Are we mis-interpreting anything? Is it feasible
for us to setup an IIS web service in between our client applications
to our web service like that?
We are pleased to provide further information, like our simple
web service code, if not sufficient. Please offer help!
Kenneth