TheDataWeb Service Oriented Architecture (SOA).
Speed is very important
Edit
Expanded Data Services

'DataWeb' Server list of Services

TheDataWeb is a Service Oriented Architecture.

• Written in pure Java
  • Provides excellent portability across all hardware and vendor platforms
  • Provides an advanced security module
    • Using the Java sandbox for security both on the server and clients
    • Prevents classical security programming leaks typical of C, .Net, etc.
    • DataWeb^? is a multi-layered security system
    • DataWeb^? must meet all Federal Security Requirements.
• SOA architecture provides scalability to hundreds of distributed servers using utility compute model (currently support approximately 50 servers)
• DataWeb^? has built in distributed monitoring of services to insure reliability of remote services.

Definition of a Service: When referring to a “Service,” we are referring to one or more servlets that provide a specific function in TheDataWeb system. These services are easily installed. Install the TomCat Java Server(or any other Java Server) and copy the appropriate Java Web Archive (WAR) files to the appropriate directory that Tomcat will read to start any service. TomCat can act as the primary webserver or it can connect to Apache or IIS which can be used as the primary webserver. These services can all run on a single computer or be distributed across machines across the world. Installation should be simple, for Microsoft there is a simple Install shield, for Linux and other flavors of users, simple scripts. We can include a simple open source database if desired.

Required Services--------------------------------------------------

{These are the required, metadata services, GIS services etc. can be accessed from remote locations}

Administration Service (AdminServer / TheDataWeb_Admin.war)

The Administration Service is responsible for keeping TheDataWeb system alive. More details in Docs_AdminServices.

Tabulation and Extraction Service TabulationServer / TheDataWeb_Tabulation.war)

The Tabulation Service is responsible for receiving the tabulation or extraction requests from the Data-Web tools. More details are in Docs_TabulationService

Optional Services ----------------------------------------------------

{A local datasource can access these services remotely or can mirror them locally}

Metadata Service (MetadataServer^? / TheDataWeb_Metadata.war)

MetadataService
The Metadata Service processes queries that retrieve the metadata to be presented in 'DataWeb' services and tools.

Login Service (LoginServer / TheDataWeb_Login.war)

The Login Service is responsible for restricting access to specific datasets and functions.

DataFerrett Service (DataFerrettServer / TheDataWeb.war)

The DataFerrett Service contains the html files that allow the DataFerrett tool to access local metadata. It also contains jpeg files for the DataFerrett applet and html pages. The DataFerrett Service allows a user to use the applet from whichever server the DataFerrett metadata is on. The DataFerrett Service also contains a table shell servlet that allows users to run numerous DataFerrett tables in batch mode.

Geography Service (MapRequestServer /TheDataWeb_MapRequest.war)

The Geography Service formally called the (Map Request Service) is responsible for receiving a request from a 'DataWeb' servier or tool and returning a map or other geographic object.

Gateway Service (TransferServer / TheDataWeb_Transfer.war)

The functionality of a Transfer Service is similar to a proxy server. This service forwards a request from a 'DataWeb' tool to the appropriate service.

Hot Report Service (HotReportServer / TheDataWeb_HotReport.war)

The 'HotReport' Service creates dynamic web pages on the server. These dynamic web pages are defined by the 'HotReport' Authoring Tool found in DataFerrett.