Media Flow Controller Common Configuration Tasks (CLI)
Media Flow Controller Administrator’s Guide
206
Configuring Media Flow Controller for SmoothFlow (CLI)
Copyright © 2010, Juniper Networks, Inc.
Configuring SmoothFlow Namespaces (CLI)
Another required SmoothFlow configuration is a namespace to which you add a configured
SmoothFlow virtual player.
Important!
SmoothFlow functioning requires at least two namespaces, one (or more) for
SmoothFlow and one for the crossdomain policy with a lower (or lowest) precedence; see
Adobe Cross-domain Policy File Specification
for details.
1.
Configure a namespace with a name (enters you to namespace configuration mode).
namespace <name>
2.
Configure delivery protocol (HTTP and RTSP may be set) options (enters you to
namespace delivery protocol mode, use exit to leave), and domain settings if needed
(default is any) for the namespace. Only one domain per namespace is allowed; if
multiple domains require namespaces, create additional namespaces with the same
domain and set match <criteria> precedence appropriately (the lower the value, the
higher the precedence).
delivery protocol {http | rtsp}
domain <FQDN> [precedence <number>]
3.
While still in delivery protocol http mode (for both delivery protocol http and delivery
protocol rtsp) configure match criteria for the namespace. See
“uri-prefix” on page 13
for
definition and example.
Note!
only uri and virtual-host are delivery protocol rtsp match
options. You can optionally set a precedence for any match option.
match {header | query-string | uri | virtual-host}
4.
Optionally, while still in delivery protocol http mode (for delivery protocol http only),
configure client-response and client-request parameters.
client-request [cookie | query-string] action {cache [exclude-query-
string] | no-cache}
client-response [header <name> [<value>] action {add | delete}]
5.
Optionally, while still in delivery protocol http mode (for both delivery protocol http and
delivery protocol rtsp) configure origin-fetch parameters for managing the cache,
modifying the Date header, and fetching content in an offline manner; not needed for
crossdomain namespace. Defaults are shown as first option.
origin-fetch
cache-age {content-type<string><seconds> | content-type-any<seconds>}
cache-age-default {28800 | <seconds>}
cache-directive no-cache {follow | override}
cache-fill {aggressive | client-driven}
content-store media [cache-age-threshold<seconds>] [object-size<bytes>]
date-header modify {permit | deny}
Important!
If pre-staging to an edge, increase the cache-age-default to a higher value.
6.
Exit namespace delivery protocol mode and return to namespace mode.
exit
7.
Configure origin-server settings; for Release 2.0.4, multiple HTTP or NFS origin servers
can be configured with the server-map option.
origin-server http {absolute-url | follow {dest-ip | header <header> |
server-map <name> | <FQDN/path [<port#>]}
8.
Configure parameters for pre-staging content from origin; not needed for crossdomain
namespace. Authentication schemes must be pre-configured to be used. The ftp user is
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
