ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Administering Rule Execution Server > Changing the Default Behavior of the Execution Stack > Execution Unit Configuration Properties

Similar to Web applications, EJBs, and enterprise applications in J2EE, resource adapters use two deployment descriptors to define their operational parameters. The deployment descriptor ra.xml is packaged inside the RAR in a subdirectory called META-INF and is defined by Sun Microsystems in the J2EE Connector Specification. The second deployment descriptor is specific to the J2EE application server and defines operational parameters unique to that server. There is no such file for WebSphere.

The RAR descriptor describes a number of Execution Unit (XU) properties that apply to the connector and not just a single ruleset.

If you want to modify the behavior of the XU in J2EE, you should edit the specific application server descriptors or use the administration console.

In J2SE, you can change the XU configuration by adding a ra.xml file with modified configuration property values to your classpath. This file will override the default_ra.xml descriptor provided in the jrules-bres-execution.jar.

The following XU configuration properties can be changed either in the application server administration console or in the connector deployment descriptor.

XU Configuration Properties
Name 
Description 
traceAutoFlush 
Flushes the log stream each time a message is written. 
profilingEnabled 
Activates profiling capabilities. 
persistenceType 
Loads the rulesets from the persistence layer. The possible values are: 
- datasource: for J2EE datasource  
- jdbc: when the XU is used in J2SE mode  
- file: for file persistence 
persistenceProperties 
Specifies the parameters of the persistence layer. 
defaultConnectionManagerProperties 
Specifies the parameters of the ConnectionManager provided by the XU. 
plugins 
Specifies plug-ins that can receive rule engine events generated by the XU.  
traceLevel 
Level of logged messages: OFF, SEVERE, WARNING, INFO, FINE. 
Java log levels are used as the reference. The ALL range is also supported. ALL indicates that all messages should be logged, which includes ILOG's debug/internal traces. 
blockingRulesetParsing 
When set to true, current executions of the ruleset in memory are finished, but no new executions can be run on the current ruleset until the new ruleset is parsed. The default is false. In this case new executions on the current ruleset can be run until the new ruleset is parsed. 
jdkLoggingEnabled 
When set to true, JDK logging is enabled. The default is false. JDK logging can be enabled only for the Sun Application Server. 

Related Concepts

Execution Unit (XU)

Related Tasks

Configuring the XU for the XU Plug-in
Adding Execution Unit (XU) JCA 1.5 Connection Factories