...

Provisioning is the process in which a “player configuration” (or “player config” for short) “Player Config” is applied to the player and a “player app” “Player App” is installed on the player. The player config Player Config applies various settings to the player (such as settings needed for the player to connect to the network) while the player app Player App provides instructions for what the player should do upon bootup.

...

Player Config

A Player Config establishes various settings for the player and may include the following:

• Network settings (wired, wireless, etc.)

• Player name and description (players can be uniquely identified by their serial number, but adding more descriptive info can be useful)

• Time zone (especially relevant if players are geographically dispersed)

• Publishing mode (tells the player how to retrieve content)

• Diagnostic web server (enables access to a wealth of diagnostic info on the player)

• Logging (enables various logging options)

• Debugging (enables access via various logging tools)

• BrightSignOS version (enables the assignment of a specific OS version to the player)

...

When using BrightAuthor:connected, the Player App is known more generically as an autorun and more specifically as an autorun.brs file (.brs denotes a BrightScript file). When a BrightAuthor:connected Setup is applied to a player, an autorun.brs and associated files will be automatically generated created on the player.

Player App for Partners

Partners who choose to use their own CMS can write their own custom player app. Some partners may use our can write a custom Player App to connect players with their CMS. Many partners use our basic autorun.brs as a basis to build on while others may elect to write their own scripts from scratchfoundation when writing their own Player App.

Publishing Modes

...