Schedule Remote Server File Structure
Any HyperCaster will create the following directory structure on a remote NAS or server from which it is configured to fetch CCMS schedules. In this example, “<share>” is either the SMB share name or FTP directory on the remote server. The serial number sub-folders are named based on the HyperCaster’s serial number, which will match the MAC address for the eth0 NIC, for example: AC1F6B43DB78.
//<share>/csv/<serial_number>
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.
//<share>/summary/<serial_number>
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
//<share>/failed/<serial_number>
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.
//<share>/verification/<serial_number>
The verification files for EACH HyperCaster client are located here in their serial number specific subdirectories, regardless of warm spare designation. Client specific sub directories are named after each HyperCaster’s serial number available on the dashboard screen.
These are not the “primary” verification files meant for final processing, but are meant to serve as an additional copy of what each individual HyperCaster did in case any data is ever lost or needs to be double checked.
One directory level above the client specific directories are the verification files created by each non-warm-spare HyperCaster. Any server that is meant to serve as a backup to a primary server should be designated a “warm spare” on the Config > System tab. Warm spare servers will continue to write their verification data to its own serial number specific directory, but will not write to the primary verification file. In the event of a primary server failure, the secondary server’s warm spare designation should be removed manually before use as a primary server.
HyperCaster File Structure
Each HyperCaster contains the same directory structure and files that are written to the schedule remote server under the //vol1/import/GDP directory, minus the MAC address sub-directories. These are meant to serve as a backup in case network connectivity or some other problem prevents transfer of information to the remote server.
Additionally, the root directory acts an import hot folder to automatically ingest SCH files.
//vol1/import/GDP
Any schedule files dropped into this directory will be imported roughly every 5 minutes. In an emergency, or in the event of a temporary communication failure with the CMP parent, any .SCH files can be manually copied here to import to individual HyperCasters.
