Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 2 of 2 total
Thread Environment Options Internal Web Server - How are resource names actually used?
Sun, Jun 5 2016 3:09 AMPermanent Link

Sidney

Here are my "Environment Options" for "Internal Web Server":

DataSets Resource Name = datasets
Custom DataSets Resource Name = customdatasets
Custom DataSets Module = RoverModule (changed from datasetmodule)
Modules Resource Name = modules

What specifically are the resource names used for.  There purpose seems to be hidden in the Internal Server and I have been unable to locate documentation that describes how they are actually being used.  Section 2.17 of the EWB2 manual refers to section 7.5 in the manual on "Creating Web Server Modules" but it never indicates how these resource names are being used.  For the internal server, it appears the bin/datamodules/win32 folder is the location of the DLL's.  The documentation seems to indicate it will be <domain>/modules on the actual web server.

Can you explain what these resource names are doing on the internal server?

Can you explain if they are used on an external server and if so how?

I will be testing EWB2 using several different servers starting with IIS if the answers are server specific.

Thanks
Sun, Jun 5 2016 12:07 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 6/5/2016 3:09 AM, Sidney wrote:
> Here are my "Environment Options" for "Internal Web Server":
> DataSets Resource Name = datasets
> Custom DataSets Resource Name = customdatasets
> Custom DataSets Module = RoverModule (changed from datasetmodule)
> Modules Resource Name = modules
>
> What specifically are the resource names used for.  There purpose seems to be hidden in the Internal Server and I have been unable to locate documentation that describes how they are actually being used.  Section 2.17 of the EWB2 manual refers to section 7.5 in the manual on "Creating Web Server Modules" but it never indicates how these resource names are being used.  For the internal server, it appears the bin/datamodules/win32 folder is the location of the DLL's.  The documentation seems to indicate it will be <domain>/modules on the actual web server.


They represent the URL resource that web server hosts the data on basically.

In order to use EWB dataset functionality we need both sides to agree on
how data is accessed:
- web server needs to host the data thru some URL/parameter combination.
This is basically your dataset resource

- client (ewb app) needs to use the same URL/parameters. Client needs to
basically refer to whatever the server resource URLs are (so if you
change the server side you also need to modift your EWB app client side)

- they need to agree on format (this one is EWB JSON format that is used
underneath)

So in default mode if you use EWB dataset functionality the server will
host the dataset on a URL similar to this (this is from 2.05 beta using
the "databound" sample so both database and dataset in this case are
"databound" as this is what they are named in sample project):

http://<sererv>/datasets?method=<rows/columns>&database=DataBound&dataset=DataBound


This is where the "datasets" name comes from - you can of course change
it but then make sure your EWB app properly refers to correct uirl resource.

Custom datasets and custom dataset module are similar except for custom
module URL resource and actual module name - see also help for these
here :
http://www.elevatesoft.com/manual?action=viewtopic&id=ewb2&topic=Configuring_Server


> Can you explain what these resource names are doing on the internal server?

Identifying the URL resource there data is hosted on

> Can you explain if they are used on an external server and if so how?

Same if you're taking about EWB web server thing - identifying the URL
resource there data is hosted on.

EWB web server has the dataset hanlding automagically built-in.


> I will be testing EWB2 using several different servers starting with IIS if the answers are server specific.

These answers are EWB web server specific.

If you're using IIS then you need to write your own back IIS handling
for all of these. Assuming you want to use the same URL resource
patterns then you need to implement ISS back end to parse and return
proper JSON data (including handling of updates and deletes etc beyond
simple queries).

Web server debug tools combined with the EWB web server are your friend
to easily and quickly map this all out.

Raul
Image