The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Revised: May 4, 2015
OL-15762-05
|
|
We prepared this material with specific expectations of you. You will audit and run reports that demonstrate your playback of media assets on your Cisco Digital Signs. |
You can audit which assets your DMPs play, and where, and when, and for how long — across any supported range of dates that you specify.
Proof of play reports are available per DMP, per DMP group, and per campaign. We use a dedicated proof of play service to collect these records and generate these reports.
Will you use AAI to change the hostname of a DMM appliance on which proof-of-play features are enabled (CSCtr00731) ? There is no common reason to do this. We recommend that you do not. Nonetheless, we will not stop you.
BEFORE YOU CHANGE THE HOSTNAME
We assume that your information is confidential and we strive to protect it from unauthorized access. Therefore, DMM self-registration of a feature license considers the combination of the appliance hostname and its hardware serial number.
After its appliance hostname is changed, DMM will reject its prior self-registration of your license to use proof-of-play features. Although the license is still valid and is still correctly associated with your hardware serial number, your DMM appliance cannot load proof-of-play logs from any server whose hostname differs from its own. It cannot read from them or write to them. Likewise, you cannot use proof-of-play features on any host but the one that self-registered the license.
Although you can return a hostname to its original value, doing so still might not be sufficient to satisfy an ongoing requirement for full and uninterrupted access to proof-of-play features and logfiles. Consider this scenario.
1. The hostname is changed from A to B. Therefore, B cannot use the feature license that A self-registered and cannot use the logfiles that DMM generated on behalf of A.
2. The hostname is then returned to A. Therfore, A can access its own data from any time when the hostname was A, including the original instance. However, it cannot use the feature license that B self-registered and cannot use the logfiles that DMM generated on behalf of B.
We recommend that you prevent these complications and disruptions by leaving the hostname in its original state.
Will you change the user authentication method from LDAP mode to Federation mode (SSO) for a Cisco DMS deployment that includes proof of play (CSCtq55094) ? Fundamental changes to user authentication are not routine but can be useful occasionally.
However, account records in the new SSO user base might not correspond exactly to account records in the old LDAP user base. It is possible, in fact, that some long-established login credentials might cease to be valid for Cisco DMS users. And so, if the proof-of-play user role assignment in your network is associated with one of these nullified user accounts, the affected user cannot view proof-of-play campaigns or run reports for campaigns.
In this case, you must assign the proof-of-play role to a user account that exists in the SSO user base.
In this release, proof-of-play reports for a given playlist during a given time range might not be correct (CSCtr97593). In some cases, these reports can:
Timesaver Go to terms that start with... [ C | R ].
|
|
|
|
Cisco Digital Signs includes methods to identify and assemble an affinity group from any combination of presentations, playlists, and assets. We call this affinity group package a campaign.
Mingled elements within a campaign all share one clear and unifying purpose. For example, the elements of your first campaign might all advertise a community celebration, even though they use various languages or differ in other, key ways. However, you recognize for your own purposes that at least one significant factor (the community celebration, in this example) unites them as an affinity group.
The benefit of campaigns is that you can audit and verify the scope of playback — individually and collectively — for all elements that support one goal, initiative, policy, or event. On a DMP-by-DMP basis, you can discover and demonstrate exactly which assets:
Note ● Proof of play features in Cisco Digital Signs ignore the playback of assets that Cisco developed — including all samples and templates that you received with any previous DMM release.
1. Add assets to your media library.
2. Develop, schedule, and publish presentations and playlists.
Step 1 Do one of the following.
Step 2 Stop. You have completed this procedure.
Step 2 Click Reports on the Home page.
Step 4 Enter the fully qualified, DNS-resolvable DMM appliance domain name in the DMM FQDN field.
Step 6 Use fields in the Authentication area to enter the superuser name and password for your DMM appliance.
Step 7 Define settings in the Data Size/Rotation Rules area.
Step 8 Choose an option in the Archiving Rules area to set how many days of playback data to accumulate before archiving it.
Step 10 Stop. You have completed this procedure.
Step 1 Click Reports on the Home page.
Step 2 Click Campaign. Then, click Manage Requestors.
The Manage Requestors dialog box opens.
Step 3 Click Add New Requestors.
The Add New Requestor dialog box opens.
Step 5 (Optional) Enter a description.
Step 7 Stop. You have completed this procedure.
Step 1 Click Reports on the Home page.
Step 2 Click Campaign. Then, click Create Campaign.
The Create New Campaign dialog box opens.
Step 3 Enter a name for this campaign.
Step 4 Associate a requestor with this campaign.
Step 5 Choose when this campaign should become active, and then choose when it should stop.
The Select Resources dialog box opens.
Step 7 Use check boxes in the table to mark assets that you might use.
Step 8 Click OK to populate your campaign with the assets that you marked.
Step 9 Stop. You have completed this procedure.
Step 1 Click Reports on the Home page.
Step 3 Choose reporting criteria.
– A summary report counts successes and failures.
– A detailed report counts either successes or failures.
Step 5 Stop. You have completed this procedure.
Step 1 Choose a format from the Export list.
Step 2 Stop. You have completed this procedure.
Step 1 Click View previous reports.
Step 2 Stop. You have completed this procedure.
Step 1 Click Reports on the Home page.
Step 3 Stop. You have completed this procedure.
Q. What might prevent proof-of-play features from working at all?
The fully qualified domain name (FQDN) for your DMM appliance must not exceed 30 characters.
123456789012345678901234567890
NOT VALID for Proof of Play
Q. How do campaigns differ from presentations and playlists?
They are fundamentally different.
Q. Are campaigns required in proof of play?
No. Campaigns are just one of three supported report types. You can also obtain proof of play reports per DMP or per DMP group.
Q. Can I associate one asset with multiple campaigns?
Q. What triggers universal proof of play auditing for an asset?
There are two scenarios in which we validate each instance of playback for an asset.
Q. What triggers conditional proof of play auditing for an asset?
We might validate some instances of playback but not others. We cannot audit playback consistently for an asset whose instances of playback occur sometimes outside any campaign.
Q. What prevents proof of play auditing for an asset?
We cannot validate instances of playback for an asset whose every instance of playback occurs outside any campaign.
The log file location for proof of play features is: /var/apache-tomcat/proofofplay-core.log