Delayed cleanup of deleted portal pages
Overview
Portal resources, such as pages, components or portlet instances are kept persistent in the portal database. When an administrator deletes a page, all its derived pages and dependent resources and content are deleted with it. The actual deletion can take considerable time, depending on the size of the portal and the number of resources affected by the deletion. Therefore, if the deletion takes place immediately after the user completes the deletion task, this might impact portal performance for users. On the other hand, if the deletion is delayed and scheduled for an off peak time, it will not affect portal response time and thereby user experience.
The delayed deletion of pages is performed by a cleanup service.
Note that this cleanup service works only for WebSphere Portal installations that are based on versions of WAS with IBM WebSphere Business Integration Server Foundation, which includes the Scheduler service and supports asynchronous beans. Portal installations that are based on WAS versions without the IBM WebSphere Business Integration Server Foundation support cannot use the delayed cleanup service, but have to delete pages and dependent resources synchronously.
Configure immediate or delayed deletion of portal pages
You can configure the deletion cleanup to happen either immediately when you delete the page or later:
Immediate deletion The page and all resources that depend on it are deleted immediately after the user completes the action for the deletion. Delayed deletion The page is marked for deletion, but the page and all dependent resources are actually deleted later. Note that once the page has been marked for deletion, users cannot view or otherwise access the page any longer. You can change between immediate and delayed the deletion of portal pages by configuring the property value scheduler.cleanup.enabled located in...
wp_root/shared/app/config/services/DataStoreService.propertiesSetting scheduler.cleanup.enabled to true enables delayed deletion of portal pages. Pages and dependent resources are deleted by the scheduled cleanup service. Setting to false disables deletion of portal pages by the scheduled cleanup service. Pages and the dependent resources are deleted immediately when the user completes the action for the deletion.
Set this property to true if you want the deletion of pages to be delayed and performed by the scheduled cleanup service. This property defaults to true, if the portal installation is based on a version of WAS that includes the Scheduler service.
The scheduled cleanup service works only when your portal installation is based on a version of WAS that includes the Scheduler service. This service is part of the IBM WebSphere Business Integration Server Foundation.
By its default schedule configuration, the cleanup service runs weekly, on Saturdays at 8 pm.
If you delete a page with an object ID and then use the XML configuration interface to re-create the same page with the same object ID, you might receive an application error when browsing that re-created page.
Configure your own delayed deletion schedule by using the XML configuration interface
You can configure the delayed deletion schedule according to your requirements by using the task tag of the XML configuration interface of WebSphere Portal. You can define a daily, weekly, or monthly schedule. You can also use the XML configuration interface to run individual cleanup tasks at arbitrary intervals.
In order for your customized schedule to be observed by the portal, enable the property scheduler.cleanup.enabled in the file...
wp_root/shared/app/config/services/DataStoreService.properties...by setting it to true.
See also
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.