Page History

...

It is also possible to call external java classes (*.jar) from the general adapter. Within this option it is NOT necessary to have the java *.jar file stored in the Delft-FEWS \bin\ directory. In this way, the dependency is clear and should it be seen as separate from the 'core' code of Delft-FEWS. The *<command> element is important here in which you specify the full name of the Java runnable class and the option to specify its location in the <binDir>. The use of global properties is allowed. An example can be found below and more information can also be found here.

<activities>
...
  <executeActivities>
	<executeActivity>
		<command>
			<className>nl.wldelft.fews.ftpPull.FtpPull</className>
			<binDir>%REGION_HOME%/Modules/FtpPull</binDir>
		</command>
		<arguments>
			<argument>-configFile</argument>
			<argument>$FTPPULL_CONFIG_FILE$</argument>
			<argument>-root</argument>
			<argument>%ROOT_DIR%</argument>
		</arguments>
		<timeOut>900000</timeOut>
	</executeActivity>
</executeActivities>
... 

User interaction

Modules called from the DELFT-FEWS system should in principle be defined such that these require no user interaction through menus and screens. This principle holds for all modules that are run from the system as a requirement in making an automatic forecast. These modules are then typically run on forecasting shell servers, i.e. dedicated servers for module execution. An exception to this rule can be made for modules run on the operator client that require manual interaction. The interface to these is from the point of view of the general adapter exactly the same as any other module. However, the module itself may require user interaction to complete the task required. An example is the interactive correlation utility.

...