The Disposition Sweep tool supports several EJB protocols
(iiop, t3, jnp), in addition to the default WSI protocols (http, https),
for communicating with the IBM® FileNet® Content Engine.
The
Connection menu on the
Disposition
Sweep Configuration page allows the selection of one of
the WSI protocols or one of the EJB protocols. By default, the
Connection field
displays the WSI protocols. If you want the EJB protocols to be displayed,
the
InfoSphere™ Enterprise
Records Sweep batch
file (
RecordsManagerSweep.bat for Windows or
RecordsManagerSweep.sh for
UNIX), must be modified. This does not apply to
InfoSphere Enterprise
Records Hold Sweep.
To modify
the Disposition Sweep tool so that it displays EJB protocols when
configuring disposition sweep:
- Log on to the machine where you installed the InfoSphere Enterprise
Records Sweep Tool with Administrator
privileges.
- Open the RecordsManagerSweep.bat (Windows)
or the RecordsManagerSweep.sh (UNIX) file with
your preferred text editor.
- Set the CONNECTION_TYPE variable to EJB. WSI is the default. If anything other than EJB or WSI is
entered, WSI is assumed. For example:
set
CONNECTION_TYPE=EJB (Windows)
CONNECTION_TYPE-EJB (UNIX)
- Set the APP_SERVER variable to your application server
type; either WebSphere, WebLogic,
or JBoss. For example:
set
APP_SERVER=WebShere (Windows)
APP_SERVER=WebLogic (UNIX)
- If you have a WebSphere® Application
Server,
make the following additional changes:
- Set the WS_DIR variable to your WebSphere Application
Server or WebSphere Client installation directory.
set WS_DIR=C:\Program Files\IBM\WebSphere\AppServer (Windows)
WS_DIR=/opt/IBM/WebShere/AppServer (UNIX)
- Set the NAMING_PROVIDER_URL to the URL for your Content Engine. set
NAMING_PROVIDER_URL=iiop://CE Server:port# where:
- CE Server is the name of your Content Engine Server machine.
- iiop is the default protocol used. Specify
the protocol that your Content Engine Server
is using.
- 2809 is the default port. Specify the port
number used by your Content Engine Server.
- For the CORBA_CONFIGURL, ensure that the path to the sas.client.props file
is correct. In particular, be sure that the default AppSrv01
folder is correct. If not, change it to match your WebSphere installation.
- If you have a WebLogic Server 9
or earlier, make the following additional changes:
- Copy the weblogic.jar file from
the WebLogic install path/lib folder
to the RM install path/RecordsManagerSweep/lib folder.
- Uncomment the line:
REM set
CLASS_PATH=%CLASS_PATH%;lib/weblogic.jar (Windows)
#
CLASS_PATH=“$CLASS_PATH”:lib/weblogic.jar (UNIX)
- Uncomment or comment other lines as necessary to use
one of the various JRE levels.
- If you have a WebLogic Server 10
or later, make the following additional changes:
- Copy the wlfullclient.jar file
from the WebLogic install path/lib folder
to the RM install path/RecordsManagerSweep/lib folder.
- Uncomment the line:
REM set
CLASS_PATH=%CLASS_PATH%;lib/wlfullclient.jar (Windows)
#
CLASS_PATH=“$CLASS_PATH”:lib/wlfullclient.jar (UNIX)
- Uncomment or comment other lines as necessary to use
various JRE levels.
- If you have a JBoss Application Server,
make the following additional changes:
- Copy the jbossall-client.jar file
from the JBoss install path/client folder
to the RM install path/RecordsManagerSweep/lib folder.
- Uncomment the line:
REM set
CLASS_PATH=%CLASS_PATH%;lib/jbossall-client.jar (Windows)
#
CLASS_PATH=“$CLASS_PATH”:lib/jbossall-client.jar (UNIX)
- Change other lines as necessary to use one of the various
JRE levels.
To modify the Records Manager Disposition Sweep
Configuration user interface so it displays WSI protocols
again, simply reset the CONNECTION_TYPE variable to WSI.