Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Workflows are a collection of various types of agents to process data. The agents in a workflow are either collection agents, processing agents or forwarding agents. The list of agents that you can see, depends on your license for Usage Engine.


  • Batch
  • Realtime
  • Task
  • System Task

Batch Workflow

A batch workflow processes input that originates in a specific source, often a file. The workflow creates batches from the data and processes them one by one.  


  • Processes batches, one at a time
  • Is started either manually or by a scheduled trigger  
  • Stops either when it finishes processing the input, or when aborted


    If the workflow aborts, the current batch can be reprocessed.

Real-Time Workflow

  Real-time workflows are applicable in systems where instant processing requests need to be addressed as they occur.



Real-time workflows may use the Inter Workflow or Kafka agents to forward data to a batch workflow.

Task Workflows

Task workflows are single agent workflows that execute user defined SQL, shell scripts or unit tests.

System Task Workflows

A number of System Task workflows are included in Usage Engine. System Task workflows and workflow groups that include System Task workflows enable you to perform background routines such as log- and run-time data clean up from the platform.


The Archive Cleaner System Task enables you to remove old archived files from the file system. Archive Cleaner operates according to data that it receives from the Archive profiles.



Enables you to create a backup of all the configurations. A backup file is saved on the host machine where the platform application is installed. 
The System Backup files are stored under $MZ_HOME/backup/yyyy_MM, where yyyy_MM is translated to the current year and month and $MZ_HOME/backup is the default path. The system saves a backup file and names it according to the following format: backup_<date>.zip. System Backup also enables you to specify the maximum age of backup files before they are removed from the host disk. You can change this location using the following command:

Code Block
<property name="mz.backup.path" value="${mz.home}/backup"/>

Refer to Persistent Storage [hide](3.0[/hide]) to know about how you can configure persistent storage.