WM Configuration
limitation of 20 simultaneous FTP clients at any site. See Using On Demand Playback on page 13 for more about progressive download.
Note For best results and to avoid impacting performance, do not exceed a maximum of 20 simultaneous progressive downloads regardless of data rate. Also, if higher data rate files are accessed via progressive download, the maximum total data rate of these files should not exceed 20 MBits/sec. This means, for example, that up to 20 users can access a 500 KBits/sec file; up to 5 users can access a 4 MBits/sec file.
TTo create a file for progressive download:
1.Open IWS and go to the Configuration: Encoder > Archiver page.
2.In the Archive File Name field, enter a valid file name preceded by public as shown in the following example. (The public folder is automatically created and all .wmv files in this folder are recognized as on demand files that can be viewed via progressive download.)
public/filename.wmv
3.Click Start Archiver to create the file.
4.Click Stop Archiver when done.
TTo view a file via progressive download:
1.Open a browser and view an archived .wmv file via anonymous FTP by
ftp://<VBrickIPAddress>/filename.wmv
2.Alternately, you can open a browser, type the FTP URL in the follow format, and select any .wmv file in the folder.:
ftp://<VBrickIPAddress>
Configuration: Encoder > Push
The WM Appliance supports up to 25 push destinations per slot (for a total of up to 50 push destinations in a dual encoder or encoder/reflector model) with independent configuration parameters and enable/disable control for each push destination. All push destinations receive the same stream. Resources are shared between pull clients and push destinations so the configured maximum number of pull clients and the configured maximum number of push destinations cannot exceed 202. The actual number of pushes that can run at the same time depends on the configured bit rates. The Maximum Push Destinations field determines how many lines
Note When an v1.x WM appliance is updated to a current WM release that supports multiple push destinations, the first row on this page is populated with the previously configured push destination.
HTTP Push - Slot1
HTTP Push lets a VBrick encoder connect to a VBrick Reflector, a Windows Media Server, or Real Helix Universal Server that will receive an encoded stream from the VBrick. Depending on the security settings on the server, a Publishing Point on the server (with specific security settings) may need to be configured before the VBrick can successfully push the stream. The VBrick continues to push to the server even after encountering an error
VBrick WM Appliance Admin Guide | 55 |
