Setting up VOD workflows

Depending on the type of deployment, either NAGRA sets up content workflows, or you need to set them up yourself.

This section explains how to do it yourself. If NAGRA is setting the workflows up for you, you can ignore this section.

Overview

This section explains how to set up VOD content workflows.

OpenTV Platform supports:

Retrying VOD workflow jobs that have failed (for example, if there was a problem communicating with the encoder/packager).
This can be configured to happen automatically.
Rerunning VOD workflow jobs that did not fail (for example, if a new source asset is available or if the wrong encoder configuration was used).

To enable automatic retry for failed jobs, add the relevant parameters to:

The required profiles are different for two-stage and single-stage VOD workflows.

You can manually rerun the workflow for a content in OpCon – see Running and cancelling workflows.

OpenTV Video Platform supports three different VOD workflows, which allow it to work with various different encoders and packagers:

Two-stage with just-in-time packaging (JITP)
Content is encoded after ingest but is only packaged when requested. For example, Harmonic VOS360 works this way.
The advantage of this approach is that JITP reduces CDN traffic and the amount of storage required.
Two-stage without JITP
Content is encoded after ingest and then packaged as a separate operation. For example, Irdeto PES works this way.

PES integration is explained in its own section here.

The advantage of this method is that you can use an encoder from one vendor and a packager from another. You can also repackage existing assets if you need to without having to transcode them again.
Single-stage without JITP
After ingest, content is encoded and packaged as a single operation. For example, AWS Elemental works this way.
This approach has the advantage of reduced complexity.