CMS
Clear OpenText Web Site Management CMS Cache
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.
No related posts.
About the author:
Markus Giesen is a Solutions Architect and RedDot CMS Consultant, formerly based in Germany. Travelling around the world to find and offer solutions for a better world (in a very web based meaning). He just found a way to do this as part of a Melbourne based online consultant house. On this blog Markus shares his personal (not his employers) thoughts and opinions on CMS and web development. In his spare time you will find him reading, snowboarding or travelling. Also, you should follow him on Twitter! 
Tags: CMS Caching, Image cache, OpenText Web Site Management Caches, page cache, RedDotTemp cache, XML cache Discussion
5 comments for “Clear OpenText Web Site Management CMS Cache”
Post a comment
Stay up to date! - Get notified about followup comments
If you don't feel the urge to comment but wish to stay in the loop:Just enter your email and subscribe to new comments.
Categories
Recent Posts
Recent Comments
- Boris Crismancich on Clear the bloody cache in Open Text WSMS
- Boris Crismancich on Clear the bloody cache in Open Text WSMS
- Vijay Karthik on Two free RedDot CMS plugins – CMS User Chat & Batch Publish
- Stefan Renneke on Render Tags – An Overview
- Stefan Renneke on Render Tags – An Overview
Recent Tweets
- RT @AirKraft: Transport Canada breakout: they manage 80K pages and 300K assets with WSM(RedDot). Wow! #OTCW 2010-11-11
- The RedDot usergroup session 'Future of WCM' is in National Harbor 7, now. See you there! #otcw 2010-11-11
- RT @yttergren: @AirKraft: Calling all WSM(RedDot) devs: share your solutions on http://bit.ly/bgPIof EVERY solution can win an iPad #OTCW 2010-11-10
- Come to the Solution Exchange session. Enhance your (#reddot) CMS project! Chesapeake 12, 3:20pm #otcw Looking forward to see you there! 2010-11-10
- More updates...
Recent Posts
- OpenText enhancements with the rdQuery Framework – Finally RedDot CMS with less clicks!
- Merge variables available in the workflow’s Email task
- Clear OpenText Web Site Management CMS Cache
- OpenText Content World 2011 – Have you registered yet?
- OpenText WSM 11 – Is the “Swan” release going to fly?
- RQL development with OpenText Web Site Management Server 11
- Workaround – Placing red dots inside of OpenText CMS Render Tags
- How to show CMS authors the page status
- Project Database Schema
There really needs to be an option in SmartTree to clear the image cache on a per-project basis (just like page cache) or a “clear all project cache” type of button. I can’t count the number of times a JavaScript file or something else gets cached on us and I don’t have direct file system access to our servers. It is eternally frustrating for me.
I have created a simple VB Script file which clears all the Cache, RedDotTemp folder & Log files without going through the Action menu to do so. But use it only in certain case only.
VB Scrit code
——————
DeleteFilesFolder(”C:\Program Files\Open Text\WS\MS\ASP\RedDotTemp”)
DeleteFilesFolder(”C:\Program Files\Open Text\WS\MS\ASP\XmlCache”)
DeleteFilesFolder(”C:\Program Files\Open Text\WS\MS\ASP\PlugInCache”)
DeleteFilesFolder(”C:\Program Files\Open Text\WS\MS\ASP\PageCache”)
DeleteFilesFolder(”C:\Program Files\Open Text\WS\MS\ASP\LOG”)
DeleteFilesFolder(”C:\temp”)
Sub DeleteFilesFolder(strpath)
Dim fs, fo, files, folders, file, folder
Set fs = CreateObject(”scripting.filesystemobject”)
if fs.FolderExists(strpath) then
Set fo = fs.GetFolder(strpath)
Set files = fo.Files
Set folders = fo.SubFolders
For Each file In files
file.Attributes = 0
file.Delete vbTrue
Next
For Each folder In folders
folder.Delete vbTrue
Next
end if
End Sub
That script also tries to zap those RedDotTemp\LIVESERVER folders. Is that OK?
Yikes, that’s true!
Hello, would you please help me with following:
I am currently facing issue with RedDotTemp folder that is too large.
This issue is on Production.
Data that are stored inside and not used by live server are useless?
If I delete them this have no impact at all? Or is better to have them stored if possible to speed up publishing process.
Folder have over 100 GB and I had to delete some date anyway. So I suppose that files with older timestamps can be manually deleted. Is it true?
thank you in advance