In this article
VIDIZMO, being a robust Enterprise Video Content Management system allows customer organizations to keep a detailed track of all application-wide processes and sub-processes within the activity to help users view its progress, current status and completion reports. This helps managing tedious processes such as transcoding media, pre-scheduling resource-intensive tasks by estimating their completion time and streamlining the application's usage throughout.
Workflow can be described as the movement of tasks and activities through a functional process. It is a logical sequence of activities or a set of complex processes that are taking place concurrently to achieve a certain objective such as transcoding media. These activities and workflows have an impact on one another in terms of functional dependency, processing speed and operational concurrency. For example, only after the Clip Media activity has successfully completed, the Transcoding activity can start. In case the files are huge and takes up a lot of processing resources, other workflows will be queued owing to this one.
To learn more about workflows, see: Understanding Workflows.
VIDIZMO allows you to configure Workflows settings using Application Configuration keys via Control Panel in your Portal. Here is how you can do this:
Before you start
To understand steps in order to configure application configuration keys, see: How to Update Application Configuration Keys in VIDIZMO.
Configuring Workflows Settings in VIDIZMO
You can configure the following in Workflows section of Application Configuration:
Content Processing Path
Here, you may update the path of the Cache folder for Workflow service to run various workflows. The service creates 'Workspace' for workflow and its activity on the specified path. Workflows and their activities can use that workspace to download and process files or other meta information (transcoding etc). Workflow service deletes the Activity Workspace and Workflow Workspace as soon as they are completed.
Maximum Concurrent Workflows
You can also define the maximum number of workflows that a single instance of Workflow Service can execute at a given time. In addition to this, Workflow service can have limits defined for each type of workflow as well. The default maximum number has been set to 16.
Workflow Retry Count
Additionally, you may configure the maximum number of attempts the workflow service is going to make to run a workflow after which it will give up the process and move onto another workflow in queue (if any). When errors occur, the error information is captured and stored along with the workflow, which can be viewed and analysed for further troubleshooting. The default workflow retry count has been set to 3 as an optimal number to balance consumption of resources and probability of random errors.