Logs For Assets Created Using An Saas - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Table 25 segment_config.xml Parameters (Continued)
Parameters
<source-type >
<scratch_path>
< ?xml version="1.0"?>
<segment_config_info>
<!—IP address of the Media Flow Controller; required for generating the HTML
content-->
<mfd-ip> {IP_address_of_Media Flow Controller} </mfd-ip>
<!—Where the final chunks reside, can be local or nfs-->
<origin-path> {/var/www/html/smoothflow} </origin-path>
<!—Where the multi-bitrate files are present; can be local or FTP. If FTP,
then the script downloads the files to the given scratch-path. If local, then
the script copies the multi-bitrate files to the given scratch path-->
<source-type loc= ftp | local> <!–Choose either ftp or local-->
<ftp_location>
<username> {username} </username>
<password> {password} </password>
<server_ip> {ftp_server_IP} </server_ip>
<path> {/test_out} </path>
</ftp_location>
<!—If ftp service is running on the same system-- >
<local-path> {/root/test_out} </local-path>
</source-type>
<scratch_path> {temp_dir_removed_by_script_when_done} </scratch_path>
</segment_config_info>

Logs for Assets Created Using an SaaS

The system generates 3 log files when you use the encoding using an SaaS procedure:
•
pub-asset-encoder.log
•
pub-asset-polling.log
encoding.com, and associates them with unique keys generated by SFAssetGenerator.py.
•
pub-asset-segmenter.log
<ftp-location> – The location of the multi-bitrate files , if the location of these files is
different from the system where it is being run. This node requires the following
additional sub-nodes:
<username> – the authorized FTP user
<password> – the authorized FTP user password
<server_ip> – FTP server IP address, source and destination, respectively, (if different)
<path> – path in or out, respectively
<local-path> – The location of the multi-bitrate files if they are co-located in the same
system where this script is run (default is current directory where script is run)
A temporary directory on the system where the processing can take place; is
automatically removed when the processing finishes
—Captures the completion status of SFAssetGenerator.py.
—Captures the multiple transaction IDs provided by
—Captures the completion status of the SFSegment.py script.
SmoothFlow Deployment
Tags and Descriptions
Creating Assets Using an SaaS 261