Configure our own delayed deletion schedule using the XML configuration interface

Use the IBM WebSphere Portal XML configuration interface to configure the delayed deletion schedule according to the requirements. Define a daily, weekly, or monthly schedule. We can also use xmlaccess.sh to run individual cleanup tasks at arbitrary intervals.

1. Edit:
   PORTAL_HOME/PortalServer/doc/xml-samples/Task.xml

2. Uncomment and edit the entry that corresponds to the scheduled time to set.

   By default, the Task.xml file is set to run the scheduler immediately one time.

3. Save the changes.

4. Import the modified Task.xml file using xmlaccess.sh (xmlaccess).

What to do next

1. For the customized schedule to be observed by the portal, set scheduler.cleanup.enabled property to true in the WP Data Store Service.

2. If we delete a page with an object ID and then re-create it with XML configuration interface, we might receive an error message that indicates the operation was canceled because it would cause a duplicate key value.

3. When we run the cleanup task, xmlaccess.sh schedules only the task to be run in WAS and returns.

   This does not mean that WebSphere Application Server runs the task immediately. To determine when a task started and ended, check the SystemOut.log log file for the messages EJPDE0005I and EJPDE0006I. These messages confirm the cleanup task successfully completed. After you confirm, we can run the XML script for re-creating a page with the same object ID as it had before the deletion.

Parent Delayed cleanup of deleted portal pages

Related tasks:

Set service configuration properties

Related reference:

Portal service configuration