CCMS Plus Setup

1. Channel Setup

Each HyperCaster must be configured with two parameters, Network and Headend ID. From the browser interface:

  • Click Channels in the Config tab.
  • Click a Channel’s title or its Edit button.
  • Fill in appropriate values for Network and Headend ID. Save those changes.

Each channel being scheduled with CCMS Plus must have a unique Network / Headend ID pair. Each schedule file has a Network and Headend ID in its filename.  (Network ID is character positions 4 & 5. Headend ID is positions 6, 7, and 8.) The HyperCaster retrieves .SCH files with a filename containing the Headend and Network ID of any of its channels for scheduling. For example, if you configure a channel to have a Network ID of 01 and a Headend ID of 001, the server will retrieve from the schedule remote server, all .SCH files with a filename of ***01001.SCH.

2. Remote Server Setup

A CCMS Plus setup includes one or more HyperCasters connected to a single remote server for schedule files, and any number of content remote servers for media. The schedule and content remote servers can be any available FTP or SMB share on the network. The HyperCaster will automatically retrieve scheduled media files not already present from any of the remote content servers, and schedules from the single schedule remote server.

To set up a remote server:

  • Click “Remote Servers” on the Config tab and select the “New Remote Server” button.
  • Select a type of “CCMS” for schedule remote servers, or “Content” for remote servers
  • Select the protocol type (either FTP or SMB).
  • Fill out the remaining protocol dependent fields (name, user, etc.) and select “Save”

3. Warm Spare Designation

Any HyperCaster that is using CCMS Plus can be designated as a “warm spare” in the “Server” section of the config tab. Warm spare servers are meant to serve as a backup to a primary server, and should be configured with the same Network and Headend ID’s. Warm spare servers do not write their verification logs to the top level remote verification location so it does not conflict with a primary server. See the explanation of the verification directory below for more details on the differences between primary and warm spare servers.