AccountingIntegrator Enabler Rule Engine Browser

About the  Rule Engine Browser tab

Using the  Rule Engine Browser

About the Rule Engine Browser

The  Rule Engine Browser enables you to:

  • Simulate Test Case exchanges
  • Perform Test Cases
  • Check and modify parameters
  • Check results and specific execution reports
  • Declare files so that they can be viewed and modified

Prerequisites

To use the  Rule Engine Browser, you must:

  • Have the corresponding rights activated:
    • Finance - AxwayAccountingIntegrator Enabler Simulator: File modification
    • Finance - AxwayAccountingIntegrator Enabler Server: File modification 
  • Be familiar with the product and have a good understanding of Windows or UNIX

Before you start, ensure that you have:

  • Entered complete path names in the Parameters tab for the:
  •  Rule Engine directories ([RDJ_EXEC] and [RDJ_HOME])
  • Broadcast Agent directory
    •  Rule Engine directories ([RDJ_EXEC] and [RDJ_HOME])
    • Broadcast Agent directory
  • Activated the automatic update option for the  Rule Engine in the User Parameters of the Axway Server -DUPDATE_RM=1
  • Sent the parameter settings to production

About the  Rule Engine Browser tab

Icon bar

Use the icon bar to perform the following tasks:

Icon Function

Perform a simulation

Click this icon.

View or modify a file

Select the file that you want to view, then click this icon.

Declare a file

Click this icon to display the corresponding window and enter the new file name.

 

The file structure

The file structure is divided into 8 categories. Six of these categories are displayed by default, and the remaining two are generated the first time that you execute a simulation (Simulation Report(s)) or that you define a new file (User Files).

The following table lists the categories that are displayed by default. Each category contains one or several files.
For more information on these files, refer to AccountingIntegrator Enabler V1.3 Reference manual.

Category File name Function

Test Cases

IEvent

Test cases for Input Events processing. This file is the same for all users

Parameters

mvt

Update report

 

rchrp

Resource file used by the rdjrch procedure

 

ref

Technical context parameters

 

script

 Rule Engine execution parameters

 

sys

Functional context parameters

 

tsc

Description of time stamping counters

 

usr

Transformation domain parameters

Sentinel

rdjstn

Sentinel agent configuration

 

trc

Auditing rules and formats

Printout

accntagr

Details of Output Events aggregation

 

cptrg

Rule counter

 

detagrie

Details of Input Events aggregation

 

detano

Details of Translation anomalies

 

detredir

Details of rejected Input Events

 

dettrans

Details of Transformation

 

errmvt

Details of errors when loading parameters file

 

errtra

Rules compilation errors

 

ieagrcn

Input Events aggregation counter

 

osagrcnt

Output Events aggregation counter

 

transcnt

Transformation statistics

Accounting printout

accntlog

Output Events accounting journal

Results

ErrorMsg

Session execution errors

 

IEvent_Anomaly

Anomaly Input Events

 

IEvent_Modified

Modified Input Events

 

IEvent_Rejected

Rejected Input Events

 

IEvent Trace

Trace of Input Events operations

 

OSegtDefault

Default Output Events operations

 

OSegt_Trace

Trace of Output Events toperations

 

Using the Rule Engine Browser

You can use the  Rule Engine Browser to:

Perform a simulation

Note: If you start a simulation using Sentinel, make sure that the Event Router is already running.

To perform a simulation:

  1. Click .
    The execution window opens.
  2. If you want to customize the execution, use the command line to enter one, or several, of the following parameters. These parameters are not positioned and must be separated by a space.

    Syntax:
    file/mqs [session] [ews] [exit]
     
    ParameterDefinition

    file/mqs

    The type of execution (file or MQSeries).

    session

    Request to start Sentinel tracking.

    ews

    Request to update the anomalies file in EWS format.

    exit

    Request to activate exits.

  1. Click OK.
    The execution report appears in the Simulation Report category and is displayed on the screen. If this is the first simulation, the system creates a Simulation Report category. It automatically adds the new file to the file list.
  2. Check the execution and click Cancel to close the file.

After this, you can use the Consultation procedure to view this Report again.

View or modify a file

You can view all files. However, you can only modify files that are defined as modifiable in the RuleManager_fr.txt configuration file.

To view or modify a file:

  1. Select the file from the list displayed on the screen.
  2. Click .
    The Browser opens and displays data.
    The header indicates if the file can be modified or not. For example, the header [Read only: file not modifiable] indicates that the file cannot be modified.
  3. Modify the data if necessary.
  4. Click OK to validate, or Cancel to close the file.

From outside Composer, you can change the modification option that corresponds to a file in the RuleManager_fr.txt file. [FOR DETAILS: Defining a file permanently]
 

Declare a file temporarily

The files that you define here:

  • Are temporary and disappear as soon as you close this window
  • Must be physically located in the operating directory

There is no maximum number of files that you can define.

To declare a new file:

  1. Click .
    The definition window opens, and by default displays:
    [RDJ_EXEC]/dat/IEvent.seq


    Where:
  2. [RDJ_EXEC] corresponds to the operating directory path.
  3. /dat/IEvent.seq corresponds to the Test Cases file path.
  4. Enter the name of the new file after [RDJ_EXEC] and click OK.
    If this is the first time that you created a file in this session, the system creates a category File(s) User(s). It adds the new file to the list of existing files.

Declare a file permanently

To declare a file as a permanent type, you can define it outside of Composer, in the RuleManager_fr.txt file.Use a text editor, for example Notepad, for this task.

To define a file as permanent:

  1. Open the file RuleManager_fr.txt in a text editor.
  2. Copy or repeat a line that already exists in the category where you want to declare the file.

Modify the elements in the new line as needed. These elements are separated by tabs in the file. The most important fields are described in the first four lines of the following table.
 

Field Detail

Category /

Category name

1: Test Cases

2: Parameters

3: Sentinel

4: Printout

5: Account printout

6: Results

Symbol /

Syntax

Symbol that corresponds to each file category

Label

File label that is displayed on the screen

Modification option

0: cannot be modified

1: modifiable can be modified

Path

[RDJ_EXEC]/dat/

File name

Name of the physical file

Icon name

Name of the icon that corresponds with the category or the sub category

Color coding

0: none

1: character string in red

2: 1 +  Rule Engine section in bold

3: 2 + value of the equals in blue

Back to top

Related Links