Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

BrightSign players in large, distributed networks should meet certain provisioning and recovery requirements. Partners who want to set up their own provisioning and recovery systems, rather than using bsn.cloud, should make sure that it meets the following requirements.

Each player must be able to provision itself, and once provisioned, periodically check in with the server for updates if configured to do so. The player and server must also be able to initiate a recovery process should the player enter an error state that cannot be fixed by rebooting (for example, filesystem corruption caused by power loss or failure of the storage device).

...

The following player registry entries are associated with the provisioning and recovery process. These keys can be modified by accessing the registry’s “networking” section using the roRegistrySectionBrightScript object.

Registry Key

Description

a

u

The name of the user in the account to which the player belongs

p

The account password that allows the player to access the request handler

g

The group within the account to which the player belongs

The name of the account to which the player belongs. 

ub

The URL prefix that is applied to the URLs of the ru, eu, and cu key values. This prefix is not applied to a key value containing a colon.

ru

The provisioning/recovery URL used by the player to download an autorun script

eu

The URL to which error notifications are posted

cu

The URL to which crash reports are posted

The following registry keys are specific to BSN.cloud but may also be useful for partners:

Registry Key

Description

a

The name of the account to which the player belongs. 

u

The name of the user in the account to which the player belongs

p

The account password that allows the player to access the request handler

g

The group within the account to which the player belongs

The account, username, password, and group registry keys are used for provisioning/recovery with the bsn.cloud. A request handler may appropriate these keys, but they are not required. 

...