DownloadPlay The Web 2010SE Home
Play The Web 2010SE |
![]()
Deployment on a corporate networkPlay The Web can use a centralized configuration file for a more efficient deployment. With such a file, every digital signage system will be updated in your organization. Store settings on a server for remote updatesMost of the Play The Web settings are stored in a .WSS file. You can store this .WSS file on a HTTP server, the same web server that is hosting web pages from your intranet or corporate web site. Doing that, your configuration file is centralized and therefore can be retrieved and updated using the network. This is an update mechanism that will push the current .WSS file to every digital signage system. This update is very light because a common .WSS configuration file weighs only a few kilo-bytes (KB). Use a custom configurationCreate a custom configuration file using Play The Web. Just set any option you need and save them in a .WSS file. Here is the list of the settings most commonly set by a .WSS configuration file:
For instance, if you are using Internet Information Server:
If you use Apache web server, you should rather store the .WSS file at this path:
Software deployment to every desktopOnce the .WSS file is stored on the server, you need to deploy files and Windows registry settings to each client. Here are the files that should be copied to every digital signage system to deploy Play The Web software:
Use your corporate deployment tool to deliver files and Registry settings to every digital signage system. Click here to know more about installation automation. Deploying configurationHere are the main settings that should be loaded into the Windows registry on each client computer:
Click here to get more information about Windows registry settings. You can also deploy manually on every digital signage system by using the "File Open from the web..." command.
Type the .WSS URL and click OK. For instance:
Using this command in Play The Web, you will need more time to deploy on every digital signage system. Using a centralized configurationThis section describes how Play The Web uses a centralized configuration file. When Play The Web is launched, the address of the .WSS file is read from the "DefaultFile" registry value. This .WSS file is downloaded through the network and stored in the Play The Web cache directory ("CachePath" registry setting). Then, the .WSS configuration file is opened and executed. At the end of the page loop, the .WSS file is refreshed if a newer version is found on the server. If your configuration file points to .pps or .swf files, these files are downloaded and stored in the cache path the same way the .WSS is cached. So, a remote update mechanism is also at work for these file types. Click to know more about PowerPoint or Flash digital signage systems. Updating a centralized configurationTo update the .WSS configuration file, copy it locally to a computer and open it using Play The Web. You can therefore update the configuration file and save these updates locally. When the new configuration file satisfies you, you can publish it by copying it again to your web server. This new file will replace the old configuration file. This updated file will now been automatically retrieved by every client and used instead of the old file. Mime type for a .WSS configuration fileWhen storing a .WSS configuration file on a web server, you should add a new mime type for .WSS files on the HTTP server. Doing this will ensure that a user who clicks on a .WSS file in a web page will get that file opened by Play The Web. Mime type for .WSS configuration file is:
If you are using Apache web server, you can add this mime type with the following command line included in the httpd.conf file or in the .htaccess file in the directory storing the .WSS file on the server:
On a Microsoft Internet Information Server (IIS), you can edit properties of the web server and add a new mime type for .WSS files. Affiliate network | Documentation | Support | Link to us Last update 03/04/2010 |