Adding Partner CMS Players to Networks

players that are configured for a partner cms application can also use a bsn cloud network connection to access players for configuration and maintenance to do this, temporary replace the partner cms autorun with an autorun brs that can make the changes needed to connect to bsn cloud this process is described below players cannot be migrated from one bsn cloud network to another unless the player provisioning record is first deleted from the old network and created in the new network (see provision docid\ cyl9kpm02co5rgcb9wqqv for more information) otherwise, the player will remain in the old network prerequisites you must be able to access the player on the local dws through a browser you must know the name of the target bsn cloud network you will need a registration token see the appendix for instructions after getting the token, you must download the cloudparameters json file from the appendix and customize it edit line 9 to add the registration token edit line 10 to add the target network name, then save the file replace the autorun and reboot the player open the local dws for the player you are adding to bsn cloud and go to the sd tab upload the cloudparameters json file to the sd card download and open the standalone autorun brs file in the appendix if you saved the cloudparameters json file under a different name on the sd card, make sure that line 4 of standalone autorun brs references the correct name upload the standalone autorun brs to the sd card go to the sd tab in the local dws and locate the autorun brs file select the cogs icon, shown in image 1, to go to the rename section rename autorun brs to autorun backup rename standalone autorun brs to autorun brs go to the control tab in the local dws and reboot the player the player will appear in the brightauthor\ connected network tab when it has rebooted, and the autorun brs will again reference the partner cms application image 20240305 163734 png appendix brs and json files https //archbee doc uploads s3 amazonaws com/0prk6so2dy9ldu77jb8d1/eawbh0sjyto nfgjb2zl2 cloudparameters json https //archbee doc uploads s3 amazonaws com/0prk6so2dy9ldu77jb8d1/wzuo69 min0wr5xtntdgo standalone autorun brs get a registration token through bsn cloud create a new setup package with bsn cloud select save setup and choose a location to save the package on your computer open the folder where you saved the package and open the current sync json file at the top of the file you will find similar script to image 2 the long string after "bsnregistrationtoken" , is your registration token the string after “account” should match your target network name inserted in step 4c screenshot 2024 03 05 at 8 28 20 am png get a registration token through an api first get your oauth token correctly issued for the target network, then see token entity (v3) docid\ xftpkrowdwpe6dqhynwfe