Publishing points that point to local stations

The following table describes what happens when publishing points and their associated local stations are migrated to this version of Windows Media Services from version 4.1.

This version 4.1 configuration

Migrates to

Unicast publishing point
pointing to a local station
associated with programs and streams
using MSBD or HTTP

Example:
Station name: MyStation

Program names: MyProg1, MyProg2

MyProg1 streams: Str11, Str12
MyProg2 streams: Str21, Str22

Str11 source: msbd://encoder:1000
Str21 source: http://server/stationx

Publishing point name: PubPoint
Path: msbd://localhost/mystation

Broadcast publishing point

Example:
Publishing point name: MyStation
Path: \WMPlaylists\MyProg1.wsx

Playlists: MyProg1.wsx, MyProg2.wsx

MyProg1.wsx media: Str11, Str12
MyProg2.wsx media: Str21, Str22

Str11 src: http://encoder:1000
Str21 src: http://server/stationx

Publishing point name: PubPoint
Path: http://localhost/mystation

If the publishing point path uses the HTTP or MSBD protocol to point to an existing local station service and programs, the upgrade process results in the following:

A new playlist file is created, using the name of the program, and the playlist file is saved to a new directory (%systemroot%\WMPlaylists\Program_Name.wsx).
Each stream within the program becomes a media element within the playlist, and all properties associated with the stream become attributes of the media element.
References to MSBD in the source URL are replaced by HTTP.
If two programs exist for a single station:
- A new playlist file is created for each program, using the name of the program, and the playlist file is saved to a new directory (%systemroot%\WMPlaylists\Program_Name.wsx).
- A broadcast publishing point is created for the station and the path points to the playlist file that was created for the first program.
Two broadcast publishing points are created:
- The version 4.1 station name becomes the name of the first broadcast publishing point, which points to the playlist path. The station properties are migrated to the publishing point.
- The version 4.1 publishing point name becomes the name of the second broadcast publishing point, which points to the first publishing point.

Note Image Notes

The upgrade process only covers the migration of Windows Media Services. Any remote servers and encoders must be reconfigured manually to use the HTTP protocol.
If you were using a port other than 80 to stream content from another server or an encoder, you will need to update the URLs in the playlist to reference the appropriate port number. For example if you streamed welcome.asf over port 8008 on your 4.1 server and your original URL was msbd://server1/welcome.asf the upgrade process will result in the URL http://server1/welcome.asf. However, that will not work if the content is not available on the default HTTP port, so you must modify the reference to http://server1:8008/welcome.asf.

Publishing points that point to local stations

Related topics