Reference bindings for Rule Execution Server modules

You use the Java™ Naming and Directory Interface (JNDI) to organize and locate components in a distributed computing environment.

Rule Execution Server execution components are packaged in archives. You use a JNDI name to bind the execution unit (XU) inside any deployment descriptors that are used by the component that calls the simple Java rule session implementation. When you use reference bindings for Rule Execution Server modules, it is best if you keep the default JNDI name.

Execution components are packaged in the <InstallDir>/executionserver/lib/jrules-res-session-java.jar archive.

The following figure shows the reference bindings for the Rule Execution Server modules.

Reference bindings for the Rule Execution Server modules
You can use any JNDI name that you want:
  • If you use the default JNDI name eis/XUConnectionFactory, JNDI automatically binds the execution unit (XU). This is true for any deployment descriptors that are used by the component that calls the simple Java rule session implementation.
  • Conversely, if you choose a different JNDI name, you must specify it in the code of a POJO rule session.