[Enterprise Extensions only]
  Next topic

Using the RuleImporter tool

ruleimporter <properties-file> <import-files> [options]

<properties-file>
The fully qualified name of a file containing the JNDI names of the BRBeans EJBs for the rule set that is to be accessed. Refer to The BRBeans Properties file for a definition of the contents of this file. This parameter is required.
<export-list-files>
One or more fully qualified names of the files containing XML rule definitions to be imported. These files must contain XML in the format defined in WAS_HOME\AppServer\Enterprise\bin\brb.dtd. This XML format is also defined here. This parameter is required.

Options

-[v]erbose
Show verbose output while importing. This will show the rule definition of every rule that is imported.
-[t]est
Only parse the input files, do not create rules in the application server. This will ensure that there are no errors in the syntax of the rule definitions provided in the XML document. Combined with the -verbose option it can also be used to see exactly what rules will be imported.
-[u]pdate
When a rule in an input file has the same primary key as an existing rule, update the existing rule with values from the input file. If this option is not specified, then any rule with the same primary key as an existing rule will cause an error and that rule will not be imported.
-[c]ommiteach
Perform a commit after each rule is created rather than creating all rules in a single transaction. If this option is not specified, then all rules are created in a single transaction. This means that if any rule causes an error, the entire transaction will be rolled back and none of the rules will be imported. If -commiteach is specified, then when a rule causes an error only that rule will not be imported. Other rules will still be imported.

  Next topic