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.
- The Workflow Transfer utility and the RMWorkflowTransferConfig.xml configuration
file used in this procedure are available in the ier_install_path/RM/Workflow/configureRMworkflow folder.
- The RMWorkflowTransferConfig.xml file specifies
information about how the workflows are transferred. Before you run
the utility, you must edit the file with information specific to your
environment.
- (IPv6) If your Process Engine is using IPv6 you must:
- Verify that you have installed an IPv6 supporting JRE.
- Configure the WorkflowTransfer file to point
to an IPv6 enabled JRE.
- In addition to using the IBM® Enterprise
Records workflows,
you can create your own workflows or modify the workflows that are
provided with IBM Enterprise
Records.
For more information, see the IBM FileNet® P8 Information
Center topic Create and modify workflows.
To transfer the Workflow Definitions:
- Refer to the planning checklist you completed for values
you might need to complete these steps. See the link at the end of
this topic.
- 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.
- (PE using IPv6) Configure the WorkflowTransfer.bat or .sh file
to point to an IPv6 enabled JRE.
- Open the WorkflowTransfer.bat or .sh file
for editing. Default location: ier_install_path/Workflow/configureRMworkflow
- Create a JAVA_HOME variable to point
to a JRE with IPv6 support.
- 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
- Save the file.
- Transfer the workflows.
- From a command window, navigate to the ier_install_path/Workflow/configureRMworkflow directory.
- 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
- 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: ier_install_path/Workflow/configureRMworkflow/WorkflowTransfer.log.
- If errors occurred, check the WorkflowTransfer.log file
in the following directory: ier_install_path/Workflow/configureRMworkflow/WorkflowTransfer.log