07-26-2015 04:23 PM
Hi community,
I'd like to know what does it mean when I publish a labview web service. I havent nocticed anything really.
thx!
07-26-2015 05:58 PM
07-27-2015 03:03 AM
I have created a website in the range of medium complexity (databases, communication to other PCs via datasocket, user management etc), and I never had to publish my webservice in order to make it work properly.
I also studied the tutorials, but never found the reason why should I publish my webservice or what is the meaning of the publish at all.
Can you send me a link which explains it?
thanks!
07-27-2015 03:32 AM - edited 07-27-2015 03:33 AM
'Publishing' your Web Service packages it up and installs it on the NI Application Web Server running on your machine so that it will run even if LabVIEW is not running. 'Starting' the web service runs it on the local application instance in the development environment (on a different port).
You can also probably just open your web files directly on the operating system - publishing to the web service allows you to access them remotely via a web address (e.g. http://localhost/WebServiceName).
07-27-2015 10:49 AM
Checkout the example finder example. I think there is really only one dealing with a weather station. It works to show a few ideas well, but only demonstrates the GET method and not the others.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
07-27-2015 10:55 AM
I did, and I am way beyond that. I have a website with multiple databases, a proper user interface, user management with credential managment, automated emails, datasocket communication to computers in different coutries, POST and GET methods etc, but I still dont understand what the publish does for me.
I need to get deeper in Sam's answer.
07-27-2015 11:46 AM
@1984 wrote:
but I still dont understand what the publish does for me.
It deploys the web server. I'm working from source right now, but lets say I'm in my project and I update the code that gets ran on a GET. That new code won't be called until I perform a publish, in this case by right clicking it in the project and pick deploy.
I see this as something that parallels RT targets. You deploy code to an RT chassis, and then when you make changes, you need to deploy those changes which is what the publish does. Of course the EXE has the ability to publish as well if it is configued to work that way.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord