CloverServer × Clover OS engine

transformation run/execution

✓

(via HTTP /S API call or from Admin WEB console)

~

(execution from command line via shell script)

run as server/daemon

✓

×

user security/multiple user support

• rights to read/write/execute applicable to user or group
• users can own individual projects/sandboxes

✓

×

maintaining history of transformation executions (full logs, tracking details, execution statuses)

✓

×

parallel execution of transformations

✓

~

(not directly supported)

re-use of worker threads/ DB connections/ JVM resources

✓

×

(each execution requires new start-up of JVM, creation of DB connection, creation of system threads)

pool of in-memory graphs for faster transformation start-up
(allowing transaction processing)

✓

×

scheduling graph run
(one time, regular)

✓

×

graph events listeners
(on start, failure, success, timeout)

with actions
(send-mail, sys-exec, graph-run, graph-kill)

✓

×

launch services allowing easy turn of transformation into service listening on dedicated URL for HTTP /S requests.

HTTP/S request may contain input parameters for transformation as well as HTTP/S response may contain output data.

✓

×

self-maintaining

(according to schedule deletes/archives obsolete logs and DB records)

✓

×

remote management
(administration accessible remotely via HTTP/S)

✓

×

JMX monitoring of running transformations

(inside Management Console)

✓
(continuous monitoring via server MBean)

~
(each transformation execution requires new connection of monitoring client)