This document describes the main steps in moving from an SMS system to a suite managed by an ecFlow server.
Multiple migration scenarios are available, from migrating everything in one big step to modifying definition files and header files to allow suites to run under both SMS or ecFlow. This is the strategy we adopted as it allowed us to test SMS and ecFlow suites in parallel.
The steps for migration are described in the following pages:
EOF abort action autocancel automigrate autorestore
clock complete cron date day defstatus
edit endfamily endsuite endtask event extern
family inlimit label late limit meter
owner repeat suite task text time
today trigger
For ecFlow this list is slightly smaller:
autocancel
clock complete cron date day defstatus
edit endfamily endsuite endtask event extern
family inlimit label late limit meter
repeat suite task time
today trigger
Embedded software may have migration concerns if they use SMS client command to communicate with tasks.:
When both SMS/ecFlow systems have to run in parellel, we have to decide what is part of the suite configuration (user side), and what is part of the system responsibility.
On the system side: