WSDL hostname is localhost

I've downloaded the Orion SDK and it works fine, except that it only connects to the web service if it is installed on the same machine as the Orion server.

localhost:17778/.../InformationService

The reason is the WSDL binds the service to localhost rather than the actual hostname or IP address of the server:

<wsdl:port name="BasicHttpBinding_InformationService" binding="tns:BasicHttpBinding_InformationService">
<soap:address location="">localhost:17778/.../>
</wsdl:port>

Can this hostname be configured somewhere in Orion?

Thanks in advance!

Find more posts tagged with

sdk

wsdl

Accepted answers

graham_fitter

I can confirm that it works fine through the firewall if the external port is the same number as the local port and the baseAddress has the IP address of the firewall.

Obviously as noted I now can't make a connection from inside the firewall but it will work like this for now.

Thanks very much for your help!

All comments

tdanner

Yes. In C:\Program Files\SolarWinds\Orion\Information Service\2.0 (default location - will be different if you installed Orion somewhere else), edit SolarWinds.InformationService.exe.config. There should be a section that looks like this:

   <host>
   <baseAddresses>
   <add baseAddress="">localhost:17778/.../InformationService" />
   </baseAddresses>
   </host>

Change localhost to the name of the machine (hostname, IP address, FQDN - any of these should work) and restart "SolarWinds Information Service". Now the generated WSDL should use the name you specified.

[This issue is resolved in Orion NPM 10.1, which is currently in the Release Candidate stage. In that version, SWIS will use the server's FQDN instead of localhost in the WSDL without you having to edit any config files.]

graham_fitter

That worked great, thanks for your prompt response!

graham_fitter

Some more information for posterity which may be of use to Java web service novices such as myself...

The default constructor to InformationService assumes localhost so you need to create an InformationService using a URL and a QName. You need to be really careful about the URL! The example code you need to do this is in the static block in InformationService where it creates the URL for the localhost connection. You end up with something like this:

URL baseUrl = org.tempuri.InformationService_Service.class.getResource(".");
URL url = new URL(baseUrl,    "">localhost:17778/.../InformationService
InformationService svc = new InformationService_Service(url,
    new QName("">http://tempuri.org/", "InformationService"));

Obviously replace localhost with the host/ip address of the Orion server.

graham_fitter

This solution works fine if the computer accessing the InformationService is on the same network as the Orion server. Now I need to access the web service from a computer on a different network, through a port mapped in the firewall and I need help making that work.

Thanks in advance!

tdanner

Edit, later: this only applies to Orion NPM 10.1.

Try this:

Edit C:\Program Files\SolarWinds\Orion\Information Service\2.0\SolarWinds.InformationService.Service.exe.config.

Find the line near the top that looks like this:

<add key="InformationServiceBaseAddressHttps" value="">localhost:17778/.../InformationService" />

Change "localhost" to some DNS name or IP address that will work. Restart "SolarWinds Information Service".

Background: the address used in the WSDL is created by taking the value of "InformationServiceBaseAddressHttps" and replacing "localhost" with whatever the server thinks is its own FQDN. If you replace "localhost" yourself by editing this file, that replacement won't happen - it will use what you specify.

tdanner

I reread your question and realized this might be trickier than I thought. You can set the https address for the Information Service to anything you want, even something that won't resolve locally. But you can only set it to one thing - there isn't a way to use different hostnames in the WSDL for different clients depending on what network they are on or how they connect.

Unfortunately, the best suggestion I can come up with right now is to find a way to get the client library to not fetch the WSDL every time. Some client libraries like to do this, others don't.