ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Administering Rule Execution Server > Execution Connection Pooling

Connection pooling is a technique used for sharing server resources among requesting clients.

In J2EE, the Rule Execution Server execution stack takes advantage of the application server pooling services. The pooling parameters should be set according to the application requirements and specific characteristics. These parameters rely on the related J2EE services.

In J2SE, the XU JAR includes a J2EE Connector Architecture (JCA) container that creates and pools connections to the XU. The XU contains a default pool implementation, which can be replaced or modified by providing any class implementing the ilog.rules.bres.xu.cmanager.IlrPool interface.

images/IlrPool.png

The pool configuration is stored in the resource adapter deployment descriptor META-INF/ra.xml.

The name of the property to configure the J2SE pool is defaultConnectionManagerProperties.

You can modify:

All properties of this resource adapter configuration property are sent to the pool instance by calling the method IlrPool.initialize(Properties).

A Connection object represents a connection with a ruleset. A single application can have one or more connections with a single ruleset, or it can have connections with many different rulesets.

The default implementation sets the maximum size to 10. The size cannot be changed after the initial value has been assigned.

The following behavior applies:

Related Concepts

Rule Execution Server Management Model
Management and Monitoring
Execution Unit (XU)

Related Tasks

Changing the Default Behavior of the Execution Stack
Management Model API Access
Invalidating Rulesets in Local VMs

Related Samples and Tutorials

How to Automate Ruleset Management