IBM Enterprise Records, Version 5.1.+              

Configuring component queues

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 have been started.

The RM_Workflow_Util and RM_Operations component queues were defined in Process regions.

To configure Component Queues:
  1. Access the Process Task Manager on the Application Engine or Workplace XT server.

    If the Process Task Manager is not running, launch it.

    1. 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
    2. Launch the Process Task Manager by running the following command:
      UNIX
      routercmd.sh
      Windows
      routercmd.bat
  2. If a Component Manager has not already been created for the connection point, use the following steps to create one.
    1. Click the Component Managers node and ensure the Service Username and Service Password are properly filled in.
    2. Right-click the Component Managers node and select New.
    3. Select an existing connection point from the list and click OK.
    4. Click Apply.
    5. Highlight the connection point name and select the General tab.
    6. 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 IBM Enterprise Records queues.
      Attention: Changes to the username and password in the Process Task Manager is only for the current thread. Once Component Manager is restarted, it uses the values in the Process Configuration Console.
    7. (Optional) Select the Automatically Started check box.
  3. 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.
    1. Stop the Component Manager, if running.
    2. Add the javaapi.jar file.
      Attention: Check to see if the javaapi.jar is already added to the required library. If it is move it to the top. Otherwise add it and move it to the top.
      1. Click the Add icon.
      2. 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
      3. Add the javaapi.jar file from this location.
      4. Move the javaapi.jar file you added to the top of the list of required libraries after adding additional JAR files.
    3. Add additional required JAR files.
      1. Click the Add icon.
      2. Browse to the ier_install_path/Workflow/configureRMworkflow/lib directory.
      3. 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
  4. 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.
  5. On the General tab, to ensure that all component queues are started, verify that the Queues field contains an asterisk (*).
  6. Click Apply.
  7. Start the Component Manager.


Feedback

Last updated: August 2011


© Copyright IBM Corporation 2011.
This information center is powered by Eclipse technology. (http://www.eclipse.org)