Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Code Block
<?xml version="1.0" encoding="UTF-8"?>
<clientConfiguration xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/clientConfig.xsd">
	<clientType>Stand alone</clientType>
</clientConfiguration>

 

The only requirement for running the FewsWebServices is that a default filter is configured in FEWS. This can be done in two different ways:

Configure a default filter in the Filters.xml of the FEWS configuration with the name of the filter that should be used for all

webservice requests.

web service requests. "${catalina.home}/fews/Region_Home/Config/RegionConfig/Filters.xml"

 

Code Block
<?xml version="1.0" encoding="UTF-8"?>
<filters version="1.1" xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/filters.xsd">
<defaultFilterId>All</defaultFilterId>
...

 

Alternatively a property file can be used to configure the default filter (and other properties as well). The property file should be located at: "${catalina.home}/fews/Region_Home/Config/PiClientConfigFiles/FewsPiService.properties". In the following code snippet the default filter to be used by the FEWS Web Services is configured using the property key "FILTER_ID" where the filter "All" has been configured.

 

 

Code Block
FILTER_ID=All

 

N.B.: In version before FEWS 2017.02 it was possible to override the FewsPiService.properties with another name or location. This is no longer supported. Only one property file can be used for all services and the name is fixed.

If the previous configurations have been applied

 

, the FewsWebServices.war can be installed using the standard installation options of Tomcat. See the tomcat deployment documentation for more information.

 

 

 

Migrations from before 2017.02

In case an existing FEWS web service has to be migrated to the 2017.02 or later version, the following changes should be taken into account.

URL

...

changes

FEWS PI-XML Web Service

The change that has the largest impact on the URLs of the Web services is the changed context path (the URL part after the servername + port). Before 2017.02 every FEWS Web service has its own context path. Since 2017.02 all webservices have the same context path, which is FewsWebServices by default.

For example before 2017.02 the URL endpoint of the FEWS PI-XML Web Service would be: http://localhost:8080/FewsPiServices/fewspiservice

Since 2017.02 it is: http://localhost:8080/FewsWebServices/fewspiservice

If it is required to keep the endpoints backwards compatible, the FewsWebServices.war can be renamed into FewsPiServices.war.

PI-XML REST Web Service

For the PI-XML REST Web Service it is not possible to keep the endpoints backwards compatible since the "rest" path is now a required part of the endpoint.

http://localhost:8080/FewsWebServices/rest/fewspiservice

 

ToDo

Migration manual:

Removing dac.jar -> Also remove LifeCycle listener from server.xml

Wat als er gestart wordt met een firebird local datastore?

FewsPiService.properties verplicht? Ook als er geen filter is geconfigureerd?

"No default filter id defined! Either configure the default filter id in Filters.xml file or configure FILTER_ID in FewsPiService properties file in the PiClientConfigFiles folder of the FEWS configuration"

umaquo uit test pages gehaald.

Temp en Work folder leegmaken. Niet weggooien!.

Bij fouten controleren of the temp dir bestaat.

clientConfig.xml required?

Patches?

...