Rule Builder > Setting Up the Execution Object Model > Working With the Deployer > Using the Deployer Settings Dialog Box |
Using the Deployer Settings Dialog Box |
PREVIOUS NEXT |
The Deployer Settings dialog box is composed of three panels, corresponding to the three activities associated with the deployer:
To open the Deployer Settings dialog box:
An example of the Deployer Settings dialog box with the Execution Object Model displayed is shown in Figure 18.2.
This option allows you to reference the path to the execution classes of a rule engine that you started remotely, so that you can use them as a source for BOM classes in the Rule Builder.
If you started an engine remotely, it may reference execution classes that are not known to the Rule Builder. In this case, you need to upload the execution classes of the engine into the BOM to be able to debug your rules.
To add an object model to the XOM when the rules are executed remotely:
If you are not using the Rule Builder to debug a remote application or write new rules dynamically, you can hide the Current Engine Object Model list from the Execution Object Model panel. To do this:
The corresponding node is removed from the Execution Object Model tree in the bottom part of the panel.
This allows you to set a Java-like package name for classes imported from an XML Schema.
To set up the package name for an XML Schema:
All classes imported from a given XML Schema are contained in the specified package.
Note |
This does not apply to .wsdl files. |
To reorder files on the user path:
Several files may contain classes with the same name. The system takes the first class that is found in the XOM path according to the order of the files. This can be used, for example, to overload JRules properties, see Rule Builder Customization User's Manual for more information.
To remove files from the XOM path:
This means that these files are no longer referenced by the XOM, and rules already written on BOM classes that map to XOM classes will not be executed. The Error\Warnings panel displays a message such as "xxx class not found". You can either delete these rules or change the part of the rule that references the deleted XOM class.
Setting the Classpaths | Setting Up Ruleset Imports | Setting a Ruleset Extractor Class | Connecting a Remote Engine | Exporting a Ruleset | Setting a New Ruleset Extractor Class | Execution Classes
Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. | PREVIOUS NEXT |