Deleting all versions and draft items after WCM migration

          If you rolling out the WCM project (or migration) and if you have separate authoring and delivery environments, it doesn't make sense to keep all versions and draft content items on delivery environment.

1. use version cropper module to delete the all versions just after migration (Doesn't require the versions on the production at all (at least for the first time))

2. Delete all draft items as we don’t need any draft items on the production (delivery environment)

1.Removing all versions could take some time to execute and the module may timeout. If so, you can either temporarily increase the timeout, or run the module multiple times on with each run covering a given library and/or data type.

2. To get the report of what version details to clear use the following URL:

Check below for more detailed options available on the version cropper module 
  • day, month and year
The version details will be cleared prior to the date specified in the day, month and year parameters. The day and month parameters must be valid integers and accepts both single digit (e.g. 9) and double digit (e.g. 09) values. If no date is specified, then the date will default to one year before the current date.
  • keep
Specify minimum number of version entries to keep on Web Content Management items. If a number is not specified, then the minimum number of version entries to keep will default to 10. The minimum number can not be less than 1 because you cannot delete the most recent version entry.
  • restrictOn
Select the item types to run the Version Cropper Module against. If no item types are specified, all item types will be processed. Use the following parameters for each item-type:

style for presentation templates
template for authoring templates
Cmpnt for components
  • library
Enter a library name. If the "library" parameter is omitted, the default library that has been configured in the file will be used.
  • fix
If omitted or set to false, a report listing which version items will be cleared is displayed. If set to true, version items will be cleared as specified.

1. You can also consider disabling Versioning for all items on production delivery servers if not required . But make sure to enable versioning on either authoring or delivery server to restore to previous versions based on the business requirement. By default versioning is enabled for all WCM items.

Change the following properies in for "versioningStrategy"

# enable version control for the following types.
# possible options are always | never
versioningStrategy.AuthoringTemplate = always
versioningStrategy.Component = always
versioningStrategy.Taxonomy = always
versioningStrategy.Workflow = always
versioningStrategy.Content = always
versioningStrategy.PresentationTemplate = always
versioningStrategy.Site = always

Cloning JCR repository insteady of syndication or import and export WCM libraries

Syndicating items from one server to another, either after migration or to roll out a new WCM environment can take a long time. Your database backup and restore features can be used to speed up the initial set up and clone data from one repository to another. This makes your system ready for syndication to be used from then on for incremental updates.

Cloning JCR repositoy will be another approach in migration projects to switch from existing system to target WCM system.This will reduce the production switch time dramatically.

Click here to download the instructions for cloning WCM repository from IBM.

Custom Launch Pages WCM7 (

What is custom launch page ? 
Custom Launch Page is another view of the Authoring Portlet. It will make Content Authors not worry about the lot things that they don't need worry about it. It reduces lot cluttering while authoring.

Following are custom launch pages are available as out of the box in IBM wcm7.0.0.1
a). /jsp/html/BasicHomePage.jsp
b). /jsp/html/HomePage.jsp
c). /jsp/html/defaultLaunchPage.jsp

you can find these jsp files under

Following screen shows how to configure the custom launch page in authoring portlet

BasicHomePage Custom Launch will look like below (/jsp/html/BasicHomePage.jsp)

HomePage Custom Launch will look like below (/jsp/html/HomePage.jsp)

Default Launch Page (/jsp/html/defaultLaunchPage.jsp) will just display the link to authoring portlet back.

Note: We can always add additional custom WCM API code inside these JSP's to enhance or modify according to the business requirement.