Grass Valley iTX Delivery Manager v.2.6 - Manual (Page 12)

6
About Delivery Manager
Modes of Operation and Endpoints
Modes of Operation and Endpoints
The table below shows which modes each endpoint supports:
Endpoint driver
Content Changed
mode
Search Media mode
Manual (export)
mode
CIFS   
FTP 
Diva   
MassTech  
PathFire 
Ardome 
FlashNet  
Core  
Delivery Manager and Workflows
Depending on the task its performing, Delivery Manager uses one of two workflow
systems.
• To trigger automated workflow operations (called ‘jobs’), Delivery Manager uses its
internal workflow engine.
• To transfer media (and any associated metadata) to the iTX content store and database,
Delivery Manager uses the ITX Workflow service.
Custom workflows (in the form of XML files) can also be created in iTX Workflow to further
enhance Delivery Manager’s functionality. These workflows may provide the ability to
process different types of content and trigger other jobs (such as QC or file verification) to
prepare media for playout.
Post Media Import Workflows
The Post Media Import process is a series of jobs triggered by a workflow following the
import of a new piece of media into Delivery Manager. This workflow runs internally for all
endpoints and therefore all media import jobs, which includes:
• Generation of proxy media copies for SmartClient and Desktop viewing.
• Generation of key frames for viewing in SmartClient.
• Deep analysis of the media file for extraction of metadata about the media.
Note: The Post Media Import workflow is added to all endpoints by
default and is part of the standard Delivery Manager installation, but
requires FPP Transcode Service to function.
To generate proxy media, the Proxy Generation Service is required.