Before you run Disposition Sweep, configure it for the
appropriate values. For example, specify the name of the Content Platform Engine server that contains
the records. Also, limit the sweep to just one file plan object store.
About this task
Disposition Sweep configuration values are also used by Declassification
Sweep. In addition to the fields required by Disposition Sweep, Declassification
Sweep also requires an ObjectStore Name value and ignores the fields
that are not required.
- If IBM® Enterprise
Records is deployed
on IBM WebSphere® Application Server, any of the IBM Enterprise
Records tools that rely upon JACE
EJB transport protocol use the JRE that comes with the same version WebSphere Application
Server or IBM WebSphere application client.
- If IBM Enterprise
Records is deployed
on JBoss Application Server or WebLogic Server, any of the IBM Enterprise
Records tools that rely upon JACE
EJB transport protocol use the JRE that comes with the same version
application server.
- Edit the JAVA_HOME environment variable in
the appropriate application server section of the BAT and SH file
of the tool. Edit the variable so it is pointing to the same JRE version
as the application server where IBM Enterprise
Records software is installed. For example, the IBM WebSphere Application Server entry might look like the
following entry: set JAVA_HOME=%WS_DIR%/java.
- Profiles allow you to save different configurations and run Disposition
Sweep using these configurations without the need to reconfigure them.
You can create a profile or edit an existing profile by running the configure command and providing the profile name. After the profile is created, you can run Disposition Sweep using
the specific profile. Profile names are composed of characters, numbers,
periods, underscores, or dashes. Profile names are constrained by
what is allowed as a file name on the current operating system. Each
profile name is saved as a file appending _RMSweepConfiguration.xml to the original file name. For example if the profile name is Profile1, the resulting file name is Profile1_RMSweepConfiguration.xml. If no profile
names are given, Disposition Sweep defaults to using the original,
default profile of RMSweepConfiguration.xml.
Important: A log file name is now associated with each profile.
So, when a sweep is run, a separate log file is created for each profile
and given an appropriate name, for example, Profile1_RMSweepConfiguration.log.
Restriction: If you are going to run the
IBM Enterprise
Records Disposition Sweep tool
in the Windows operating system, apply the following settings. Apply
these settings in order to correctly show the information in European
languages (except English). Apply the settings from the Command Prompt
before running the tool:
- Set the font property to Lucida Console.
- Change the code page to relative Windows ANSI code page (from
1250 to 1257). For example, if you want to show French in DOS windows,
run 'chcp 1252' to change the code page to 1252. Code page 1252 is
the Windows ANSI code page for West European Latin. For a full list
of code pages, see the Code Page Identifiers table.
Procedure
To configure Disposition Sweep:
- From a command prompt, go to the RecordsManagerSweep folder.
- Enter one of the following commands:
Option |
Description |
AIX, HP-UX, Linux, and Solaris |
./RecordsManagerSweep.sh -DispositionSweep -configure
[-profile "profile name"] |
Windows |
RecordsManagerSweep.bat -DispositionSweep -configure
[-profile "profile name"] |
- Specify the appropriate values for the following fields. You can clear existing values by clicking Reset.
- Click Configure.
- To reset all values to default values, click Reset. To close the Sweep Configuration Console without changes, click Exit.