Configuration properties for execution units

You can set configuration properties for the execution unit (XU) in Java™ EE or Java SE by modifying the deployment descriptors or by using the administration console.

You can change the following XU configuration properties either in the administration console of your application server or in the connector deployment descriptor.

Important: After you have modified a property, restart the application server to apply the changes.

Table 1. XU configuration properties
Name	Type	Default value	Description
asynchronousRulesetParsing	Boolean	true	If you keep the default value, new executions on the current ruleset can be run until the new ruleset is parsed. If you set the property to `false`, current executions of the ruleset in memory are completed but no new executions can be run on the current ruleset until the new ruleset is parsed.
compiledArchivesCacheProperties	String Use a comma to separate the two parameters.	`10` for the maxSize parameter	Use this property to cache the compiled ruleset archive (containing the bytecode) that the XU generates upon the first execution of a ruleset. Use the maxSize parameter to set the maximum number of compiled archives in the cache and the path parameter to set the directory of the compiled archives cache. The cache is enabled if the path parameter is set to a valid directory. Each instance of the XU must use a different path. This property applies only to the decision engine.
defaultConnectionManagerProperties			Use this property to specify the parameters of the ConnectionManager instance that the XU provides. Used in Java SE only for tuning the connection pool. Ignored in Java EE environments. See Rule session tuning.
documentBuilderPoolProperties	String Use a comma to separate the two parameters.	`-1` (= infinite duration) for the pool.waitTimeout parameter	Use this property to specify the settings of DocumentBuilder instances. The execution unit uses DocumentBuilder instances to convert XOM objects to BOM strings, and conversely. Use the pool.maxSize parameter to set the maximum number of instances in the pool and the pool.waitTimeout parameter to set the maximum number of milliseconds before attempts at obtaining an instance from the pool fail. Attention: The 0 value means infinite timeout. Use this value with extreme caution because if the pool is overloaded, it might cause some threads to hang in the system.
memoryProfilerIncludedPackageNames	String		The estimated memory size includes only the objects from the packages that are given by the setting of the `memoryProfilerIncludedPackageNames` XU property.
persistenceProperties			Specifies the parameters of the persistence layer. For more information, see Persistence properties for execution units
persistenceType		`jdbc` in Java SE `datasource` in Java EE	Defines the type of persistence for storing rulesets. `datasource` for Java EE data sources `jdbc` when the XU is used in Java SE mode `file` for file persistence on Java EE and Java SE platforms
plugins			Use the following aliases to specify which plug-ins can receive the rule engine events that the XU generates: `DVS`, `Management`, `Event`, `HTDS`, `Monitoring`, or `SMF` (for z/OS®).
profilingEnabled	Boolean	true	Set this property to `true` to activate profiling capabilities. Restriction: You cannot use profiling on rulesets that are built with the decision engine.
rulesetUsageMonitorEnabled	Boolean	true	Activates the XU memory profiler. You can use the profiler to retrieve information about the memory that the XU uses for a ruleset.
traceAutoFlush	Boolean	false	Flushes the log stream each time a message is written. WebSphere® Application Server does not use this property.
traceLevel		FINE	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 be logged, which includes the product debug and internal traces. WebSphere Application Server does not use this property.
transformerPoolProperties	String Use a comma to separate the two parameters.	`-1` (= infinite duration) for the pool.waitTimeout parameter	Use this property to specify the settings of DocumentBuilder instances, The execution unit uses these instances to convert XOM objects to BOM strings, and conversely. Use the pool.maxSize parameter to set the maximum number of instances in the pool and the pool.waitTimeout parameter to set the maximum number of milliseconds before attempts at obtaining an instance from the pool fail. Attention: The 0 value means infinite timeout. Use this value with extreme caution because if the pool is overloaded, it might cause some threads to hang in the system.