Page History

...

The WaterCoach can be used in the so called participant mode. In that case there is one "master" WaterCoach session, which controls the LocalDataStore as used by Delft-FEWS. The other students start up the WaterCoach and make a connection to this same LocalDataStore. For this the shared LocalDataStore should be available to all students (e.g. network, citrix, internet). Also, some actions are necessary.:

• Master WaterCoach:
  
  • The
  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="40402" end="40402"/>, (01 FEWS Explorer).
    
    • Note: this addition should be only made in the master WaterCoach configuration, and should 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).
• • Needs access to the ScenarioScriptDatabase (SSD), to load the scenario as well as the script.

• Particpant WaterCoach(es):

  • Should link to the embeded vjdbc server run by the Master. This is configured in the clientConfig.xml of the Delft-

  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

  • 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.

• • .xml

  • Also
  The participant sessions also
  • need access to the ScenarioScriptDatabase (SSD)
  . They won't make use of the scenario, but they will
  • , to make use of the script
  ,
  • and 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
  • .

   

...

Examples

...