Sometimes it is necessary to clear the CMS caches.
This can be done via the OpenText WSM interface or manually, folder by folder..
So here’s a quick list of folders describing their purpose:
- Page Cache
C:\\<OpenTextInstallFolder>\\ASP\\PageCache
The PageCache is generating pages for the CMS while you work in the authoring interface. So that you don’t have to load everything out of the DB everythime a page is called. This can be cleared manually when logged into the server or via CMS interface (Administer Project Structure > Project > Clear Page Cache) - Image Cache
C:\\<OpenTextInstallFolder>\\ASP\\ImageCache
The ImageCache is taking care of images which have been resized on the server and are displayed to you in the browser so that the CMS doesn’t have to use imagemagick to resize images every time you load a page. - XML Cache
C:\\<OpenTextInstallFolder>\\ASP\\XmlCache
The Xml Cache is on the fly generated config files for user settings, language variants and other “stuff”… It’s usually one of my first suspects when I think I need to clear some caches and it can be done via the Server Manager as well (Administer Application Server > Application Servers > SERVER NAME > Clear Language Resource Cache) - RedDotTemp
C:\\<OpenTextInstallFolder>\\ASP\\RedDotTemp
This one takes care of the publishing process. All files to be published will be created in the RedDotTemp folder first, then compared to what’s on the server and then the changes will be send through via FTP (publishing to a local directory will always publish everything). Don’t just delete everything in here, the LIVESERVER folders shouldn’t be touched.
How to trick OpenText WSM into a clean full site publish
If you think the publishing process doesn’t take over all files, I suggest changing the publishing target by adding a slash (or removing it) to the target folder path. The files will still end up in the right location but the CMS will take this as a new FTP target and initiate a full site publish with a clean cache.
Disclaimer and why you shouldn’t do this in a production environment
In general I recommend to not clear caches manually unless you’re on a development environment. Doing this on a production environment will have an impact on performance and should only be executed via the CMS interface in order to prevent the deletion of folders used by the CMS.
Update 2012-02-15, I just uploaded the VB script by Alok Varma for you to download, simply rename to .vbs and it’s good to go. Here’s the file: ClearCache VB Script
Please Note: Rename the ClearCache.txt to ClearCache.vbs. We can run the vbs file from “Command Prompt” or “Microsoft (r) Console Based Script Host”. Please change the file path in script to reflect your CMS settings.
