Automated tasks for composite applications

Automated tasks for composite applications

You can manage application maintenance by controlling automated tasks that are available using the XML configuration interface. The automated tasks clean up resources associated with deleted applications and detect application status based on policy settings.

Task Description
com.ibm.portal.ai.task.AITask_Purger This task cleans the system of all resources belonging to applications that have been deleted. By default, this task runs at 12:00 p.m. (midnight) on Sunday. Avoid scheduling this task to run close to the time when the portal cleanup service runs. Generally, it is recommended to not run this task when the system is under load.
com.ibm.portal.ai.task.AITask_PolicyHandler This task detects application status by sensing the conditions specified by the policy settings for each composite application running on the server. By default, this task runs at 10:30 p.m. daily.
com.ibm.portal.ai.task.AITask_IMPORT_RESTORE_POINTS This task imports backups from the file system and cannot be scheduled. It is required when a backup from a different server is imported, for example, when staging a development or test environment to a production environment.

Parameters for scheduling tasks
Like the tasks for cleaning up portal resources, these periodic maintenance tasks for composite applications can be run immediately or at specified intervals. The scheduling interval parameters dayOfMonth and dayOfWeek are optional and are mutually exclusive. Each scheduling interval parameter requires a value for the parameter startTime. To run a task daily, use only the parameter startTime.
In contrast to the task that cleans up portal resources, composite application tasks can be scheduled to run more than once. For example, you can schedule an application task to run every Monday at 10.00 a.m. and every Friday at 1:00 p.m. To accomplish this, simply add the task instance ID to the task ID in the task command. Tasks for composite applications can be started immediately.
The example below schedules the task to run every Monday, starting at 10:00.
<task action="create" name="com.ibm.portal.ai.task.AITask_Purger">
<dayOfWeek>5</dayOfWeek>
<startTime>10:00</startTime>
</task> 
Parent
Manage applications
Back up, archiving, and restoring applications
Delayed cleanup of deleted portal pages
XML configuration reference
Sample XML configuration files

+
Search Tips | Advanced Search

Task	Description
com.ibm.portal.ai.task.AITask_Purger	This task cleans the system of all resources belonging to applications that have been deleted. By default, this task runs at 12:00 p.m. (midnight) on Sunday. Avoid scheduling this task to run close to the time when the portal cleanup service runs. Generally, it is recommended to not run this task when the system is under load.
com.ibm.portal.ai.task.AITask_PolicyHandler	This task detects application status by sensing the conditions specified by the policy settings for each composite application running on the server. By default, this task runs at 10:30 p.m. daily.
com.ibm.portal.ai.task.AITask_IMPORT_RESTORE_POINTS	This task imports backups from the file system and cannot be scheduled. It is required when a backup from a different server is imported, for example, when staging a development or test environment to a production environment.