Start the two IBM® Enterprise
Records component
queues, RM_Workflow_Util and RM_Operations as part of configuring
your IBM Enterprise
Records workflows.
The component queues cannot be used until they are started.
About this task
The RM_Workflow_Util and RM_Operations component queues
were defined in the earlier process regions topic.
- 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.
Procedure
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, start it.
- Go 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
- Start the Process Task Manager by running the following
command:
- AIX, HP-UX, Linux,
and Solaris
- routercmd.sh
- Windows
- routercmd.bat
- If a Component Manager is not created for the connection
point, use the following steps to create one.
- Click the Component Managers node
and ensure that the Service Username and Service Password are properly
completed.
- 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 or Content Platform Engine Administrator and Records
Administrator roles, and the rights to start the IBM Enterprise
Records queues.
Important: Changes to the user name and password in the Process
Task Manager is only for the current thread. After Component Manager
is restarted, the tool uses the values in the Process Configuration
Console.
- (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. Deleting
the files can cause the system to function improperly.
- Stop the Component Manager, if running.
- Add the javaapi.jar file.
Important: Check to see whether the javaapi.jar is
already added to the required library. If the file is added, move
it to the beginning of the list. Otherwise add it and move it to the
beginning of the list.
- Click the Add icon.
- Browse to the following location on the Application Engine or Workplace XT server:
- Application Engine
- AE install path/Workplace/WEB-INF/lib
- Workplace XT
- WPXT install path/WorkplaceXT/WEB-INF/lib
- Add the javaapi.jar file from this location.
- Move the javaapi.jar file you added to the
beginning of the list of required libraries after adding additional
JAR files.
- Add additional required JAR files.
- Click the Add icon.
- Browse to the ier_install_path/Workflow/configureRMworkflow/lib directory.
- Add the following JAR files:
- ddcp.jar
- ddcpResources.jar
- ierLogTrace.jar
- rmapi.jar
- rmapiresources.jar
- rmworkflow.jar
- rm-transfer-api.jar
- super-csv-2.0.1.jar
- xercesImpl.jar
- xlxpScanner.jar
- xlxpScannerUtils.jar
- xlxpWASParsers.jar
- jsrl73_1.0_api.jar
- bdp-iface.jar
- bdp-impl-jace.jar
- bdp-impl-jaceResources.jar
- listener.jar
- rm-bds.jar
- rm-sm-util.jar
- On the Web Services tab, Web
Services Settings subtab, ensure the Listener URL and
Listener Local Host for Application Engine or Workplace XT are properly completed.
- 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.