Configure Rule Engine Server

For managing the runtimes, Rule Engine Server uses the AccountingIntegrator configuration information stored in Repository. For how to store the AccountingIntegrator configuration deployed from Composer into Repository, see Manage Rule Engine configurations with the Repository.

The user must deploy this configuration to an AccountingIntegratorRepository Axway Server type from Composer.

The AccountingIntegrator configurations stored in Repository are uniquely identified by an application name and a configuration identifier. For this reason, to process a file, the user must provide the needed information for identifying the AccountingIntegrator configuration:

  • The configuration identifier
  • The application name

For configuring the newly created runtime, Rule Engine Server performs the following tasks:

  1. Takes the ctx and mvt files from Repository
  2. Puts the files into the runtime/dat folder
  3. Calls the commands rdjraz and rdjdep.
  4. Automatically generates the script.fic file.
Note   The user must provide the name of the Processing Context In needed in script.fic as the Collection Type name.

After the runtime is configured with success, Rule Engine Servercalls the rdjexp command on runtime to process the file. Rule Engine puts the results of the transformation into a timestamped folder under the folder …/RuleServer/extra/workDirectory/output/. This folder is configured in script.fic by Rule Engine Server.

After executing rdjexp, it calls the rdjreport command to generate the reports.

Parameters to configure in script.fic

The following parameters can be configured in script.fic file:

  • SESSION
  • DATE_OPERATION
  • STAMPER
  • Environment_Transformation

The user can also use INSERT to configure other parameters in script.fic.

For information on how to specify these parameters in an Event Processor operation, see the Rule Engine Server processFileEvent operation description in Functions.

The following reports parameters from script.fic can be configured from Administration:

  • PRINT_REDIRECTION_IEvent
  • PRINT_DETAIL_TRANSFORMATION
  • PRINT_TRANSFORMATION_REPORT
  • Print_Report_Aggregation_IEvent
  • Print_Report_Aggregation_OSegt
  • PRINT_LOG_ACCOUNT
  • PRINT_LOG_COMPENSATION
  • Print_Report_Rule_Counter
  • Print_Report_Agreg_Account
  • Print_Detail_Agreg_IEvent

For how to configure the Rule Engine reports with Rule Engine Server, see Configure the report generation for the Rule Engine Server.

Configure the Processing-Context-In name

For starting a transformation session,the user must specify also the Collection Type name for Rule Engine Server to configure the Processing-Context-In name in script.fic. For this, he must:

  1. Use the Financial export option to export the same configuration deployed from Composer as ctx.mvt and mvt.mvt
  2. Import the configuration into Designer after this is transformed using the transformConfiguration command.
  3. The Designer configuration must be deployed in Repository into the application linked to Rule Engine Server (by default, the default application).
  • Related Links