There shouldn't be any extra steps required to work remotely. You can pull up the wsdl in a browser on the same computer where the java example fails?
At this point, I'd probably use Wireshark or Fiddler to see what's actually happening when the java example is failing.
The issue was with the SolarWinds.InformationService.exe.config file (and all the references to localhost). WE replaced all the localhost references with the hostname of the box, and those changes showed up in the WSDL location attributes. Those attributes on the client side need to point to the server (not the local client).
Unless there is a SSL feature in wireshark, I can only see where the packets are going, and not what's in them... adn packets destined to localhost were certainly unexpected.
Things are looking good so far. Tomorrows tests are to use the web cluster certificate (in place of the self signed cert documented in the Orion SDK.pdf), and apply the necessary config changes to have all WSDL location attributes point to the cluster (not an individual server). Then we'll see if we can remove the disableCertificateValidation().