AccountingIntegrator Enabler Rule Engine: Parameters tab

Field Contents

 Rule Engine Parameters

Parameters required to determine the location of the operating environment and the AccountingIntegrator Enabler  Rule Engine installation environment.

Server version


Specify the Accounting Integrator  Rule Engine product version to use.

Possible versions are:

  • 2.2.x
  • 2.1.x
  • 2.0.x
  • 1.6.x
  • 1.5.x
  • 1.4.x
  • 1.3.x

From the Enabler version onwards, this field insures backward compatibility with previous  Rule Engine versions.

The ctx and mvt files will have to comply with the version of the server that you have selected.For example, if the deploy is made from a 1.6.x version of the Enabler to a 1.5.x  Rule Engine version only the 1.5.x compatible features will be accepted when the broadcast files are generated.

If you try to use features that are not supported in a server of a lower version, the Accounting Integration  Rule Engine will throw an exception.

For instance, for a server version inferior to 1.6.x, if you set the length of the numeric fields to 28 (maximum length accepted since 1.6.x), the manager will throw an error because in these versions the maximum length for numeric zones was 18. The same will happen for decimal field management that is available only starting with 2.0.x  Rule Engine versions.

Operating Path [RDJ_EXEC]


Specify the full file path of the AccountingIntegrator Enabler  Rule Engine operating directory.

In practice, Send to Production commands are not sent directly to AccountingIntegrator Enabler  Rule Engine, but instead to the Broadcast Agent you specified in the Agent Path field. You must then retrieve them and transfer them manually to AccountingIntegrator Enabler  Rule Engine.

It is therefore recommended that you enter the same path as for the Agent Path field.

Installation Path



Specify the full file path of the AccountingIntegrator Enabler  Rule Engine installation directory.

 Rule Engine Host Parameters

Parameters required to open a working session on the machine where AccountingIntegrator Enabler  Rule Engine is installed.

You can install AccountingIntegrator Enabler  Rule Engine on either of the following:

  • A separate machine to the one where you installed the Broadcast Agent
  • The same machine as the Broadcast Agent, but with a separate user account

Remote installation

Select this to indicate that AccountingIntegrator Enabler  Rule Engine and the Agent are not installed on the same physical machine.

The Broadcast Agent then passes the Host name specified in the Axway AccountingIntegrator Enabler Server object as a parameter in the scripts.

When AccountingIntegrator Enabler  Rule Engine and the Broadcast Agent are on the same physical machine, the Broadcast Agent uses the localhost value in the scripts.

Remote user name

Enter the user name and password for accessing the Remote  Rule Engine.

Remote user  password

Agent Parameters

Parameters required to specify the location of the processing environment of the Agent associated with the Axway Server. The system sends the configuration files  mvt.mvt and ctx.mvt to this processing environment.


directory path


Enter the path to the Agent directory in which the system stores the mvt.mvt and ctx.mvt files to create the processing environment for the given Axway Server managed by the Agent.

User parameters

Specify your own set of parameters required for running the scripts. Separate each parameter with a semicolon (;) in the format:

-D<variable name>=<value>

Example: -DUPDATE_RM=1 assigns the value 1 to the UPDATE_RM parameter.

The system automatically loads the variable with the given value when the Agent runs the scripts.

Trace Level

Set the log detail you require for recording exchanges between Composer and the Broadcast Agent. Select one of these options:

  • None
    Only displays the messages at the beginning and end of the transaction in addition to any errors encountered.
  • Standard (default)
    Enriches the None information level with details of the objects processed as well as the different execution phases on the end of transaction ANT script.
  • Debug
    Verbose information with precise code details
  • Detailed
    Medium level of detail

Back to top

Related Links