Page History

...

1. FEWS configuration file Explorer.xml  in the directory  SystemConfigFiles
   1. the  dateTime  section  
      1. In order to hide the year within FEWS, the dateTimeFormat must be configured accordingly.  
      2. The cardinalTimeStep  should be consistent with fewsSystemTimeUpdateInMinutes . Indeed, it makes no sense to set it in the WaterCoach to 1 minute, while it is set to 1 hour in the FEWS configuration (although this will not cause any problems in the game). (obsolete as of FEWS release 2013.02)
      3. The element adjustSystemTimeAutomatically should be set to 'true' (this is the default), otherwise it will not be possible for the WaterCoach to alter the systemTime during the game. (Also make sure that you don't have a T0 configured in the global.properties file).

   2. To have a pop-up appear with new messages, vjdbcServicePortRange needs to be configured in Explorer.xml. This same service is also required for the participant mode. Note: by specifying this range the vjdbc service is started. This part of the configuration can be kept the same in the live system, but be aware that this means that this service will be started in the live system as well.

      Code Block
      xml xml
      <vjdbcServicePortRange start="40402" end="40402"/>

   3. Note: this change is no longer required with the embedded WaterCoach: The port number  fewsPiPortNumber for the FEWS PI service has to be in the range of port numbers that must be specified in Explorer.xml . Note: by specifying this range the PI service is started. This part of the configuration can be kept the same in the live system, but be aware that this means that the PI service will be started in the live system as well.

      Code Block
      xml xml
      <piServicePortRange start="50505" end="50505"/>

   4. To distinguish the FEWS configuration for the WaterCoach, one could change the name and panel labels. The name of the Explorer window is configured with systemCaption and the name of the panels with panelHeaderLabels . For example, the term TRAINING or SERIOUS GAME could be added to the captions of these panels.  (obsolete as of FEWS release 2013.02 since the FEWS user interface contains a yellow border when operated in WaterCoach mode)
2. Depending on the set-up of the scenario and script database, an additional change could be required, see Scenario and Script database.
3. Note: with some configurations at the start-up of fews via the WaterCoach, the error message 'Fault occurred' may occur. This message can be ignored. 
4. Since all data for a scenario is pre-loaded in the FEWS local data store, it is desirable to hide certain data after the current system time, e.g. measurement data. This can be accomplished by specifying hideExternalHistoricalAfterSystemTime=true in the file global.properties , which is located in the FEWS configuration directory. As the name of this key implies, only time series of the type "external historical" are hidden; time series of the types "external forecast", "simulated historical", and "simulated forecast" are completely visible. As of FEWS release 2012.02, this step is no longer required.

...

• The master WaterCoach session needs to make her LocalDataStore shareable using the F12-P function within the Fews application. In the future this action will be done automatically, if the WaterCoach application is so configured. As of FEWS release 2013.02, this step is no longer required, as long as the vjdbcServicePortRange is configured in SystemConfigFiles/Explorer.xml to a specific port, e.g.: <vjdbcServicePortRange start="200040402" end="200540402"/>. Note: this addition should be only made in the master WaterCoach configuration, and not be included in the configuration of the participant WaterCoach sessions. (01 FEWS Explorer)
• Start the embeded vdjbc server using the F12-L option. This action provides an IP adress and port number in the log-window of the Fews application. These should correspond to the IP adress and port defined in the client_config.xml file of the particpant WaterCoach sessions. Replace by next step (url).

• The particpant WaterCoach session(s) should link to this embeded vjdbc server by configuring this in the clientConfig.xml of the FEWS application, see configuration example. Note: the participant WaterCoach sessions should not have the vdjbc server configured in the Explorer.xml

• The master WaterCoach session can not be used for the training, because LocalDataStore of its Fews application is not updated by changes made by the participant WaterCoach sessions.

• The participant sessions also need access to the ScenarioScriptDatabase (SSD). They won't make use of the scenario, but they will make use of the script, to generate messages. If the SSD is not available, the WaterCoach Display will no start up properly.
  

  With the embedded WaterCoach (2016.01 and up) the master WaterCoach session can be used for training and the LocalDataStore of its Fews applications are updated by changes made by the participant WaterCoach sessions.

   

...