When restarting the Component Manager verify that the required
JAR files are included in the required libraries.
To restart Component Manager:
- Windows only:
From the Windows Services
console, verify that the Process Application Engine Services
Manager service is running.
- Start Process Task Manager using the routercmd.sh or routercmd.bat command
file.
The file is located in the following directory:
Option |
Description |
Application Engine |
AE_install_path/FileNet/AE/Router |
Workplace XT |
WPXT_install_path/FileNet/WebClient/Router |
- Expand the Component Managers node.
- If the existing Component Manager is running, stop it.
- Select the existing Component Manager, and select the General tab.
- Enter a Connection Point name for the connection point
used by Application Engine or Workplace XT.
- Enter a Service User Name and Service Password for an account
that has Process Engine Administrator
and Records Administrator roles, and the rights to start the IBM® Enterprise
Records queues.
- Optional: Select the Automatically
Started check box.
- Select the Required Libraries tab.
- Specify or verify the required JAR files.
- From the Application Engine or Workplace XT directory add the javaapi.jar file
(if it is not already present).
Component |
Directory |
Application Engine |
AE_install_path/FileNet/AE/Workplace/WEB-INF/lib |
Workplace XT |
WPXT_install_path/FileNet/WebClient/WorkplaceXT/WEB-INF/lib |
Important: Move the javaapi.jar file
to the top of the list of required libraries when adding additional
JAR files.
- From the ier_install_path/Workflow/configureRMworkflow/lib directory,
add the following files (if they are not already present):
- rmapi.jar
- rmapiresources.jar
- rmworkflow.jar
- rm-transfer-api.jar
- xercesImpl.jar
- xlxpScanner.jar
- xlxpScannerUtils.jar
- xlxpWASParsers.jar
- jsr173_1.0_api.jar
- From the AE_install_path/FileNet/AE/Router directory
in Application Engine or the WPXT_install_path/FileNet/WebClient/Router directory
in Workplace XT, add the
following file (if it is not already present):
- ContentExtendedOps.jar (upgrades from releases
other than 4.5.1 only)
Important: After updating the Component Manager,
do not move or delete the JAR files, as this can cause the system
to function improperly.
- Click Apply.
- Click Start on the toolbar.