Rule Execution Server reference

Refer to these topics for predefined ruleset properties and RuleApp properties, for execution unit (XU) persistence properties and configuration properties, RuleApp management using the MBeans Accessor API, Ant tasks, public API, and guidance on the graphical user interface in Eclipse.

MBeans accessor API
To manage RuleApps, you can use the MBeans accessor API. Decision Server provides both a default implementation and a specific implementation for WebSphere® Application Server.
Rule Execution Server Java API
Reference documentation for the Rule Execution Server Java™ public API.
Rule Execution Server REST API
Reference documentation for the REST public API.
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.
Persistence properties for execution units
You use the persistenceProperties parameter to configure the persistence property of the execution unit (XU).
Predefined ruleset and RuleApp properties
Context parameters for the Rule Execution Server console
The Rule Execution Server console is a web application. You can configure it by modifying the values of the context parameters in the web.xml deployment descriptor.
Hosted transparent decision services reference
Hosted transparent decision services serialize Java primitive and simple types to XML and return status codes to the calling application.
Ant tasks
Ant tasks are available for you to deploy RuleApps and Java XOMs. They support both HTTP and HTTPS communication protocols.
Messages
Each listed message provides a detailed description about the error message and some steps to try and resolve the error.