+

Search Tips   |   Advanced Search


Delayed cleanup of deleted portal pages

Get an overview of the cleanup service for portal pages and their dependent resources.

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.


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:

You can change between the immediate and delayed deletion of portal pages by configuring the property value scheduler.cleanup.enabled in the Data Store Service. For more details about this refer to the topic about Portal configuration services, section about Data Store service. Set the following Data Store service configuration parameters as required:

scheduler.cleanup.enabled = (true)

Determines whether deletion of portal pages is performed later by the scheduled cleanup service, or immediately after the user completes the deletion task. This affects the deletion of portal pages and all their dependent resources, such as components and portlet instances.

true

This setting enables delayed deletion of portal pages by the scheduled cleanup service. Pages and dependent resources are deleted by the scheduled cleanup service.

false

This setting disables deletion of portal pages by the scheduled cleanup service. Deletion of the pages and their dependent resources is triggered immediately when the administrative user runs the cleanup task.

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 IBM WAS that includes the Scheduler service.

By its default schedule configuration, the cleanup service runs weekly, on Saturdays at 8 pm.


Configure your own delayed deletion schedule by using the XML configuration interface

You can also configure the delayed deletion schedule according to your requirements by using 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.

Notes:

  1. In order for customized schedule to be observed by the portal, enable the property scheduler.cleanup.enabled by setting it to true in the DataStoreService.

    For more details about this property refer to the section about Configuring immediate or delayed deletion of portal pages above.

  2. If you delete a page with an object ID and then use the XML configuration interface to recreate the same page with the same object ID, you might receive an error message indicating the operation was aborted because it would have caused a duplicate key value.

  3. When you run the cleanup task, the XML configuration interface only schedules the task to be run in WAS and returns. This does not necessarily mean that IBM WAS runs the task immediately.

    To determine when a task started and ended, check the portal log SystemOut.log for the EJPDE0002I and EJPDE0003I messages. These messages confirm that the cleanup task has successfully completed. After you have confirmed this, you can run the XML script for re-creating a page with the same object ID as it had before the deletion.


Parent topic:

Configure portal behavior


Related tasks


Set service configuration properties


Related reference


XML configuration reference
Sample XML configuration files
Automated tasks for composite applications


Related information


Work with the XML configuration interface
Data Store Service