Content Manager 11.00


This release has reached its end of support. We strongly advise that you update to a more current release.

For more information on updating or upgrading, please contact your sales representative.

Skip to end of metadata
Go to start of metadata

The user can generate Playback Audit reports using Content Manager. There are several types of Reports that the system supports:

  • Media Item reports (pdf/html)
  • Player reports (pdf/html)

The user may choose the level of detail and specify the selection criteria for these reports.  

Prior to using the reporting module, the Playback Audit Module needs to be installed and configured, if it was not done at the time of initial installation.



When installing the Playback Audit Module (PAM) for the first time on an existing system, care should be taken to prevent Content Manager from becoming overwhelmed with the quantity of historic "Billing" files that are waiting to be processed, as they are never deleted from your Content Manager. Moving the Billing files to an alternative location prior to installation is recommended, as it will free up HDD space over time, depending on the size of your network. 

The purpose of the PAM is to give you a way of gathering information on your assets, and the frequency with which they are utilized. This information will be stored in Log Files that will be stored in the following directory, unless you move it somewhere else on your machine because of a space concern: (the default directory is
C:\ProgramData\Scala\InfoChannel Content Manager 5\Data\<NETWORK_NAME>\receive\billing\<PLAYER_UID>). 

The frequency with which these logs will be gathered is explained in more detail in the Managing the Point to Point Server section, which covers the Playback Audit Settings in Network > Distribution > Properties. These can be set to hourly or nightly, but it is recommended that these logs be run on a nightly basis, as doing so hourly will fill your disk space more quickly. Routine checks also scan for and prevent duplicates.  Once the logs are gathered, they are processed, and the data is stored in the MongoDB database.

After the log information is collected it is parsed or converted into the reporting format you have set up. After that, it is sent to an archive. The default location for this directory is: C:\ProgramData\Scala\InfoChannel Content Manager 5\Data\ <NETWORK_NAME> \receive\billing_archive\<PLAYER_UID>.  If you data for this archive, it will be scanned and parsed. If it has never been processed before, it will then be stored in MongoDB. 

Additional Topics

For more information on topics relating to Playback Audit Reporting, please see:

  • No labels