Cisco Systems 5.2.x manual Best Practices to Stop Playback of a Scheduled Job, 18-4

Chapter 18 Schedule Media to Play and Commands to Run

Concepts

•Almost never schedule event instances that extend more than 60 days into the future. The exceptions to this rule are:

–An entry that recurs monthly can persist in your schedule for as long as 3 months.

–An entry that recurs annually can persist in your schedule for as long as 3 years. Furthermore, we recommend these additional best practices:

•Avoid deploying assets to any given DMP more than once per day. Ideally, all deployments should occur outside your normal business hours. You can schedule a deployment package that contains assets for more than one presentation if the target DMP has sufficient local storage to save the entire package. Applied outside normal business hours, this simple method reduces your dependence on daytime deployments, which might otherwise disrupt your digital signage temporarily.

•Avoid having any more than approximately 200 events (of all kinds, combined) saved in your schedule at any one time.

•Avoid having any more than approximately 100 presentations saved in DMD at any one time. If your presentations database grows too large, you might be prevented from designing, saving, and deleting presentations, and the start time might be disrupted for your scheduled events.

•Instead of creating a presentation that is similar to one that used to be in your schedule, simply modify the old presentation and reschedule it.

•Avoid extending the playback window for your customer-facing presentations and playlists beyond the actual hours when customers will see them.

•If you are not sure when or how many times a task or presentation occurs in your schedule, you can use the Schedule Reports feature.

Best Practices to Stop Playback of a Scheduled Job

Caution	Do not delete an event from your schedule to stop a presentation from playing on your DMPs.
		When you do this, your DMPs continue to use the presentation as if nothing has changed. This occurs because each deployment
		job includes an instruction to stop, which you delete along with the job that contains it.
		Instead, use Play Now to deliver the Stop All Applications command.

Restrictions

•External Server Restrictions, page 18-4

•Content Delivery Network Restrictions, page 18-5

External Server Restrictions

Caution	It is important to understand all possible limitations and effects of deploying to an FTP server, as well as the exact
	circumstances that lead to these effects. Files are sometimes unplayable or deleted automatically; subdirectories are
	sometimes created automatically; and values that you enter in DMM are sometimes changed automatically.

	User Guide for Cisco Digital Media Manager 5.2.x
18-4	OL-15762-03