InfoSphere Enterprise Records, Version 4.5.1.3+              

Configuring the Disposition Sweep tool

Configure the disposition sweep tool with your environment's values before you can run it. Configure page and run from a command properties. Slow performance. Error log for troubleshooting.

To configure and run the Disposition Sweep tool:

  1. Log on to the server where you installed the Disposition Sweep tool.
  2. With a command prompt, navigate to the following directory: RM_install_path/FileNet/RM/RecordsManagerSweep/
  3. Open the Configuration settings page for the Disposition Sweep tool by running the following command:
    UNIX®
    ./RecordsManagerSweep.sh -DispositionSweep -configure
    Windows®
    RecordsManagerSweep.bat -DispositionSweep -configure
  4. In the Configuration settings page, enter the appropriate values for your environment. Click Configure to start the configuration.
    Table 1. Configuration values to set for your environment
    Field Required Provide this information
    Server Name Yes Provide the name or IP address of the Content Engine server where you want to run the Disposition Sweep process.
    Port Number Yes Provide the WSI Data Service port number.
    Object Store Name No Provide the GUID or Name of the FPOS on which you want to run Disposition Sweep. If you do not provide a value, the Disposition Sweep process will run on all the FPOSs associated with the specified Content Engine server.
    Run For Record Types No Specify the value as True to have the Disposition Sweep process check all record types for any modifications made to the associated disposition schedules. If the disposition schedule of any record type has been modified, the Disposition Sweep process updates all the entities associated with that record type. Specify the value as False to have the record types ignored.
    Entity GUID No Provide the GUID of the InfoSphere™ Enterprise Records entity (Classification Scheme, Record Category, or Record Folder) for which you want to run the Disposition Sweep process. The Disposition Sweep process will run against the specified entity and all of its children. By default, this node is empty and all entities are processed.
    User ID Yes Provide the user name that Disposition Sweep uses to log on toContent Engine for performing calculations and to log on to the Process Engine for launching workflows. The user must be assigned the Records Administrator role, be a member of the Content Engine Administrators group, and be an object store administrator for the FPOS.
    Password Yes Provide the password for the user ID.
    PE Connection Point Yes Enter the name of the connection point used by Application Engine or Workplace XT.

    When configured to only process auto-destroy actions, this field is not required and can be left blank.

    Update Batch Size No By default, InfoSphere Enterprise Records stores a maximum of 1,000 entities in a batch for update.
    Read Batch Size No By default, InfoSphere Enterprise Records stores a maximum of 10,000 entities in a batch for read.
    Thread Count No Enter the number of processing threads that InfoSphere Enterprise Records uses during the disposition sweep process. The best practice is to specify one thread for each logical CPU on the Content Engine server. For example, enter “8” if there are eight logical CPUs on your Content Engine server. The default is 1.
    Activity Log File Name No Provide the name and path of the error file to be created by the Disposition Sweep process. By default, a file called ErrorFile is created in the <RM_install_path>/FileNet/RM/RecordsManagerSweep folder by the Disposition Sweep process. If the process runs without error, the error file is zero bytes in length.
    Run For Vital (Optional) No Set this to either False or True. (default: False)
    When the configuration finishes, you can run the Disposition Sweep tool.
  5. To run the tool, execute the following command:
    UNIX (From a Cron job or command prompt)
    ./RecordsManagerSweep.sh -DispositionSweep
    Windows (From Windows Scheduler or command prompt)
    RecordsManagerSweep.bat -DispositionSweep
  6. Verify that the Disposition Sweep tool ran correctly by viewing the log file at RM_install_path/FileNet/RM/RecordsManagerSweep/DispositionSweepActivity.log. If the log file is empty, the Disposition Sweep process was successful.


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)