Adding RuleApp execution artifacts to an existing project

You can add execution artifacts to an existing Rule Execution Server client project to execute RuleApps.

Before you begin

  1. The class path of the project uses the variable ILOG_EXECUTION_SERVER_HOME to declare the Rule Execution Server JAR files. This variable is set to <InstallDir>/executionserver. Therefore, to run the project, you must first installRule Execution Server.
  2. To call the correct libraries, use the class paths that are defined in <InstallDir>/executionserver/lib/classpath-executionserver.xml.

Procedure

  1. Click File > New  >  Other.
  2. On the Select a wizard page, expand Rule Designer and then select Artifacts for RuleApps.
  3. Click Next.
  4. Select a generator (template) to help you call the rulesets, and then click Next.
  5. Select the project where the artifacts are generated, and then click Next.
  6. Select the RuleApp project for which you want to generate files, and then click Next.
  7. Select the ruleset archives that you want to call from the project, and then click Next.
  8. Add initial values for each ruleset parameter in each selected ruleset, as follows:
    1. Select each line in the table, and then click Change.
    2. For each selected ruleset, specify the default values of the IN and IN_OUT parameters.

      The default values are read from the ruleset archives and displayed in the wizard page. If no default value is specified in the Properties page for ruleset parameters, the value set in the ruleset archive is null.

    3. Enter a value, and then click OK.
    4. Click Next.
    5. Select the check box to specify an alternative task to the main task in each ruleset archive. Enter the task name to start the ruleset execution, and then click Next.

      You can change the main task only if the ruleset archive contains a rule flow. If a ruleset has no rule flow, no line is displayed in the table for this ruleset.

    6. Specify the name for the RuleApp runner, enter the specific properties for the project, and then click Finish.

Results

If one of the generated files already exists in the project, the name is suffixed with a number. For example, if you already have a build.xml file, the generated build file is renamed build2.xml.