[EMAIL PROTECTED] wrote:
Hello Axis users/developers!
First, I would like to apologize for cross-posting (to both user and dev mailing
list), but i couldn't decide which of the lists would be more suitable
for my problem.
Neither, this is a generic web server issue.
I need to implement a mechanism that would allow clients from the
internet to access web services on nodes on a private, internal LAN with
no public IP addresses.
Our system, remarkably similar to the one you describe, works as follows :
Blade farms run the web service hosts along with various other web
resources (CGI, compute farm etc). These are on a distinct subnet with
private addresses and no access to the outside world of any form.
Web nodes (blades + alphaservers, I think) run Apache webserver.
ProxyPass directives in the Apache configuration are used to map URL
patterns through to internal addresses on the blade farms. For example,
there is a proxy pass that maps all of
http://www.ebi.ac.uk/collab/mygrid/services/service1 to
web4-node1.ebi.ac.uk:8080/axis/services (or similar, I can't recall
exactly but you get the idea).
Hardware IP redirector exposes an external address and routes requests
to the web nodes. Obviously this is optional, you could just have the
web node or nodes exposed on the internet but this allows scalability of
the web layer as well as the service layer.
The potential catch with this is that you have to be careful when
setting the endpoints in the WSDL bindings section - we generally
disable automatic WSDL generation having taken a copy of the
autogenerated document, rewrite the endpoint and deploy it as static
content on our primary web servers.
Tom
