Never having PAM before, or a new system. Content Manager version 11.01.04

Summary Report

• It displays the number for players found based on your criteria and selected date range. Each player is displayed on its own page with the number of media items, the number of time those media items played, and the total duration they played during the selected date range.
• more details Check which version of MongoDB is required.

Note:

• 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.
• If you require to access the Mongo database with username and password (Step 10), Content Manager need be later than equal to 11.02
• Content Manager version 11.01.04 requires MongoDB version 2.6.6 or better
• If you use antivirus software, exclude below from real time scanning
  • CM folder C:\ProgramData\Scala\InfoChannel Content Manager 5\Data\YourNetwork\receive
  • Pre-imaged Player D:\FTProot\InfoChannel_Player_5_Config_and_DATA\Application Data\Logs
• Except CM version 11.01, skip steps 17, 18, 19 and 20

Installation Steps

1. Download playbackauditassistant.exe (your Content Manager version) from download center.

1. Setup Wizard

1. Tick Install the MongoDB>Next

1. Accept the agreement>Next

1. Choose where the MongoDB application will be installed. You can either use the default location (as seen below), or change to a different location. Once you have made your selection, click Next to continue.

1. Click Visit MongoDB Download site

1. Click MongoDB x.x.x and start downloading mongodb-Win32…..
   • CM1101 requires the use of MongoDB database MongoDB version 2.6.6 or better

1. Click Browse and select mongoDB-win...>Open>Next

1. Database File Storage Location
   • Choose where the MongoDB database files will be stored. You can either use the default location (as seen below), or change to a different location. A warning will appear telling you that each player will consume about 10MB of disk space, and the location you selected has only about x GB free on your machine for the logs, so please change the destination folder if necessary. Once you have made your selection, click Next to continue.

1. Click Next

1. Click Yes.

1. MongoDB database Name (default name pam)>Next

1. Click Finish

1. Open ContentManager System>Network Settings>Miscellaneous>Enable Playback Audit reporting. Save and Close.

1. Logout. Log back in. or Refresh the browser screen containing your Content Manager, and another menu called Reporting should appear at the top of the page, as seen below.

1. Reporting>Database Configuration. Put Step 11 MongoDB Database name in Schema. (Default pam)

1. Click Test Connection and confirm the connection

1. (Only 11.01)Access your Content Manager server. Go to Default: C:\Program Files\Scala\MongoDB open mongod.cfg with notepad
   • (Except version 11.01, skip the steps 17, 18, 19 and 20)

1. (Only 11.01) Change to javascriptEnabled:true and save it.

1. (Only 11.01) Restart MongoDB service and Apache Tomcat service.

1. (Only 11.01) Confirm MongoDB Log Default: C:\ProgramData\Scala\MongoDB\Logs
   • It should be javascriptEnabled: true.
2. Check "billing" . As soon as "billing" has been newly updated. Within one minute, the new files will be appeared in billing_archive. (Normally next day)
   • Default: C:\ProgramData\Scala\InfoChannel Content Manager 5\Data\YourNetwork\receive\billing

1. Go back to Content Manager. And click Reports

1. Click +New and create a report

1. Report from Players. Network>Players>Tick players you wish to get reports.>Report.

1. Detail Report
   • It displays the number for players found based on your criteria and selected date range. Each player is displayed on its own page with a header containing the same information as the player summary report. Each page also lists the name of each media item, the number of times it played, and the total duration it played during the selected date range

Adjusting Your Settings

In the Reporting menu, clicking on Settings allows you to make changes to the general Report settings for the following parameters:

• Properties:
  • Network content and data language: Defaults to Follow User's Report Language, but can be set to any of those supported by Content Manager.
  • Default report language for users: Defaults to User's Language, but can be set to any of those supported by Content Manager.
  • Header: None is necessary, but one can be added to the report.
  • Footer: None is necessary, but one can be added to the report.

• The Logo Media tab allows you to add or remove a logo for your reports, and set an alignment (either left, right or center) for where that logo should be on the report itself.

• Once you have your changes to this screen, click either Save Changes, or Save and Close to commit those changes.

Troubleshooting.

1. Making sure that the database connection is established. (Step 16)
   1. Provide a screenshot.
2. The new files will be appeared in billing_archive (Step 21 Generally next day)
   1. Network>Distribution>Properties. Enable Playback audit log uploads:

1. Does the player turn off at night?
   1. Delay logs SSHEALTH_LogUploadDelayHours=h in MMOS or
   2. Set hourly (Not recommended) Playback Audit Settings in Network > Distribution > Properties
1. Uninstall MongoDB completely and install it again.
   1. Uninstalling PAM 11.02 (MongoDB 3.0.12)