Configuring a Rule Execution Server instance

You can configure a running Rule Execution Server instance for many purposes.

Here are a few examples.

Share server resources
Change the persistence type
Modify the behavior of the execution stack
Add connection factories to your application server
Notify the execution unit (XU) of ruleset updates
Customize Decision Warehouse

Enabling ruleset execution monitoring
To generate and store the trace of the ruleset execution in Decision Warehouse, you add specific properties to a ruleset.
Customizing a Decision Warehouse data source
The JAR files of the product distribution include a default data source. You can customize how and where the trace data is stored.
Adding data sources to Decision Warehouse
You can add dedicated data sources to Decision Warehouse and query them from the Rule Execution Server console without any loss of execution performance. You can also use an extension API to customize trace data storage by writing a custom Data Access Object (DAO).
Optimizing Decision Warehouse
You can optimize Decision Warehouse by reducing the size of execution data and using it asynchronously.
Rule session tuning
Each rule session is associated with an execution unit (XU) connection. You can configure ruleset execution to share server resources by setting up connection pools. The number of concurrent connections in a pool affects performance.
Changing the default behavior of the execution stack
You can modify the values of various execution unit properties or parameters that affect the execution stack.
Changing the default behavior of the management console
By setting the TCP/IP management mode, you can enable Rule Execution Server to manage execution unit (XU) instances that are running on a different Java™ virtual machine (JVM) or JMX MBean server than the Rule Execution Server console.
Adding execution unit (XU) JCA connection factories
You can add Java EE Connector Architecture (JCA 1.5) connection factories for execution units (XU) to the deployment descriptor of your WebSphere®, WebLogic Server, or the JBoss application server.
Notification of ruleset updates to the execution unit
You can notify an execution unit (XU) in a local Java virtual machine (JVM) cache that a ruleset has been updated and must no longer be used by the cache. You use a management session bean.

Parent topic: Managing rule execution in Rule Execution Server

Related information:

Rule artifact management and deployment

Rule Execution Server basics

Deployable packages

Overview: Ruleset execution

Monitoring Rule Execution Server events

Rule Execution Server samples