Overview: Execution Code Generators

ILOG JRules User Guide > Executing Rules > Tasks > Executing a Ruleset Using Rule Execution Server > Overview: Execution Code Generators

Overview: Execution Code Generators

PREVIOUS NEXT

To invoke a ruleset on Rule Execution Server you must write execution code to locate a deployed RuleApp that contains the ruleset on an application server. This code is best written in Rule Studio inside a client project. Rule Studio provides several project generators to assist with this task:

a POJO execution code generator (stateless rule session execution)
a Web service generator, which generates either a Web service class for JDK 5, or a monitored transparent decision service project with the required files and method calls, depending on your selection
a Service Component Architecture (SCA) execution code generator
a Scenario Service Provider (SSP) set up, which generates ANT files to update the SSP archive

You can also extend the provided generators to generate these project components. For more information see Maintaining Execution Code Generators.

Because JRules is divided into modules (executionserver, scenariomanager, studio, teamserver, jrules2dotnet), each module contains its own lib directory.

You need to define executionserver.home before importing classpath-executionserver.xml, and engine.lib.dir for classpath-engine.xml. The executionserver.home value should be <InstallDir>/executionserver and the engine.lib.dir value should be <InstallDir>/executionserver/lib. There is no need to define this property when importing classpath-executionserver.xml.

An example of an Ant build file that uses the executionserver.j2se.classpath is provided in <InstallDir>/executionserver/samples/j2serulesession/build.xml. This should give you enough information to make your packaging and show how to use the classpath-executionserver.xml file.

Note