As I've stated before, if you don't use an embedded object then the only thing that a browser understands is HTML. For the example you provided this means you need a web page that has the following things on it:
- textbox for entering a start date
- textbox for entering an end date
- an image that is the graph
- a "Submit" button
Note that these would all be standard "web" elements, not LabVIEW elements.
Clicking the "Submit" sends an HTTP GET request to the server. The server needs to handle the GET request and send HTML back to the client. One way to accomplish this is to essentially create a LabVIEW app that the web server can call with the start/end dates and the LabVIEW app simply writes the graph image to disk. The server returns an HTML page to the client that includes an <IMG> element pointing to the image that the LabVIEW app created. The LabVIEW app can be an executable or a DLL. Your call. In fact, for this you would not need the Internet Toolkit. The web server would, however, require the LabVIEW Run-Time Engine in order to actually run the LabVIEW code.
The advantage of the above suggestion is that you don't need to have an additional web server (the LabVIEW web server). You already seem to have a web server in your configuration so you
just need to create the web page using your favorite server-side scripting
language. The content is actually not complicated.
A completely different suggestion: If all you want to do is to display data in a graph then you can implement a non-LabVIEW solution for the web. According to your configuration the data is stored in a database. Well, you can create web pages that get data from databases based on user inputs pretty easily, and you don't need LabVIEW to do that. If you want to display data in a graph then you can probably use a server-side control to create the graph and generate an image from it. For example, for .NET there's
ZedGraph.