Troubleshooting Rule Engine plug-in issues
The Rule Engine plug-in is a stand-alone BMC Remedy rules-driven engine with the Java engine running in the back end. This plug-in provides an interface for defining and running rules.
To troubleshoot Rule Engine plug-in issues
- Verify the Rule Engine plug-in configuration.
For more information, see Rule Engine plug-in configuration.
For more information on AR System Administration: Plugin Server Configuration form and AR System Administration: AR System Configuration Generic UI form, see Configuring java plug-in servers and Updating configuration settings by using the AR System Configuration Generic UI form.
- Troubleshoot common plug-in related issues.
For more information, see General approach for troubleshooting plug-in issues.
- If you need to investigate the issue further, enable the following logs:
Enabling logging for the Rule Engine plug-in
To troubleshoot plug-in related issues, you must enable plug-in logging by changing the plug-in log level in the RLE:Configuration form, or by editing the plug-in log level in the log4j_pluginsvr.xml file.
To enable logs by using the RLE:Configuration form
- Select AR System Administrator Console > Application Administration Console > Custom Configuration > Asset Management > Advanced Options > License Engine Configuration.
- Click Open. The License Engine Configuration form appears.
- From the Log Level list, select DEBUG.
- Click Save.
- Click Close.
The SWLMFilter.log file now generates the debug logging for the Rule Engine plug-in without restarting the AR System server.
To enable logs by using the Plugin Server Configuration form
In a browser, open the BMC Remedy AR System Administration Console, and click System > General > Plugin Server Configuration.
- On the Plugin Server Configuration form, from the
- Select the Plugin Server Configuration tab.
- In the Logging Configurations area, from the Log Level list, select DEBUG.
The arjavaplugin.log file now generates the debug logs for the Rule Engine plug-in without restarting the AR System server.
The plug-in history is recorded in the RLE:RunHistory form and errors, if any, are recorded in the RLE:EngineException form.