Currently there are a number of mechanisms that allow external applications to exchange data with the Delft-FEWS. Importing and exporting data via a number of possible file formats is used in current operational systems.
Other, more interactive, methods have been developed and are described in this section. Up till now these mechanisms are not fully developed yet. They have been set up as test cases, each with a particular goal in mind. The following sections will give a description of the current status of these projects, what their strong points are and what their weaknesses are.
The Delft-FEWS Web Services provide different web services API's to exchange data with FEWS.
Fews JDBC server provides a simple JDBC interface. The FEWS JDBC server uses an OC region configuration and initializes a synchronization process with the MC to update the data. The client application sets up a connection to the JDBC driver and uses SQL queries to retrieve data. Currently it is only possible to retrieve data from the FEWS system and not write data to the FEWS system.
Fews Workflow runner service provides a simple API using a SOAP framework called XFire. The SOAP framework is set up by passing a configuration file as an argument in the main method of the service runner class. Once the service is started by the runner class, the client application uses XFire to retrieve a proxy of the API. With the proxy instance the client application can run single task workflows on the MC. On running the a workflow the client must pass the input timeseries arrays as argument to the proxy. The output timeseries produced by the workflow run are written to output files configured in the configuration file.
- FEWS Web Services
- FEWS PI REST Web Service
- FEWS PI SOAP Web Service
- FEWS Web Mapping Service with time support (WMS-T)
- FEWS Schematic Status Display (SSD) Web Service
- WaterML2 Web Service
- Embedded - Fews PI service
- Fews Data Access Component
- Fews JDBC server
- Fews Workflow Runner service
- JDBC vs. FewsPiService