Deploying The Smoothflow Reference Client Player; Table 26 Required Configurable Nodes And Parameters - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide

Deploying the SmoothFlow Reference Client Player

A binary SmoothFlow client player is provided to you as a reference and for testing or
evaluation purposes. This section details how to install the Juniper Networks Smoothflow
Player for testing purposes onto your Web page.
Note! Adobe Flash Player versions 9 and above are supported.
The SmoothFlow_ReferencePlayer.zip file contains everything you need to get started.
Contact Juniper Networks Customer Support (see
page 34) to obtain the zip, and unpack it to your Web server.
You work with the following files retrieved from the zip:
•
fPlayerIn.swf—This is the Adobe SWF (shockwave flash) file with SmoothFlow playback
functionality that must be embedded in your browser page.
•
AC_RunActiveContent.js—This file is used to dynamically generate JavaScript-based
active content embedding tags for the browser to display your Flash movie. This file
contains functions that embed your active content based on the parameters it receives
from the main.html page.
•
fPlayerInternal.html—This is the file that you request via your portal server to view the
sample SmoothFlow content. Be sure to set base_uri and video_name tags correctly.
•
crossdomain.xml—Flash uses this file to control the cross-domain resource-access
policy, for both HTTP and socket connections. Use it to control which resources a Flash
application can access, when that application did not originate in the domain of the site.
The crossdomain.xml file must be hosted and delivered via Media Flow Controller.
Follow these steps to deploy the SmoothFlow Client player.
1. Copy fPlayerIn.swf, AC_RunActiveContent.js, fPlayerInternal.html, and
crossdomain.xml from the zip to the same directory in the doc root of your Web server.
2. Modify the HTML below (source for fPlayerInternal.html). Reset the underlined
references as needed.
and is followed by an example file
3. Use the URI for the player as follows. For example, if the HTML page in which you have
embedded the player is fPlayerInternal.html, then any anchor links to that page should
be of the form:
www.somedomain.com/fPlayerInternal.html
Table 26 Required Configurable Nodes and Parameters
Parameter
'base_uri'
'video_name'
'ext'
Table 26 gives a brief explanation for the configurable parameters
(Example
The domain hostname/IP address where the video sequences reside (must be
configured).
The rest of the URI, which gives the logical path and video name, without any
extensions. For example, if the video's full URI is
http://www.somedomain.com/sf-test/foo.flv
the video_name will be /sf-test/foo
The player automatically builds the rest of the URI which will conform to the
SmoothFlow Query Parameter API specifications.
The file's extension; usually .flv.
Deploying the SmoothFlow Reference Client Player
"Requesting Technical Support" on
fPlayerInternal.html).
Description
SmoothFlow Deployment
267