Delayed cleanup of deleted portal pages

 

+

Search Tips   |   Advanced Search

 

This section describes the cleanup service for portal pages and their dependent resources.

Portal resources, such as...

  • pages
  • components
  • 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.

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

We 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.

    Once the page has been marked for deletion, users cannot view or otherwise access the page any longer.

We can change between the immediate and delayed deletion of portal pages by configuring the property value...

scheduler.cleanup.enabled

...in DataStore Service as described in Setting configuration properties:

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

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

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

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 error message indicating the operation was aborted because it would have caused a duplicate key value. For more details about this refer to Problem: Re-creating and browsing a page can result in a duplicate key error.

 

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

We can also configure a delayed deletion schedule using the XML configuration interface. We can define a daily, weekly, or monthly schedule or run individual cleanup tasks at arbitrary intervals.

In order for the customized schedule to be observed by the portal, set the property...

scheduler.cleanup.enabled

...to True.

 

Related information

 

Parent topic:

Manage pages, layout, and content