Before you run Disposition Sweep, you must configure it
for the appropriate values. For example, you must specify the name
of the Content Engine server
that contains the records, and you can limit the sweep to just one
file plan object store. Disposition Sweep configuration values are
also used by Declassification Sweep. However, in addition to the fields
that are 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 should 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, it is recommended that
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.
- You also must edit the JAVA_HOME environment
variable in the appropriate application server section of the tool's
BAT and SH file so the variable 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 new 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 and are constrained by what
is allowed as a filename on the current operating system. Each profile
name is saved as a file appending _RMSweepConfiguration.xml to
the original filename. 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, in order to correctly show the information
in European languages (except English), you need apply the following
settings using 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
Windows ANSI code page for West European Latin). For a full list of
code pages, see the link to the Code Page Identifiers table at the
end of this topic.
To configure Disposition Sweep:
- From a command prompt, navigate to the RecordsManagerSweep
folder.
- Enter one of the following commands:
Option |
Description |
UNIX |
./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 making any changes,
click Exit.