Web Services

[Jamc]

Hi,

I have tried the example on your webpage (http://zone.ni.com/devzone/conceptd.nsf/webmain/29543201344AA09F86256D740066839E) with the subject "Using Web Services in LabVIEW". When I try to import it I get the following error: Validation Failed. The URL does not exist or the WDSL is bad. Can you give me any solution to this problem cause the URL exist.

Regards

Robert

[Lycangeek]

Not sure where the problem is for you. I just tried the URL from xmethods that is mentioned in the KB...

http://ws.cdyne.com/NotifyWS/phonenotify.asmx?WSDL

and it worked fine for me. It is an external web service owned by another company, so it's hard for us to say when it might not be working...

Is this the URL you were trying?

[Jamc]

I have tried the one you did and many more from xmethods but I always get the same result: "Validation Failed. The URL does not exist or the WDSL is bad". This occur already when I try to import the web service. 

However, I got hold of a local web service on our intranet and then I was able to import it and use its methods.

I am not sure if this problem is due to our firewall or a configuration in LabVIEW or the weather outside.

/Robert

[Lycangeek]

Hmmm, sounds like a proxy issue more likely. Do you know if you must go through a proxy to get out to the internet? You can always check your IE Tools->Options->Connections to see if your IT group set one up.

[Jamc]

I think your right. I have not check with our IT group but we have a high security level on everything else so it probably is the proxy server. I found another local web service and it worked fine. 

Thanks for the help

/Robert

[Lycangeek]

Well, internally we use the .NET framework to generate a .NET interface to the web service, and then wrap that with VIs. You can do it yourself manually via the wsdl.exe program that comes with the .NET SDK.

Just go to www.microsoft.com/downloads and get the .NET 2.0 Framework SDK. Here is the docs for the tool - you can see there is a place to specify the proxy you need to go through.

http://msdn2.microsoft.com/en-us/library/7h3ystb6.aspx

Once you've created the .NET assembly, you can program it directly via the .NET palette in LV. It's pretty straightforward.

In the meantime, I'm opening a bug report so that a future version of the tool will support authenticating proxies.

[Jamc]

I found an example somewhere on ni.com that genereated .NET interface to a web service. The test that I made where on a computer with LabVIEW 7.1 and Framework 1.1 (Normally I use LabVIEW 8.20). I only had time to make a quick test and I could make the interfaces but there were problem when I tried to used them. I do not think that this example specified the proxy server. I have to try this later. Does it matter if you have Framework 1.1 or 2.0?

/Robert

[Lycangeek]

The item you refer to is the "prototype" of the feature we put into LV 8.20, so the proxy generator is very similar. It doesn't matter whether you use 1.1 or 2.0.

If you have a successful proxy generated, you can use it directly. The .NET API of the proxy allows you to set the web proxy information.

See here for more information: http://forums.ni.com/ni/board/message?board.id=170&message.id=176414&query.id=4806#M176414