Troubleshooting Rule Engine plug-in issues

The Rule Engine plug-in is a stand-alone rules-driven engine with the Java engine running in the back end. This plug-in provides an interface for defining and running rules.

Related topics

Rule-Engine-plug-in-configuration

Enabling-plug-ins

To troubleshoot Rule Engine plug-in issues

  1. Verify the Rule Engine plug-in configuration.
    For more information, see Rule-Engine-plug-in-configuration.
    For more information about the 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.
  2. Troubleshoot common plug-in-related issues.
    For more information, see the General-approach-for-troubleshooting-plug-in-issues.
  3. To further investigate the issue, 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

  1. Select AR System Administrator Console > Application Administration Console > Custom Configuration > Asset Management > Advanced Options > License Engine Configuration.
  2. Click Open. The License Engine Configuration form appears.
  3. From the Log Level list, select DEBUG.
  4. Click Save, and then click Close.

The SWLMFilter.log file generates the debug logging for the Rule Engine plug-in without restarting AR System server.

To enable logs by using the Plugin Server Configuration form

  1. In a browser, open the AR System Administration Console, and select System > General > Plugin Server Configuration.
  2. On the Plugin Server Configuration form, from the Plugin Server Instance list, select the instance for which you want to enable logs.
  3. Go to the Plugin Server Configuration tab.
  4. In the Logging Configurations area, from the Log Level list, select DEBUG.
  5. Click Apply. 
    The arjavaplugin.log file generates the debug logs for the Rule Engine plug-in without restarting 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*