Summary
Moxie's caches are directories that Moxie modules and Moxie system services use exclusively to store files. The files in these directories are Moxie digital signage system assets. These files are referenced using a unique naming scheme so they can be managed by Moxie.
Installation Locations and Options
There are several Moxie cache locations throughout a Moxie installation. Many of the caches used by Moxie are relatively small and secondary in nature but there is one cache, the Data Server cache, whose location is customizable by the user upon the installation of Moxie.
When installing Moxie for the first time, an option to choose the Moxie cache (the Data Server cache) location within the system, is offered. This is the primary cache for exclusive use by the Data Server. This Data Server cache is used as the central repository and holds all of the media assets that have been uploaded into Moxie.
Default Locations
Caches are located on Drive C by default.
The Data Server cache is located on Drive C by default. It can be modified using the Moxie Data Server Configuration (MDSC) tool.
If Moxie is installed in a location other than C:\, then the default directory reference path, displayed as Drive C in the example paths, reflects this change.
- Data Server:
C:\ProgramData\Omnivex\ Moxie\Cache\ - Moxie Studio running on:
Windows 7 32-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files\Omnivex\Moxie\Studio\Studio\Cache\
Windows 7 64-bit or Server 2008 64-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files(x86)\Omnivex\Moxie\Studio\Studio\Cache\ - Services
Script Service running on:
Windows 7 32-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files\Omnivex\Moxie\Script Engine\ScriptEngine\Cache\
Windows 7 64-bit or Server 2008 64-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files (x86)\Omnivex\Moxie\Script Engine\ScriptEngine\Cache\
Sync Service running on:
Windows 7 32-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files\Omnivex\Moxie\Sync Service\SyncService\Cache\
Windows 7 64-bit or Server 2008 64-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files (x86)\Omnivex\Moxie\Sync Service\SyncService\Cache\ - Players running on:
Windows 7 32-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files\Omnivex\Moxie\Player\Omnivex Moxie Player\Cache\
Windows 7 64-bit or Server 2008 64-bit:
C:\ProgramData\Omnivex\Moxie\Drive C\Program Files (x86)\Omnivex\Moxie\Player\Omnivex Moxie Player\Cache\
Why caches change size
There are a variety of typical scenarios responsible for changes in cache size.
- The Moxie Data Server's cache size increases every time new content is uploaded. If files are deleted from the Moxie Data Server, using the Data Manager module, they are also deleted from the cache.
- The Moxie Studio maintains a cache of the current modules it has loaded and the Moxie assets that are being used by those modules. The modules are stored as ZIP files and are renamed with an ID assigned by the Data Server. The asset files are not managed automatically, but can be deleted by purging using the System Manager module.
- Service caches increase in size when files are used by the service. For example, syncing files into Moxie from the network file system. The sync service cache is managed automatically.
- Each Moxie Player has its own cache for local storage of content files and other Moxie data items. A Player's cache size increases if it is assigned new content. A Player does not automatically delete old or unused content files. These files can be deleted by purging a Player of its content using the System Manager module.
Troubleshooting Caches - Purges and Modifications
When troubleshooting, it may be necessary to purge or modify one or more caches. As a best practice, it is recommended that you back up the files you are planning on modifying in the event that changes need to be reversed.
Cache modifications should be considered a troubleshooting option of last resort. If you are unsure that modifying a cache is the correct course of action for your issue, consult the Omnivex online support forums for further information.
Note: Never make a modification to a cache while it is in use by any Moxie services. Ensure that all Moxie services have been stopped before attempting modifications.
Data Server cache
The Data Server cache is customizable and can be located anywhere the Data Server Service has permission to access. The cache contains the database references to files uploaded by Moxie users and is automatically maintained by the Data Server Service. As files are deleted, using the Data Manager module, they are also purged from this cache location. Do not manually modify or delete the contents of this cache. If the files are manually removed from the cache, files that are used by Moxie will not reference correctly and this results in unpredictable behavior in displayed content. The files will continue be visible in the Data Manager module, however all of the Moxie applications that connect to the Data Server will not be able to resolve the locations of these missing assets.
The working directory is used as a temporary space within the Cache folder for Moxie to manage files before they are copied into the cache folder. If the Moxie Data Server service is stopped and there are files in this directory, it is safe to delete them.
Studio
The Studio cache is used as a storage area for the loading of the modules. Moxie manages a set of .zip files which contain the information to build the modules as Moxie starts up. These .zip files should not be modified or deleted.
The Studio cache is also used by the modules when accessing resources in the Data Server. Modules place assets in the cache as they need them.
If the Studio cache requires purging, the cache and its corresponding backbone.sdf file must be deleted. The .sdf file and the cache reference each other and must both be deleted; deleting only one leaves the Studio in an unpredictable state. When the purged Studio is restarted, it creates a new file and cache.
Moxie System Manager contains a function to purge the files on a Studio.
Player
A Player's cache stores all the assets that have been assigned to the Player. Maintenance is not automatic as files may be required for future content playback. Moxie Player Manager and System Manager both contain functions to purge the files on a Player.
If the Player cache requires purging, the cache and its corresponding backbone.sdf file must be deleted. The .sdf file and the cache reference each other and must both be deleted; deleting only one leaves the Player in an unpredictable state. When the purged Player is restarted, it creates a new file and cache.
