LabVIEW DCSS

[amragman]

Hi,

I want to setup Double Client Server Structure for making my VIs accessible through internet. Here's what I am looking forward to implement

1. Run Web server on a say linux system which had public IP.
2. The Web page published using a VI system, will be available on this web
server. This should know, for each experiment where is the VI server
running.
3. The page should have all the front end VIs.
4. They in turn will contact the corresponding VI servers and update the
front panels.

The problem is I am not able to figure out how to do this. I've tried Web Server but that runs on the same machine as VI. Please help.

[Ben]

To get more help with this you should post an image illustrating what you want to accomplish.

On the surface this sounds like a "remote witnessing" application where you want a single web-page that get you started and then does the re-directing to the appropriate target machine.

Ben

[amragman]

I am trying to setup a Virtual Lab.

Currently, the machines hosting the virtual experiments are directly accessible through the internet (Image: http://yfrog.com/5015876457j). So each machine needs its own public IP and they are vulnerable to security threats too. Clients access the VI embedded in a webpage.

I am trying to modify it as following (Image: http://yfrog.com/3w31128833j😞

I have a centralized linux server running LabVIEW 8.5 and having a public IP. The machines hosting the virtual experiments (having local IPs) should be accessible through this server. What I mean, is the server should host the VI embedded web pages for each experiment. When a client requests a VI he would be displayed the appropriate VI and server should forward all the requests for that VI to the appropriate machine.

I think this is possible through VI server but I am unable to figure out how.

[Ben]

First let me set your expecations.

This is going to require a bit of work. AS you move along break up the challenge into bite-sized chunks and handle them one by one posting new Q's for each puzzle.

Inthis thread starting at post #39  I posted a brain-flush outlining how the LabVIEW community could set up a web-site to allow us to particiapte in virtual robot wars. Please take a look at what I posted there and give it some thought.

I would be very interested in any posts that can simplify this approach.

Ben

[amragman]

From your post I got this idea:

 Whenever the client requests a VI for an experiment a new process is spawned off, that handles the user session for that experiment, forwarding him to the machine that hosts the Experiment. If this is the case, then won't the machines still be be needing a public IP? 

[Ben]

---

amragman wrote:

From your post I got this idea:

 Whenever the client requests a VI for an experiment a new process is spawned off, that handles the user session for that experiment, forwarding him to the machine that hosts the Experiment. If this is the case, then won't the machines still be be needing a public IP? 

---

If you just redirect the user to that machine yes.

If your public machine acts in the users behalf, then the server could host FPs for each experiment. Those FPs could then use VI server to update values. So the user still interacts with a LV app on the public mahcine but the public machine turns around and checkes the private machine (via VI server or other update methods). I don't expect this reply helped much aside from giving you another term (VI sever) to look into.

Ben

[amragman]

---

Ben wrote:

---

If your public machine acts in the users behalf, then the server could host FPs for each experiment. Those FPs could then use VI server to update values. So the user still interacts with a LV app on the public mahcine but the public machine turns around and checkes the private machine (via VI server or other update methods). I don't expect this reply helped much aside from giving you another term (VI sever) to look into.

Ben

---

Hey this is the approach we've been on...I was stuck at how to configure VI Server for this.

[Ben]

---

amragman wrote:

---

Ben wrote:

---

If your public machine acts in the users behalf, then the server could host FPs for each experiment. Those FPs could then use VI server to update values. So the user still interacts with a LV app on the public mahcine but the public machine turns around and checkes the private machine (via VI server or other update methods). I don't expect this reply helped much aside from giving you another term (VI sever) to look into.

Ben

---

Hey this is the approach we've been on...I was stuck at how to configure VI Server for this.

---

Depends on what you mean by "configure VI Server". In one of my remote witnessing apps, the GUI is just a thin layer calling VI Server invoked Action Engines to get teh updates and pass user actions.

Ben

[amragman]

By "configure VI Server" I mean how do I implement the above mentioned thing through VI Server. Please pardon my knowledge of VI Server, I am new in that area.

[Ben]

First a suggestion on hwo to use this forum...

I and many of the contributors to this forum are volunteers so you can't expect anyone of us to reply. We also have our own jobs so we appreciate people who want to learn but are willing to do the leg-work themselves.

So go to the LabVIEW help and  serach for the example on using the VI server. You can start with the example running a client and a serve on the smae machine. After you get that working move to getting it working across two machines. Any error codes you get should be in the forum somewhere so search out those to get it working.

If you run into trouble, post everything you have so far along with a clear question and hopefuilly one of the volunteers will help out.

I am telling you this because I don't want you to depend on me sonce I can disappear without notice when I go off to help one of my paying customers.

So...

Serach the examples, try it yourself, post with code, and have fun!

Ben