Wednesday, 13 June 2012

IBM Web Content Manager - Cleanup of WCM versions

This from my IBM colleague, Thomas Hurek

When you install WebSphere Portal / Web Content Manager version 7 and 8 versioning is enabled by default. That means whenever you update a WCM artifact an additional version is created. After some time you have a lot of versions and this can slow down your system. 

If you want to find out how many version nodes you have you can run the following SQL query and check for the number of entries in the jcr:versioning workspace (replace JCR with the according schema):

SELECT JCR.ICMSTJCRWS.WSID AS WORKSPACE_ID, WSNAME AS WORKSPACE_NAME, COUNT(*) AS NODE_COUNT 
FROM JCR.ICMSTJCRWSNODES, JCR.ICMSTJCRWS 
WHERE JCR.ICMSTJCRWSNODES.WSID > 0 AND JCR.ICMSTJCRWS.WSID = JCR.ICMSTJCRWSNODES.WSID 
GROUP BY JCR.ICMSTJCRWS.WSID, WSNAME


My recommendation is to only enable versioning for the design items and keep versioning set to manual for content items and site areas.

Want to know more ? Then read the rest of Thomas' article here.



No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...