...
- workflowId: identifier of workflow to run
- systemTime: (optional) overruling system time for running workflow
ExportTimeSeriesActivity
Exports the given time series to PI formatted file.
...
Let process sleep for configured amount of milli seconds
Workflow test runs can either be started from within a FEWS stand-alone application, or within a JUnit test.
...
Workflow test runs can be started from the command line. To do so one must configure a Region as they would for a Stand Alone system.
Before 2014.02
Before 2014.02, configure in the bin directory the 'Region.exe' and 'Region.jpif' files. For the JPIF file some adaptation must be made. Here is an example:
| Code Block | ||
|---|---|---|
| ||
..\jre
-mx256m
-cp
$JARS_PATH$
nl.wldelft.fews.system.workflowtestrun.WorkflowTestRun
Region_Name
..\path_to_your_config_test_file.xml |
Before 2018.02
From 2014.02 to 2017.02, this was done via an ini file:
| Code Block | ||
|---|---|---|
| ||
#Delft-FEWS ini file
main.class=nl.wldelft.fews.system.workflowtestrun.WorkflowTestRun
classpath.1=*.jar
#Java Runtime jvm.dll location
## for 32 bits use ../jre/bin/client/jvm.dll
vm.location=../jre/bin/client/jvm.dll
## 64 bits use ../jre/bin/server/jvm.dll
##vm.location=../jre/bin/server/jvm.dll
vmarg.1=-Xms512m
vmarg.2=-Xmx1024m
#location of the bin dir has changed in 2017.01 (was .)
working.directory=../bin
#region_home directory - <region_home> to be replaced with actual region home directory
arg.1=../<region_home>
arg.2=..\path_to_your_config_test_file.xml |
Check the attachment workflow_test_run for an example.
Since 2018.02
Since 2018.02, the The required flags should be set when calling FEWS from the command line. This can be done conveniently with the simple DOS batch file below. Note that one should at minimum specify the root folder where the FEWS bin is stored, the regionHome directory, the patch, and the WorkflowTestRun file that is to be executed.
...