App URL/CMS URL

in the hands on example, a player was manually provisioned by physically copying a player app to the player’s storage device since the default setup file was acceptable, provisioning of the player did not require a new setup file to be explicitly applied while manual provisioning is a very straightforward process, it poses challenges when multiple players are involved, players are in remote or hard to access locations, and/or the content needs to be updated frequently remote provisioning can therefore be highly beneficial in many scenarios the recommended method for partner provisioning of players, either manually or remotely, is through the use of setup files which can be created via brightsign control or author cms url/app url the publishing mode docid\ resciigy djrpuzgwaa4e is one of the important settings included in a setup file, and the cms url (also known as app url) publishing mode is an effective way to remotely get content onto players more details of this setup can be found here docid\ resciigy djrpuzgwaa4e , but a summary is as follows the desired autorun brs or autorun zip file is uploaded to a player accessible url the autorun zip file includes the essentials ( autozip brs and autorun brs ) and, if desired, the presentation file and associated content files the url path to the autorun brs or autorun zip file is designated as the cms url/app url (an example is available at https //www brightsign biz/examples/autorun zip https //www brightsign biz/examples/autorun zip which you may use) the player is configured with the cms url/app url there are several ways to do this a cms url/app url can be applied directly to a player or group of players in brightsign author (in the provision screen) or brightsign control you will be shown one way to do this in the next section create a cms url/app url setup using brightsign author or control (see app url setup docid\ xtwqflwci3mhbkodm7ewm ) the setup file contains info about the cms url/app url the setup file can be remotely applied to a player or group of internet connected players players download the autorun brs or autorun zip file from the cms url/app url specified in the setup file player(s) configured for a cms url/app url will, upon booting, download the autorun br s or autorun zip file from the specified cms url/app url if the file is an autorun zip file containing an autozip brs file, the player will unzip that file the player will then reboot, and then run the autorun brs file next, we will walk through another hands on example in which we provision a player directly to use an cms url/app url next example (app url) > docid\ gira9pdvypkdwjdybdhr9