TelVue HyperCaster® User Manual

Page 103

TelVue HyperCaster

User Manual / v5.0 / October 2014

is a registered trademark of TelVue Corporation 800-885-8886 / www.telvue.com

102

Any stream or feed configured on a HyperCaster can have a “Spot ID” specified. During import of an
SCH file, if any row contains a spot ID that matches an available feed’s spot ID, a stream event will be
created instead of a regular playout event.

E-Mail Notifications of Missing Content

In the event content is scheduled but is missing from the server or has not yet been saved to the
server, it is possible to set up an email notification. Email notification or missing file alerts can be sent
to email enabled users based upon on a specified time threshold.

To do so, select the following:

•

Configuration>Email Configuration

•

Check “Deliver Email Notifications”

Set up your SMTP address, port, domain along with username and password. If you do not know how,
consult your IT person regarding the proper values of these email settings.

Additionally, email notifications must be enabled on a user by user basis. That can be set in the Users
section of the Config tab.

When a missing file is scheduled to play within the threshold, the Missing Files system health item will
become “critical” and an email will be sent to all users who have selected to receive notifications.

The missing files information is available as a report under the Reports tab, as well as being part of
the HyperCaster API. (

Missing Files API

)

Directory Folder Structures

Schedule Remote Server File Structure

Any HyperCaster will create the following directory structure on a schedule (type CCMS) remote
server. In this example, “vol1” is either the SMB share name or FTP directory on the remote server.

//vol1/import/GDP/csv

Raw copies of the imported .SCH files. Once each schedule file has finished importing, the most recent
copy of the SCH is saved here for future reference.

//vol1/import/GDP/summary

A summary report is created for each individual schedule file import, and will be located in this
subdirectory. The date/time of the import is incorporated into the filename. For example, the schedule
file A0901001.SCH imported on 6/7/2012 at 14:27:19 will be called
A0901001_import_log_cmp_06072012_142719.csv. There will be a line for each individual playout
event in this report, showing a successful import or displaying any individual error messages.

//vol1/import/GDP/failed

A failed report is created if any schedule entries are not imported successfully. The failed report
consists of the raw schedule file rows that could not be imported and is named in using the same
timestamp scheme as the summary files.

//vol1/import/GDP/verification

The verification files for EACH HyperCaster client are located here in their client specific subdirectories,
regardless of warm spare designation. Client specific sub directories are named after each
HyperCaster’s serial number available on the dashboard screen.