InfoSphere Enterprise Records, Version 4.5.1.3+              

Transferring workflow definitions

A workflow definition is a processing template that Process Engine uses each time that the workflow runs. It routes the work, data, attachments, and other info to participants so that they can complete activities. When you import the FPOS data model files to an object store, several workflow definitions are imported to the Root Folder\Records Management\Workflows directory.

Before the workflows can be used, they must be transferred to Process Engine. The transfer is done by running a utility from the Application Engine or Workplace XT machine. The end result of the transfer is an executable version of each workflow definition in the Process Engine database.

To transfer the Workflow Definitions:
  1. To access the worksheet file, p8_worksheet.xls, that contains the parameter values to specify in the InfoSphere Enterprise Records installation, see the using the installation and upgrade worksheet section. In the worksheet file, verify that the Data > Filter > AutoFilter command is enabled.
  2. Edit the RMWorkflowTransferConfig.xml file and fill in the Content Engine Server Name, Content Engine WSI Port Number, the Connection Point Name and the FPOS Name.
    Important: If the object store name contains non-English characters, save the RMWorkflowTransferConfig.xml file as UTF-8.
  3. (PE using IPv6) Configure the WorkflowTransfer.bat or .sh file to point to an IPv6 enabled JRE.
    1. Open the WorkflowTransfer.bat or .sh file for editing. Default location: RM_install_path/FileNet/RM/Workflow/configureRMworkflow
    2. Create a JAVA_HOME variable to point to a JRE with IPv6 support.
    3. Add the following options on the Java™ command line:
      -Djava.net.preferIPv6Addresses=true -DpreferIPv4Stack=false
      Example for Windows®, change:
      java -classpath.;%CLASSPATH%
      -Dwasp.location=%COMMON_FILES%/CE_API/wsi -
      Djava.security.auth.login.config=%COMMON_FILES%/CE_API/config/jaas.conf.WSI
      com.filenet.deploymenttool.WorkflowTransfer.WorkflowTransfer
      to:
      "%JAVA_HOME%/bin/java" -classpath.;%CLASSPATH%
      -Djava.net.preferIPv6Addresses=true -DpreferIPv4Stack=false -
      Dwasp.location=%COMMON_FILES%/CE_API/wsi -
      Djava.security.auth.login.config=%COMMON_FILES%/CE_API/config/jaas.conf.WSI
      com.filenet.deploymenttool.WorkflowTransfer.WorkflowTransfer
    4. Save the file.
  4. Transfer the workflows.
    1. From a command window, navigate to the RM_install_path/FileNet/RM/Workflow/configureRMworkflow directory.
    2. Start the Workflow Transfer utility, by using the following command:
      UNIX®
      ./WorkflowTransfer.sh
      On UNIX servers, you must have execute and write permissions to the WorkflowTransfer.sh file.
      Windows
      WorkflowTransfer.bat
    3. When you are prompted, enter the user_ID and password of a user with the object store administrator role on the FPOS object store.
      Restriction: Sun Java System Directory Server only
      For the user_ID, you must use the fully qualified LDAP name, for example:
      uid=Administrator,cn=CE Admin Group,ou=FileNet,dc=com
      If errors occurred, check the WorkflowTransfer.log file in the following directory: RM_install_path/FileNet/RM/Workflow/configureRMworkflow/WorkflowTransfer.log.
  5. If errors occurred, check the WorkflowTransfer.log file in the following directory: RM_install_path/FileNet/RM/Workflow/configureRMworkflow/WorkflowTransfer.log


Feedback

Last updated: November 2010


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