Page History

...

• 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="40404" end="40404"/>. Note: this addition should be only made in the master WaterCoach configuration, and not be included in the configuration of the participant WaterCoach sessions.
• 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.

  Info
• The participant sessions also need a copy of 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.titleNote on master WaterCoach session
  

  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.

   

Examples

...