Web services on a clustered server

Question

Hi,
          I'm newbie on web services and I made a simple web service with bea workshop. when I try to deploy it on a bea WLS that has a unique server all works fine, also when I try to test the WS through http://myserver:7001/myapplication/mywebservice.jws or when I try to visualize the WSDL file through http://myserver:7001/myapplication/mywebservice.jws?WSDL.
          But when I try to deploy the same WS on a clustered server (with 1 admin server and 2 clustered server) I don't find the WS and if I try to visualize the WSDL file I get a WEBSERVICE ERROR on the browser :O
          can anyone help me
          thanks in advice
          Daniele

Answer 1

External domains are a prerequisite here, and a minimum of one public static IP address.
You can set that up with a reverse proxy (Apache reverse proxy) through the Xserve box, allowing connections from outside to reach the Xserve and the Xserve communicating with the Mac Mini box. This is basically a web pass-through, were Apache running on your Xserve can hand off to your Mac Mini. This involves reading the [web manual|http://www.apple.com/server/macosx/resources/documentation.html] and using Server Admin to establish the reverse proxy.
You can also set up a mid-level server-grade external firewall (using an external firewall and not a Mac is locally preferred for various reasons) to have it port-forward connections based on IP address, for instance. This is a more traditional set-up for a web server, and is covered in various IP network configuration discussions around the Internet. This involves setting up your network with a reasonable mid-range commercial or open-source firewall, and establishing port-forwarding on the firewall.
You must expect your servers to be attacked, and you will be attacked. The servers I administer are attacked many times a day, with XSS and SQL injection attempts and probes for various other known vulnerabilities, dictionary attacks against passwords, and attempts to post spam on the web sites are also very common. This involves monitoring your logs, watching for attacks, and staying current on all your software and keeping your archives current; your (trusted) backups are the path back from a server breach.
You may want to consider a DMZ for your public-facing services, which is another feature of a typical server-grade firewall, as a web breach can get hairy for the rest of your LAN. Using a properly-configured DMZ usually isolates a breach.
Here's an old [write-up on the various network pieces|http://labs.hoffmanlabs.com/node/275] that can be involved in a small server-oriented network configuration.