Run Disposition Sweep

Disposition Sweep is a daemon process. To limit the performance impact on your system, schedule the process to run when the system usage is low. To run Disposition Sweep, ensure that the JVM you have installed on the machine running the process is JRE 1.4 or higher.

To run Disposition Sweep

Run Disposition Sweep from the RecordsManagerSweep folder on the machine where you installed the Disposition Sweep component. Use one of the following commands to execute Disposition Sweep:

Alternatively, you can run Disposition Sweep from a command prompt by navigating to the ..\FileNet\RecordsManagerSweep\lib folder and entering the following:

java -jar rmsweep.jar

You can verify whether Disposition Sweep ran successfully by viewing the DispositionSweepActivity.log file created in the RecordsManagerSweep folder. If the error file is empty, the Disposition Sweep process ran successfully. Otherwise, the file will contain errors that you can use to troubleshoot the problem.

NOTE Because Disposition Sweep shares some properties with Declassification Sweep, Disposition Sweep also writes some information into the DeclassificationSweepActivity.log file.

Stop Disposition Sweep

To stop Disposition Sweep, use the -stop parameter:

A message displays when the Disposition Sweep processes have stopped.

Generate reports of entities due for Full Disposition, Destroy, Transfer, or Interim Transfer

You can use Disposition Sweep to generate reports that include a list of entities that are due for full disposition, destroy, transfer, or interim transfer. Disposition Sweep saves the reports as text files in the RecordsManagerSweep directory.

To generate these reports, execute one of the following commands depending upon report type.

where:

Generate a report of entities due for Full Disposition

Generate a report of entities due for Destroy

Generate a report of entities due for Transfer

Generate a report of entities due for Interim Transfer

Check the log file

After Disposition Sweep runs, check the activity log you configured. The log file shows:

NOTE The log file does not include a list of records that failed because Content Engine does not supply that information.