|
Performance is affected by the type of network, and therefore the type and complexity of devices, data and functionality.
GeoXplorer™ has been successfully deployed in Intranet and Internet networks.
This is arguably the most significant technical component of an Enterprise Web GIS solution, which serves data (information) and applications (functionality) to the user.
- GIS Servers
- Gateway Servers (which are required to support mobile applications, and are described under Information Processing Services and Gateway Servers).
- Web servers
- Application servers
- Map servers
- Data servers
- Combined onto one server
- Divided between many servers (as 'distributed' or 'scalable' solutions), eg.
- The Web & Application server can be one server
- The Web, Application & Map server can be one
- All four functions can be provided by one server (not recommended), or
- Each function can run on several servers
The recommended approach is to have separate servers if budget and technical context permits. The number of servers and their power i.e. number and power of processors (CPU) and memory, affect the performance of a web GIS solution, and its cost. Load balancing can be applied to any of the servers to improve performance.
Web servers communicate with the client devices via the network. These receive requests from the client, invoke the application server, and serve back responses to the client. The web server requests services from the application server.
These manage server transactions and securities. An application server manages requests from the Web server and passes them to the Map server.
Map servers are the workhorses of Web GIS solutions, and performs many functions similar to traditional GIS. The map server processes client requests and generates results. The Map server executes spatial queries and analysis and generates and delivers maps to the client via the application and web servers. It executes the relevant functionality and accesses the relevant data from the data servers.
The data server serves spatial and non-spatial data from relational or non-relational database structures. These servers can be one or many:
- Dedicated GIS data servers - spatial and non-spatial data
- Enterprise data servers, which exist outside the GIS infrastructure
GeoXplorer™ is developed using Microsoft Active Server Pages (ASP) as its application server and the powerful MapInfo® MapXtreme® NT as its map server. It is deployed using Microsoft Internet Information Server (IIS) as the Web server. Data servers can be anywhere in your enterprise, once accessible via networking.
The client is where users interact with spatial data via a Web browser using the functionality provided in the Web GIS, and subsequently view and output the results. Web clients fall into three main categories of devices:
Go to types of client browser interfaces for more information.
GeoXplorer™, which is a medium client, uses a small Java applet, which is downloaded on application start-up. This allows GeoXplorer™ to have more powerful interactive functionality via the browser.
ESBI Computing have a mobile GIS application called GeoMobile, which can be used to provide powerful location based data capture functionality in the field.
The location component of Web GIS technology is delivered through mobile field-based clients with Position Determining Devices (PDE), which can be either :-
- Global Positioning Systems (GPS)
- Triangulated mobile phone cell id's
These components are vital for Web GIS applications which rely on real-time location information on vehicles and staff, or for the provision of Location Based Services (LBS). The mobile devices update the Web GIS with information on their location, or may be used to update GIS databases with changes to spatial and non-spatial data real-time, which are vital for work scheduling and assets management and planning systems.
For more information on this technology go to Position Determining Devices under Mobile GIS.
ESBI Computing's mobile application GeoMobile works with GPS to provide powerful location based data capture functionality in the field.
|