Rule Builder > Setting Up the Execution Object Model > Exporting a Ruleset |
Exporting a Ruleset |
PREVIOUS NEXT |
The export command in the Rule Builder is equivalent to extraction and publication of the ruleset only. You can export rulesets as .irl
, .xrl
, and .xml
files.
.irl
format (the default) allows you to either save a rule file for later use, or to send a ruleset to an engine embedded in a business rule application.
.xrl
format is only used to save a rule file for later use or processing by another application.
.xml
format containing only the ruleset "signature", that is the list of input and output parameters. Some tools require to know what input they can give to the ruleset and what output they can expect, without the need to know how it works inside, and without parsing the ruleset. For example, a tool could use the signature to generate an EJB that invokes the ruleset. The signature is sufficient to generate the EJB.
To export the current ruleset to a file that will be directly understandable by the rule engine:
ruleset.xsd
, statement.xsd
, value.xsd
, flowstatement.xsd
, condition.xsd
, and common.xsd
. These files are located in the <InstallDir>/doc/xml
directory.Ruleset export uses the project ruleset extractor.
You can also export rulesets as part of a RuleApp. The RuleApp is exported as an archive (.jar
) file that can be integrated into a Business Rule Execution Server (BRE Server).
Setting a Ruleset Extractor Class | Exporting a RuleApp Archive
Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |