Start the two IBM® InfoSphere™ Enterprise Records component
queues, RM_Workflow_Util and RM_Operations as part of configuring
your InfoSphere Enterprise
Records workflows.
The component queues cannot be used until they have been started.
The RM_Workflow_Util and RM_Operations component queues
were defined in Process regions.
- After the Component Manager starts, the list of available component
queues displays and indicates whether the queues started correctly.
- If the queues do not start, verify that the account information
specified on the Advanced tab of the Component Manager is correct.
To configure Component Queues:
- Access the Process Task Manager on the Application Engine or Workplace XT server.
If
the Process Task Manager is not running, launch it.
- Navigate to the following location on the Application Engine or Workplace XT server:
- Application Engine
- AE_install_path/FileNet/AE/Router
- Workplace XT
- WPXT_install_path/FileNet/WebClient/Router
- Launch the Process Task Manager by running the following
command:
- UNIX®
- routercmd.sh
- Windows®
- routercmd.bat
- If a Component Manager has not already been created for
the connection point, use the following steps to create one.
- Click the Component Managers node
and ensure the Service Username and Service Password are properly
filled in.
- Right-click the Component Managers node
and select New.
- Select an existing connection point from the list and
click OK.
- Click Apply.
- Highlight the connection point name and select the General tab.
- Enter a Service Username and Service Password for an
account that has the Process Engine Administrator and Records Administrator
roles, and the rights to start the InfoSphere Enterprise
Records queues.
- (Optional) Select the Automatically Started check box.
- Select the Required Libraries tab and specify the required
JAR files to add.
Important: After updating
the Component Manager, do not move or delete the JAR files, as this
can cause the system to function improperly.
- Stop the Component Manager, if running.
- Add the javaapi.jar file.
- Click the Add icon.
- Browse to the following location on the Application Engine or Workplace XT server:
- Application Engine
- AE install path/FileNet/AE/Workplace/WEB-INF/lib
- Workplace XT
- WPXT install path/FileNet/WebClient/WorkplaceXT/WEB-INF/lib
- Add the javaapi.jar file from this location.
Important: Move the javaapi.jar file you
added to the top of the list of required libraries after adding additional
JAR files.
- Add additional required JAR files.
- Click the Add icon.
- Browse to the RM_install_path/FileNet/RM/Workflow/configureRMworkflow/lib directory.
- Add the following JAR files:
- rmapi.jar
- rmapiresources.jar
- rmworkflow.jar
- rm-transfer-api.jar
- xercesImpl.jar
- xlxpScanner.jar
- xlxpScannerUtils.jar
- xlxpWASParsers.jar
- jsr173_1.0_api.jar
- On the Web Services tab, Web Services Settings sub-tab,
ensure the Listener URL and Listener Local Host for Application Engine or Workplace XT are properly filled in.
- (InfoSphere Enterprise
Records Transfer
Tool only - all web application servers) If you are using JRE 1.4
on a UNIX platform, on the Advanced tab, add the following to the
JRE Parameters already listed:
-Djava.endorsed.dirs=RM_install_path/FileNet/RM/Workflow/configureRMworkflow/
lib/endorsed
- On the General tab, to ensure that all component queues
are started, verify that the Queues field contains an asterisk (*).
- Click Apply.
- Start the Component Manager.