Rule Builder > Setting Up the Execution Object Model > Working With the Deployer > Setting the Classpaths

The Execution Object Model panel of the Deployer Settings dialog box allows you to view or manually set the paths to the java classes, XML Schemas, or Web services that make up the XOM. The top part of the Execution Object Model panel displays your file system, and the bottom part of the panel displays the various XOM paths.

Any of the following files can be added to the XOM path:

To add a file to the XOM path:

  1. Click a file in the list in the top panel. The full name is displayed in the text field in the middle panel.
  2. Click the add arrow in the middle of the dialog box or double-click the selection. The selected file is added to the user part of the XOM in the lower panel of the dialog box.

The example in Figure 18.3 illustrates how the NCL.xsd, BAL.xsd, and TRL.xsd files can be added to the XOM path.

images/deploy_05.png

Figure 18.3    Defining the Execution Object Model Classes

User Java Classpath

To add a directory or an archive file to the User Java Classpath list:

  1. Click a directory, .jar file, or a .zip file in the top part of the panel. The full name is displayed in the text field in the middle panel.
  2. Click the add arrow in the middle of the dialog box or double-click the selection. The selected file is added to the user part of the XOM in the lower panel of the dialog box.
  3. Click the OK button to register your choice.

User Dynamic Classes

This path allows you to specify XML Schemas or Web services that will be loaded into the XOM as dynamic classes.

  1. To add an XML Schema to the User Dynamic Class list:
    1. Click an .xsd or .xom file in the top part of the panel, and then click the arrow in the middle of the panel, or double-click the file in the top part of the panel.
    2. The only valid file extensions are .xsd for an XML Schema file and .xom for a proprietary serialization format of the object model created from an XML Schema.
    3. If you choose an .xsd file you can define a package name to prefix the names of the loaded dynamic execution classes.
    4. To do this click the .xsd file in the bottom part of the panel, and then click the Set Package button, or click the file itself.
    5. The file name becomes editable, and you can type a package name.
  2. To add a local Web service to the User Dynamic Class list:
    1. Click a .wsdl file in the top part of the panel.
    2. Click the arrow in the middle of the panel, or double-click the file in the top part of the panel.
  3. To add a remote Web service into the User Dynamic Class list:
    1. Click an http:// node in the top part of the panel, and type in the Uniform Resource Locator (URL) of a Web Services Description Language (WSDL) in the text field below the list of implementation elements, as shown in Figure 18.4.

    2. images/addRuleService.gif
    3. Figure 18.4    Selecting a Web Service
    4. Click the arrow in the middle of the panel to add this URL to the User Dynamic Class list.
    5. Click the OK button to register your choices.

See Also

Connecting a Remote Engine | Setting a Ruleset Extractor Class | Exporting a Ruleset


Customer Support | Copyright © 1987-2004 ILOG S.A. All rights reserved. Legal terms. PREVIOUS   NEXT