If you installed any of the optional tools during the IBM® Enterprise
Records installation, you must
configure the tools on the server where they are installed. Before
you can run the IBM Enterprise
Records Disposition
Sweep or Hold Sweep applications, for example, you must configure
them for use in your environment by specifying, among other things,
the name of the FPOS and the Content Engine server
on which you want to run the sweep processes.
If you installed all of the IBM Enterprise
Records components (the Web application
and the optional tools) on a single server, then you must log on to
the server and configure each tool. If you installed the IBM Enterprise
Records components on multiple
servers, then you must log on to each server where you installed a
tool and complete the configuration procedures on each server.
Important: - Running sweep applications on your system might affect
the general system performance. You should configure your system to
run the sweep process when the system usage is low. For more information,
see the link at the end of this topic.
- Ensure that you have the required JDK version. See the IBM FileNet P8 Hardware and Software
Requirements for details.
- You do not need to reconfigure Disposition Sweep or Hold Sweep
each time you run them unless you want to change the values such as
object store, user ID, and password.
- 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 WebSphere Application
Server entry
might look like the following entry: set JAVA_HOME=%WS_DIR%/java