Sample task class names
- com.ibm.icpcs.transactionserver.scheduler.ScheduledTaskSample
- This example task simply emits a banner containing the task name to the console. It has a single optional
parameter that can be specified, wait, that specifies an amount of time for the task to
consume. If the wait parameter is specified, two (2) banners are emitted, one for the start of the wait
interval and one for the end of the wait interval. Sample tasks that are set up using the wait option should
be specified as background tasks so the scheduler is available for processing other tasks during the wait
period.
This is a sample of how to write a custom task. Please modify this sample to suit your needs.
- com.ibm.icpcs.transactionserver.scheduler.ScheduledTaskCyclePurge
- This task attempts to purge any Transaction Server business days (cycles) that have reached
their expiration time. The expiration time interval is set using the bdayDataExpiration
option in the configuration data (config.properties). The expiration interval must be set
in the configuration profile and cannot be passed as a task parameter. It is recommended that the business day
purge task be executed in the background so the scheduler remains available for processing other tasks.
For more information about configuring this task, see Automating the Business Day Purge Process.
- com.ibm.icpcs.transactionserver.scheduler.TrackingMonitor
- This task enables periodic sampling of the TRACKABLES table in the Transaction Server database for entries that are overdue or late. If configured, this task issues any configured alert messages for the overdue or late trackable item and posts a TrackedItemOverdue event in the event monitor. Additional processing for trackable item overdue/late events can be configured with a user-written event handler that intercepts the "tracked item overdue" event code. This task should be run in the background.
- com.ibm.icpcs.transactionserver.scheduler.ReportDirectoryMaintenance
- This task is used to schedule maintenance of the Transaction Server report directory. At this time, the Transaction Server cleans up any reports that are sufficiently aged to keep the report directory volume static. It is usually specified as a repeating event occurring daily. A single parameter, expiryPeriod, is used to specify any report file age required for deletion and defaults to 20 days. Any time interval specification is available for this parameter. If not overridden, a default report directory maintenance task is scheduled to occur every day at midnight and delete any report file over 20 days old. To override the default configuration, specify your own entry in your scheduler configuration file. The NAME element must match the default scheduler value for ReportDirectoryMaintenance.
- com.ibm.icpcs.transactionserver.scheduler.PreAllocateBusinessDayTask
- This task is used to schedule the preallocation of Transaction Server business days during
nonpeak processing for when activation is needed. Preallocating business days is required only when using a
Transaction Server that is configured with tables partitioned by business day. Failure to correctly
pre-allocate business days during non peak processing may cause ingestion to fail and corrupt the database.
Schedule the business day preallocation to occur at a time when the Transaction Server is not taking new work, such as over a weekend. The preallocate business day task can be configured to run at a specific time and day and ensure a specific number of business days are preallocated. These preallocated business days do not appear in any business day lists and are not available for use until they are activated. Preallocate enough business days to handle the maximum business day requirements for the time interval specified. Allocating business days in a Transaction Server configured with tables partitioned by business day during ingestion interferes significantly with ongoing work. It can cause the image cash letter load operations to fail when work for a new business day is encountered. Having a supply of preallocated business days prevents the image cash letter failure.
The preallocated business day task has the following parameters:Table 1. Preallocate Business Day Task Parameters Parameter Type Default Description preAllocationCount Integer 16 The target number of preallocated business days to be available at task invocation. This may not be the same number of preallocated business days created. Preallocated business days may be left over from a prior task invocation.