Table of Contents
Advertisement
•
Create – at the server level will allow a user to create publishing points, or at the
individual publishing point level it will allow a user to create
Adding users and privileges at the server level will allow all inherited publishing points to
acquire the same security privileges. To add individual privileges for a specific publishing
point, select the
WMS Publishing Points ACL Authorization
user must already exist as a domain user or as a local user on the server. The user name will
be listed and can be given the desired privileges.
To Create Authenticated Push Publishing Points:
On the
WMS Publishing Points ACL Authorization
for the
Permission
user or set of users by adding the user. Click
named users will be allowed to push to the server after being authenticated. If this change is
done at the server level, the changes must be propagated to the publishing point level to be
effective.
To Create Non-Authenticated Push Publishing Points:
Either disable
WMS Publishing Points Authorization
authorization always on, and selectively allowing authentication to be bypassed for some, on
the
WMS Publishing Points ACL Authorization
Write Permission
Click
to apply the change to the server. If this change is done at the server level, and the
Ok
change is propagated to all publishing points, all publishing points will allow push without
authentication.
To Create Pull Publishing Points:
Create a broadcast publishing point on the server and use the WM Appliance's
the source for the publishing point. When you start the publishing point it pulls the stream
from the appliance and you can see the server listed in the client table on the VBrick's Status:
Server Status > Encoder Details page in IWS. You can optionally enable the
point when first client connects
the server wait for a client to connect before it starts the pull from the appliance.
The Windows Media Server must have the HTTP control protocol enabled to accept a push.
Go to
Server Properties
enable
WMS HTTP Server Control Protocol
server. The HTTP control protocol uses port 80 by default so make sure you do not have
other services running that also use that port. Also, the
be enabled at the server or Publishing Point level.
Creating Publishing Points on Helix Universal Servers
The RealNetworks Helix Universal Server allows both Push and Pull from a Microsoft
Windows Media encoder and auto-detects for the source method. Currently, only non-
authenticated push publishing points are currently supported by the VBrick WM Appliance
for the Real Helix Universal Server.
Creating Non-Authenticated Push Publishing Points
Using the Helix Administrator interface in the Helix Server, login and on the left pane click
on
Broadcasting
pane lists all the publishing points that are configured. Note that Helix does not separate Push
VBrick WM Appliance Admin Guide
, click
Publishing Point
Properties
user if already checked, and add write permission for a selected
Everyone
for the
user (if already on the list or add to the list if necessary).
Everyone
feature in the publishing point's general properties to have
and select
Control Protocol
and then click
Windows Media Encoding
Copy From Points
, select
Authorization
. To add users and subsequently, permissions, the
screen from above, uncheck
to apply the change to the server. Only the
Ok
, or keeping the default policy of
at the publishing point level, select
in the left pane and in the right pane
to enable HTTP Control Protocol on your
WMS Negotiate Authentication
. The Windows Media Sources
WM Configuration
.
, and right-click
Allow Write
Allow
as
HTTP URL
Start publishing
must
49
Advertisement
Table of Contents
