Running a transformation is isolation is only useful for one-off or simple scenarios. To be truly useful, it needs to fit into any operational environment.
CloverDX ensures that your transformations live happily alongside other applications, systems and processes and be controlled by them when necessary.
The CloverDX Server lives in your main operational environment and is responsible for a range of automation and orchestration tasks to ensure it can launch and be launched by external processes and applications.
The most commonly used automation features are
CloverDX has its own internal scheduler. However, you can also use your preferred scheduler to launch data jobs.
You can monitor data jobs and trigger alerts when necessary. Monitoring applies at the server and job levels.
As well as alerting, the monitoring can also launch other data jobs based on the job’s execution status.
CloverDX offers many ways to launch data jobs based on a range of event triggers.
CloverDX Server provides an easy way to configure REST API endpoints that can be invoked from any external process.
You can monitor files and folders to detect new files or file modifications. For example, you might want to launch a job when a file is FTP’ed.
You can launch a data job based upon the completion status of an executing job. Different jobs can be launched based on completion, success, failure, timing out etc.
CloverDX can monitor message queues and launch jobs when specific messages are found.
You can also write Groovy scripts to perform any other generic task that the other event listeners cannot.