IBM Enterprise Records, Version 5.1.2    

Configuring basic schedule sweeps

Configure performance tuning parameters and the repository-wide common behavior configuration parameters for a basic sweep by using IBM® Enterprise Records Task Manager.

About this task

Before you schedule a basic sweep by using Task Manager, you can configure the performance tuning parameters and the repository-wide common behavior configuration parameters.

Procedure

To configure basic sweep parameters:

  1. Configure the performance tuning parameters from the IBM Enterprise Records user interface at Administration View > Settings > Basic Schedule Sweep. Start with the default values for these parameters, then either increase or decrease the settings to improve performance.
    For example, when you increase size you increase the memory but reduce the number of calls to the Content Platform Engine, you see the following impact.
    • On a system with a large amount of memory, increasing these values can improve disposition performance.
    • On a system with less memory available, increasing these values can decrease the system throughput and can cause an OutofMemory exception.
    Systems act differently based on the topology of the system, the amount of memory, the number of running processes, and other factors. Each system must be individually tuned.
  2. Configure the repository-wide common behavior configuration parameters from the IBM Enterprise Records user interface an Administration View > Repositories > Basic Schedule Sweep.

    The basic schedule sweep runs the appropriate queries and generates a report with the records that are ready for disposition. This task marks these records as InReport by setting the record property CurrentPhaseExecutionStatus to a random integer value 1000 - 4000. This setting enables the basic schedule sweep to filter the records to avoid duplicate records in reports. The sweep the runs a basic schedule workflow to run the disposition process. This task then groups records that are based on the reviewer that is specified for the container that contains the records. A different report and workflow are generated for each reviewer.

  3. To avoid unexpected errors, ensure that the Containers for sweep you set do not overlap with any existing valid basic schedule sweeps. For example, if you have a file plan structure, /File Plan/Category Level 1/Category Level 2, and a valid basic schedule sweep with Containers for sweep set for Category Level 1, do not create a new basic schedule sweep with Containers for sweep set for Category Level 2. In this case Category Level 2 is covered by Category Level 1.


Feedback

Last updated: November 2013
frmcg001.htm

© Copyright IBM Corporation 2013