Configure the Rule Engine Server

The administrator can use the Administration to configure the Rule Engine Server.

Configuration actions that can be done include:

  • Setting the Root folder where the core configuration and the runtime folder are located. The Rule Engine runtimes created are stored in sub-folders under the runtime folder.
  • Enabling/disabling the Sentinel monitoring. See Sentinel monitoring.
  • Managing file listeners. See Manage listeners.
  • Configuring the report generation for the Rule Engine Server. The configuration applies to all the runtimes managed by the configured Rule Engine Server. See Configure the report generation for the Rule Engine Server.

Sentinel monitoring

There is a section named Sentinel monitoring for configuring the Sentinel monitoring for the Rule Engine using the Rule Engine Server.

To enable the Sentinel monitoring, the administrator must register the Sentinel instance he wants to use as an external component. For details, see Manage external components.

The following parameters can be set for Sentinel monitoring:

  • Monitor Rule Engine RDJRAZ command – Activates the monitoring of the RDJRAZ command. When enabled, the Rule Engine sends the operation reports to Sentinel to allow RAZ monitoring.
  • Possible values: Yes, No
  • Default value: No. If the Sentinel monitoring is enabled, the default value is Yes.
  • Monitor Rule Engine RDJMAJ command – Activates the monitoring of the RDJMAJ command. When it is enabled, Rule Engine sends the operation reports to Sentinel to allow MAJ monitoring
  • Possible values: Yes, No
  • Default value: No. If the Sentinel monitoring is enabled, the default value is Yes.
  • Monitor Rule Engine session – Activates the monitoring of the Rule Engine session. When it is enabled, Rule Engine sends the operation reports to Sentinel to allow the session monitoring.
  • Possible values: Yes, No
  • Default value: No. If the Sentinel monitoring is enabled, the default value is Yes.
  • Monitor Rule Engine Business Output Event – Activates the business monitoring. When it is enabled, Rule Engine sends the business data to Sentinel
  • Possible values: Yes, No
  • Default value: No. If the Sentinel monitoring is enabled, the default value is Yes.
  •  
  • Configure the report generation for the Rule Engine Server

    The configuration applies to all the runtimes managed by the configured Rule Engine Server.

    If there are rejected input events, a report called Anomaly details is generated and stored in the Rule Engine Server. The report can be accessed using the Administration.

    The parameters used to define the report generation are:

    Property Description Default value Possible values
    Reports format Defines the format of the reports to generate txt txt, pdf, html
    Deployment reports

    Stores the reports that have been generated during the deployment of the configuration .

    • If it is set to No and:
      • the deployment of the Rule Engine configuration is successful, then the reports are removed,
      • the configuration deployment fails, the reports generated are registered in the Rule Engine Server and can be accessed using the Administration.
    • If this parameter is set to Yes, the reports are registered in the Rule Engine Server and can be accessed using the Administration.

    The list of the deployment reports is:

    • Error Configuration
    • Table configuration Error
    • Internal Tables Check
    • Rules compilation
    • Compilation Errors
    • Cdeployment Log
    • Configuration file detail
    • Internal Settings list
    • Internal Settings list
    No Yes, No
    Redirected Ievents

    Activates the redirected Input Events report

    If this parameter is enabled and there are redirected Input Events, a report named Redirected Ievents is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Transformation Detail

    Activates the Transformation detail report per Input Event .

    If this parameter is enabled, a report named Transformation Detail is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Transformation Statistics

    Activates the Transformation statistics report.

    If this parameter is enabled, a report named Transformation Statistics is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    IEvent aggregation statistics

    Activates the Input Event Aggregation report.

    If this parameter and the aggregation are enabled for input events, and if the Rule Engine configuration contains aggregation rules for input events, a report named IEvents aggregation statistics is generated and registered in the Rule Engine Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    OEvent aggregation statistics

    Activates the Output Event Aggregation report.

    If this parameter and the aggregation are enabled for input events, and if the Rule Engine configuration contains aggregation rules for output events, a report named OEvents aggregation statistics is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Accounting Journal

    Activates the Accounting Journal.

    If this parameter and the Accounting processing option are enabled, a report named Accounting Journal is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Compensation Journal

    Activates the Compensation Output Events generation report.

    If this parameter, as well as the Accounting processing and the Compensation options are enabled, a report named Compensation Journal is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Statistics per Rule

    Activates the Transformation statistics report per rule.

    If this parameter is enabled, a report named Statistics per rule is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Accounting OEvent aggregation

    Activates the Accounting Output Event aggregation details report.

    If this parameter and the aggregation are enabled for output events, and if the Rule Engine configuration contains aggregation rules for output events, a report named Accounting OEvent aggregation is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    OEvent aggregation

    Activates the Output Event aggregation details report.

    If this parameter and the aggregation are enabled for output events, and if the Rule Engine configuration contains aggregation rules for output events, a report named OEvent aggregation is generated and registered in the Report Server.

    The report can be accessed using the Administration.

    Yes Yes, No
    Note   The reports are stored in the Report Server only when the Rule Engine Server is orchestrated by the Event Processor. All these settings are used only when the Rule Engine Server is used with the Event Processor.
    Note   The Rule Engine log is also registered in the Report Server and can be accessed in Administration. Its format cannot be configured and is always txt regardless of the format chosen for the reports.

    Related Links