Cleanup for IBM WCM Versions

When IBM Web Content Manager, which is also called as IBM WebSphere portal, 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 there is a chance that your system may slow down.

If you want to know how many version nodes you contain, then run the below SQLquery and check for the number of entries in the jcr:versioning workspace. In the above SQL query replace the JCR with the actual (respective) schema.

Start“

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

”Stop.

Note: “Make sure that you have your database (db) backup before triggering the fix mode.”

In WAS AdminConsole:

Go to WAS Admin Console -> Resources -> Resource Environment Providers -> WCM WCMConfigService

Set the following:

versioningStrategy.Content manual

versioningStrategy.SiteArea manual

Now restart the JVMs. You can remove the versions that you do not need any more.

The changes that are made for Version Cropper in WebSphere Portal version 7 and 8 is now called Clear Versions.

There are two options with the Clear Versions module - one to report the number of versions that it will clean and then the fix mode that will clean the versions. In the sample below we keep the current version and one extra version behind. Note that one system version is always kept behind by the system even if you delete all versions.