METEOR2 workflow management systems consist of both (1) design/build-t
ime and (2) run-time/enactment components for implementing workflow ap
plications. An enactment system provides the command, communication an
d control for the individual tasks in the workflow. Tasks are the run-
time instances of intra- or inter-enterprise applications. We are deve
loping three implementations of the METEOR2 model: WebWork, OrbWork an
d NeoWork. This paper discusses WebWork, an implementation relying sol
ely on Web technology as the infrastructure for the enactment system.
WebWork supports a distributed implementation with participation of mu
ltiple Web servers. It also supports automatic code generation of work
flow applications from design specifications produced by a comprehensi
ve graphical designer. WebWork has been developed as a complement of i
ts more heavyweight counterparts (OrbWork and NeoWork), with the goal
of providing ease of workflow application development, installation, u
se and maintenance. At the time of this writing, WebWork has been inst
alled by several of the LSDIS Lab's industrial partners for testing, e
valuation and building workflow applications.