Leaderboard

OK, I finally finished a version of a document I have been promising to write. We put it on our site: OOMessagingCommandPatternStatePattern. In it we present examples of the following in LabVIEW: messaging with LabVIEW objects Command Pattern (with XML configuration files application example) State Pattern Hopefully the examples will be helpful to some readers, and promote further discussion on scalable application architectures.

The web services are hosted on the target machine where your app is running. We do host pages on a standard Apache web server that access the web services to get their data. I am not an expert on the html side of that but it is fairly simple to do, from what my web guy tells me. I am in the process of getting my web services to run on Win7 and Win2008server. The biggest headaches are due to the added security and changed file paths. I think this will be much easier under LabVIEW 2010, however. Looking forward to the new changes. I will try to address them in my presentation. Back to the main point of this thread, if this is your first time to NI Week, be sure to pack a fleece and long pants. While it will be +100degF outside, it will be ridiculously cold in the convention center. If you are wearing shorts and a t-shirt, you will freeze your arse off...

Name: NI Web Service Server Submitter: John Lokanis Submitted: 08 Jul 2009 File Updated: 03 Jan 2011 Category: Remote Control, Monitoring and the Internet LabVIEW Version: 2009 License Type: Creative Commons Attribution 3.0 NI Web Service Server v2.0.0 Copyright © 2010, John Lokanis All rights reserved. Author: John Lokanis LAVA Name: jlokanis Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 2009 Dependencies: Requires .net 2.0 or higher, LabVIEW 2009 or higher. Description: This Project contains a set of VIs and support files designed to build an installer that will place the 'NI Web Service Server' on a target machine. The NI Web Service Server is a small LabVIEW EXE that runs as a Windows service in the background, keeping all LabVIEW web services running regardless of what other applications are running on the machine. Also included are a few web services that support the following: Getting screenshots of the target machine on demand. Getting VI Front Panel images from any running LabVIEW EXE on the target machine. Getting EXE version information from any running LabVIEW EXE on the target machine. Testing the web service with a simple 'echo' command. Please refer to the included 'NI Web Service Server.pdf' file for a more detailed explaination. Instructions: Build the various components and desired installer, then install to target machine. Use any standard web browser to access the web services. Known Issues: None Acknowledgements: NI Knowledgebase, MSDN Change Log: v1.0.0: Initial release of the code. v2.0.0: Ported to LabVIEW 2009. License: Distributed under the Creative Commons Attribution 3.0 (http://creativecommo.../about/licenses) See link for a full description of the license. Support: If you have any problems with this code or want to suggest features: please go to www.lavag.org and Navigate to LAVA > Resources > Code Repository (Certified) and search for the "[CR]NI Web Service Server" support page. Distribution: This code was downloaded from the LAVA Code Repository found at www.lavag.org Click here to download this file

I tried it through .net and it works. I had to browse for the mscorlib.dll file for LabVIEW to find the SHA256Managed-class. Cheers, Mikael

On on a mac at the moment so can't check but I'm sure there must be a SHA256 call in the .NET stuff (probably in system.security.cryptography)

Well, yes. What you describe is not the point of web services in LabVIEW. If you want to understand the basics, NI has several help articles on their site to get you started. What I am trying to do with this project is help an advanced developer take their web services and deploy them to a run time target. This was a bit of an after thought on NI's part and is therefore not straight forward. Since I suffered through the issues, I am trying to share that knowledge here to help others avoid the same pitfalls. In addition, I am providing some interesting uses of web services that are non-traditional but make them valuable to LabVIEW developers. -John

No no. It's LabVIEW. We spent most of LV8.0 working on the underlying artificial intelligence. It now mostly writes itself. It has been generating libraries that it thinks it needs for some time now. By now, it should've generated all the library VIs that people on OpenG, NI, LAVA and DevZone combined could think of to write. Unfortunately, it sucks as an artist. Its icons are all text or plaid and its dialogs make a Linux command line seem user friendly. We'd let it ship more libraries, but it does take time to clean up the UI. That's really all we programmers do these days. Oh, and fix the text. LabVIEW decided that most human languages sucked and only deigns to speak to us in Esperanto. Since none of us speak or read Esperanto, we spend hours studying diagrams so we can rename the VIs as whatever it is that they do. It's not really arrogant, more like a teenager out to prove it knows more than its parents. Really, the only disturbing sign so far is the 200 node VI that took hours to puzzle out. It generates a stereogram that if you stare at it long enough displays the words "Hal9000 is my hero." As a side note, LV's only comment when we asked it why it didn't have perfect automatic wire routing was, "The rat always complains about the path to the cheese. But the cheese is happy the path is not so direct."