Stations with no publishing points

The following table describes the migration of stations in version 4.1 that are not associated with publishing points.

This version 4.1 configuration

Migrates to

Station with one or more existing programs

Example:
Station name: MyStation

Program names: MyProg1, MyProg2

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

Str11 source: msbd://encoder1:1000
Str21 source: http://encoder2:2000

Broadcast publishing point

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

Playlists: Prog1.wsx, Prog2.wsx

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

Str11 src: http://encoder1:1000
Str21 src: http://encoder2:2000

If a version 4.1 station exists and there is a program that points to that station, the following happens during the migration:

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 associated stream properties 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 is set to point to the playlist file that was created for the first program.
A broadcast publishing point is created. The existing station name becomes the name of the broadcast publishing point, which points to the playlist path.