Initiate Encoding Using An Saas; Table 22 Setup.xml File Parameters - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

SmoothFlow Deployment

Initiate Encoding Using an SaaS

The SFAssetGenerator script works with two XML files, setup.xml and asset.xml and outputs
one, jobid.xml. You use this script to provide the chosen encoding service with information for
the encoding to generate the multi-bitrate assets. This section describes the three XML files
and provides usage options. Initiating the encoding requires these steps:
1. Create a setup.xml file describing the Website of the encoding service and your login
credentials plus where you want the multi-bitrate profiles output to and credentials for that
(for example, FTP site and credentials), and how often you want status polling done.
2. Create the asset.xml file describing each single-bitrate video and how many multi-bitrate
profiles you want created and at what rates; including frames-per-second, container
format, and keyframe interval.
3. Run the SFAssetGenerator.py python script to initiate the encoding of the referenced
single-bitrate videos into multi-bitrate (MBR) profiles. This script outputs the jobid.xml file
with descriptions of the multi-bitrate profiles created by the SaaS.
Usage Options for SFAssetGenerator.py Script
Use the SFAssetGenerator.py python script by running the python command at the
command line and using the following tags. Example follows.
•
-s—setup.xml
•
-a—asset.xml
•
-o—jobid.xml
Example:
python SFAssetGenerator.py -s <setup_xml_file> -a <asset_xml_file> -o
<jobid_xml_file>
setup.xml
This file specifies the global setup configuration parameters; variables are shown in curly
brackets ({ }). Can be called setup.xml and its location specified via the –s command line
parameter. If it is not specified, the script looks in the current folder for a setup.xml file. If the
file is absent, the script throws an error and stops.
The configurable parameters for setup.xml are described in
file.
Table 22 setup.xml File Parameters
Parameters
<service_provider>
256 Creating Assets Using an SaaS
<name> – name of encoding service; for example, www.encoding.com. The
"pre_process=1" corresponds to the encoding service; currently only
encoding.com is supported.
<login> – your encoding.com credentials
Media Flow Controller Administrator's Guide
Table 22, followed by an example
Tags and Descriptions
Copyright © 2010, Juniper Networks, Inc.