Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Rules Engine Administration
  Search  |  Index
Process Reference  
Rules Engine Administration
Installing and enabling
Rules repository
Transferring workflows
Workflow and repository versions
Starting Rules Builder
Creating and exporting rules
Reinitializing regions
Troubleshooting
   

Starting ILOG Rules Builder

FileNet provides a set of customized files that extend and enhance the functionality of ILOG Rules Builder. Using these customized files users can create rules for Process workflows that support the workflow data fields and workflow-specific actions—such as sending the workflow to a submap or raising an exception.

In order to create and run business rules for Process workflows, ILOG Rules Builder must be started from the command prompt using a custom startup file (runilog.bat on Windows or runilog on UNIX) provided by FileNet. Before using this file, you must update the file with the location of the Java Runtime Environment (JRE) and ILOG JRules on your system. Failure to update and use the startup file will result in workflows that do not execute as expected or runtime errors. For instructions on updating the startup file, see Enable Rules Engine integration in the Installation Guide.

NOTE If you choose to create your own startup file for ILOG Rules Builder ensure that:

  • the FileNet provided .jar files fnbal.jar, ri.jar, and re.jar are included in the CLASSPATH statement
  • the file, fnbuilder.properties, is specified in the -properties option. The fnbuilder.properties file implements a file locking mechanism to ensure that the Rules repository is not corrupted by simultaneous updates from Rule Builder and Process Engine.

See runilog.bat (Windows) or runilog (UNIX) for example syntax.