dremas

Thank PiDi. I have tried a few variations on that idea, but no luck yet :-(

Hi all, I have been playing around for days trying to solve a seemingly simple problem: In 2013 Web Services, the port is set in the build spec. However, when running multiple instances, the ports need to be different between instances.  There is a property node for setting "websrvr.port"  but it doesn't seem to have any effect.

Has anyone had any luck setting the Web Service port programmatically, or from a command line argument? Right now this is a huge blocker for being able to set up web services at all, so I appreciate anyone's thoughts.

It turns out that the port is in niwebserver.conf, which can be loaded programmatically in the code. You just need two config files, and you can change the port from a Property Node: http://zone.ni.com/reference/en-XX/help/371361G-01/lvprop/app_web_server_configure/

Along these lines, has anyone been able to set the port through command line arguments? I want to run multiple instances of the same application on a pc. If the port must be part of the build spec, then I'll have to create separate executables for each port I want to enable :-(

Hi all,

I'm creating a LabVIEW Web Service in LV2013. So far it's been great, but there is one feature I can't find. The "Set HTTP Response Code.vi" doesn't take a string as an input. So I can provide an error code, but no detail string! To make matters worse, if I report a 4xx, the response body is not passed on, so I have to hack the error into a header. There must be a better way. Has anyone encountered this yet?

Thanks,

-O

Thanks Shaun, that works perfectly and is quite flexible!

Hi all,

Any thoughts on the simplest way to trigger a LabVIEW event using an external script in Windows? I want to be able to poke my LabVIEW application and kick off a predefined code block. No need to pass any information/message.

I'm looking for something very passive, unlike, for example, a listening TCP socket.

Thanks!