Versions Compared

Key

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

...

http://localhost:8080/FewsWebServices/wms?SERVICE=WMS&VERSION=1.3&REQUEST=GetLegendGraphic&LAYERS=Wind_forecast_nwp

 


 


Properties

 

The following WMS specific properties can be configured in the FewsPiService.properties file.

 

  • WMS_BASE_URL: url that will be reported in the GetCapabilities response as URL to be used to request maps.

  • WMS_CLIENT_CACHE_TIMEOUT: Timeout of the cache in seconds, that is sent to the browser. default is 84600 seconds (one day). To disable caching, set the timeout to 0.

  • WMS_ALLOWED_GRID_PLOT_GROUP_ID: Id of the grid plot group which layers will be made available in the WMS service. If not configured, all layers are available.
  • WMS_IMAGE_MAX_WIDTH_HEIGHT: The maximum size of the WIDTH and HEIGHT product GetMap parameters. The default is set to 2304000 (the full HD resolution of 1920x1200). N.B.: The higher this value is set, the more memory is required to generated the WMS images.

ICT requirements

 

For general FewsWebServices requirements, see: 

Specific requirements Requirements for the FEWS WMS service very much depend on the number of layers that are used and the size of the layer grids. 

To avoid memory issues the number of layers should be restricted by specifying the WMS_ALLOWED_GRID_PLOT_GROUP_ID property.

The and the tomcat server the FewWebServices.war file WMS service is running in on should have sufficient memory. When many concurrent users are using the WMS service the CPU requirements will increase as well since all images have to be rendered at the same time on the same server.

 

Since the WMS service is stateless, it can be easily scaled up by using multiple tomcat instances and a load balancer in front. 

Tomcat itself can also be tuned by specifying the number of concurrent requests. In case memory errors occur, the tomcat server.xml can be tuned to limit the number of concurrent requests. In the tomcat server.xml the maxThreads parameter specifies the maximum number of concurrent requests that are allowed. For Tomcat 7 this is set to 200 by default, which is quite a lot for a WMS service. See the following example where the tomcat server.xml has been configured with a maximum of 50 threads.

 

 

 

Code Block
<Connector port="8080" maxThreads="50" minSpareThreads="10" maxSpareThreads="20"
               enableLookups="false" redirectPort="4443" acceptCount="100"
               debug="0" connectionTimeout="60000" 
               disableUploadTimeout="true" />

...

The following WMS specific properties can be configured in the FewsPiService.properties file.

...

WMS_BASE_URL: url that will be reported in the GetCapabilities response as URL to be used to request maps.

...

WMS_CLIENT_CACHE_TIMEOUT: Timeout of the cache in seconds, that is sent to the browser. default is 84600 seconds (one day). To disable caching, set the timeout to 0.

...