$LVSERVER_ROOT in niwebserver.conf (LabVIEW 2009)

[hecmar.arreola]

Hi!

I'm trying to figure out how to get remote panels working in my built applications programmed in LabVIEW 2009.

I followed this guide for LabVIEW 8.6:

http://digital.ni.com/public.nsf/allkb/7F95D43D3F50FCAC8625710E000068E1

It looks like the niwebserver.conf file has some new features.  One that I'm curious about is this $LVSERVER_ROOT.  I can't figure out where this points to, and how I change this variable.  Is this something I can set somehow if I make an installer?

It it adds more flexibility for me to make a generic niwebserver.conf that requires less modifications on each of my target hardware platforms, then I'd like to know more about it so I can use it instead of entering in hard directory paths.  I just can't find any documentation on it.

[NathanK]

We put in the $LVSERVER_ROOT alias in 2009 specifically to make the web server easier to configure for built executables.

In 8.6 the $SERVER_ROOT alias was set to LabVIEW's web server directory (LabVIEW/resource/webserver). All relative paths in niwebserver.conf were therefore relative to this location. This turned out to be a real hassle for built executables as I'm sure you've noticed. All the paths had to be absolute paths and that made installation difficult.

To fix this problem in 2009 we changed things a little. We added the $LVSERVER_ROOT alias that points to LabVIEW's web server directory. That alias is used to find any of the web server's own files like the modules or mime.types file. You shouldn't need to use this alias. The old $SERVER_ROOT alias is set to the directory that the configuration file is in. In 2009 all relative paths in niwebserver.conf are relative to the location of the config file itself. This change should allow you to use relative paths in a generic niwebserver.conf and not need to hard code the absolute paths on each target.

Let me know how it goes.

Nathan

[hecmar.arreola]

Ok, so if I understand your post correctly, the $LVSERVER_ROOT is not something that I should need to change at all.

I'm glad NI is making it easier to enable remote panels in application builds.  I thought that the changes for this in 8.6 were really good and made things easier.  I haven't had success with my LabVIEW 2009 build, but I also haven't gone through much trouble shooting yet.  Most likely a firewall issue.

It looks like, in order to enable web servering, you still have to add a line to the .ini file or specifiy a custom one in the build parameters.  You guys might want to consider adding a Remote Panels option to the build dialog box in order to make things even easier.

[Joachim082]

Hi,

what have you added in the ini-File? I've also problems with my webserver on my cRIO 9022. What have changed in LV2009? I've attached the ni-rt.ini

and also the niwebserver.conf (only renamed in the attachment). When I open the rt-device on the webbrowser I don't get any response - webserver is not running. Any suggestions?

Regards,

--
Joachim

[The_Chancenator]

Hi Joachim,

Based on this discussion forum, it doesn't look like you should need to change anything about your *.ini file in LV 2009. Additionally, they are referring to the ini file that is generated by the application itself (named application.ini by default), not the RT or Webserver ini files.  Are you able to get the webbrowser running outside of an executable?

[hecmar.arreola]

Hi Chancenator,

See my post here: http://forums.ni.com/ni/board/message?board.id=170&message.id=439052#M439052

-Nic

[The_Chancenator]

Thank you, Nickerbocker.

[Joachim082]

Nickerbocker,

On a windows machine I've got no problem during the upgrade process from 8.6 to 2009. But on a rt machine neither on a crio nor on a desktop pc the webinterface is running as expected.

A little bit curious is that the path of the rt machine is automatically set to D:\ni-rt\system\www although the system path has to be c:\ni-rt\system. I've attached a screenshot of the webserver dialog.

Regards,

-- 

Joachim