Execution components

Execution components are components that enable the execution of a ruleset by the execution unit (XU). You choose between execution components depending on the ruleset deployment and execution platform, on the execution pattern, and on the possible use of EJB.

The Rule Execution Server API includes interfaces known as rule sessions (see ilog.rules.res.session). You can use that API to bind an application and call the execution module.

A Rule Execution Server application must contain the Java™ classes that execute in the client JVM and deployment descriptors that describe the EJBs and other application server resources used by the client.

A client module must embed the Rule Execution Server execution components that are used to reference the XU.

The Rule Execution Server execution components enable you to write code to interact with the Rule Execution Server model without any dependency on the internal implementation.

You choose which execution component to use depending on the following criteria:

• The platform on which you plan to execute the ruleset, see Execution and management stacks.

• The execution pattern that is most appropriate for your application, see Execution patterns.

• Whether deployment will take place on a Java SE or Java EE platform, see Java SE and Java EE applications.

• Whether you use EJB or not: Using EJB factories.

• Whether you want synchronous or asynchronous execution, see Synchronous execution patterns.