Rule Execution Server

Troubleshooting information for Rule Execution Server and its console.

Finding the cause of an improper Rule Execution Server configuration
When Rule Execution Server does not work as expected, you might want to investigate the Execution Unit (XU) configuration.
Tuning the Decision Runner web application
You improve the performance of simulation runs in the Business console.
Tuning the Rule Execution Server logging level
To make it easier for you to fine-tune and analyze logs, each Rule Execution Server component uses its own logger. By using the appropriate logging service for your application server, developers can log messages that are based on message type and level. They can also control how these messages are stored at run time.
Determining the cause of a performance issue
When a performance issue occurs in your test or production environment, it might be difficult to determine whether it is caused by the Rule Execution Server execution stack, the environment (application servers, networks, and client APIs such as REST), or the customer code calling the ruleset execution. Setting the log to gather certain information helps you narrow down the cause of the performance problem.
Resolving slow first execution of a ruleset
You can force class loading during the ruleset loading.
JDBC not bound
A JDBC not bound error message is raised when an error occurs during the creation of the data source.
Fixing a memory leak from using the HTDS REST API with JSON parameters
Using the hosted transparent decision service (HTDS) REST API with JSON parameters might cause a memory leak. You can prevent this issue by setting up a configuration parameter in the web.xml file for HTDS.
Limitations on OpenAPI specifications and tools
You might face some restrictions concerning the OpenAPI specifications and tools when you use the hosted transparent decision service (HTDS) through OpenAPI-based clients.
Limitation of the default maximum file size for deploying a RuleApp archive
For transaction security reason, the maximum file size for a RuleApp archive is limited. It is set to 100 MB by default. When you try to upload, restore, or deploy a RuleApp Archive whose size exceeds 100 MB, you get an error message. You can fix the issue by increasing the value of the maximum file size in the deployment descriptor file of the Rule Execution Server console management archive.
Troubleshooting Rule Execution Server on the Liberty profile server
Find here how to troubleshoot your Rule Execution Server configuration on the WebSphere Liberty profile server.

Parent topic: Troubleshooting and support for Operational Decision Manager