Set up the transformation environment

Session environments and domains

The session environments and domains allow you to spread the various processing phases across different executions (for example, daily, monthly, quarterly or annual processing)

The session environment activates one or more domains.

Each domain, when activated, executes the Transformation-Phases associated with it.

The session environment is activated in script.ges. If no session environment is specified and only one is defined in the usr.dat file, the Rule Engine runs in the environment defined in the usr.dat file.

Keyword Description/Values
>Configuration< Section



The name of the session environment activated by the session

The domains activated by the environment must be supplied in usr.dat. Configure the domains in Axway Composer.

Keyword Description/Values


BATCH;DOM1            ;III.

BATCH;DOM2            ;JJJ.

Rules to follow:

Rule Meaning


Environment: Required parameter

Specifies the name of the session environment


Domain: Required parameter

Specifies the domain that is activated by the associated environment
If several domains are activated by the same environment, supply a line for each domain


Processing-Context-Out. See Implement redirection



The semi-colon ( ; ) is the required delimiter


End each line with a period ( . )

Implement redirection

Redirection copies the processed Input-Event to one or more outputs.

The Input-Event is only redirected if ALL phases of the current processing are completed successfully. If the Input-Event is placed in anomaly or rejected, the redirection is canceled for the Input-Event concerned.

If exits are enabled, it is the Input-Event as modified by the exits that is redirected.
The only exception to this is the exit applied to enrich the event before the application of a Transformation-Rule.

For example, an Input-Event that is processed in real time at the bank counter must be processed for other applications during the overnight batch run.  This means that a copy must be made after the real-time processing.

Redirection is enabled through sys.dat, usr.dat and script.ges.

Parameter settings in sys.dat:

Keyword Description / Values
>Choice< Section



Parameter settings in usr.dat:

Keyword Description/Values
Section >Environment_Transformation<




Rules to follow:

Rule Meaning


Processing-Context-Out: Required parameter if redirection is enabled

Specifies the logical name of the exchange zone that is to receive the redirected Input-Event

If you do not specify a Processing-Context-Out for the redirected Input-Event, redirection does not take place
You can specify more than one Processing-Context-Out for redirected events
Specify each Processing-Context-Out on a separate line


The semi-colon ( ; ) is the required delimiter


End each line with a period ( . )

Parameter settings in script.ges:

Keyword Description/Values
>Script.Ges< Section

IEvent_Redirected (Processing-Context-Out)

The name of the exchange zone to which the redirected Input-Events are written

If you have specified more than one Processing-Context-Out for redirected events, define an exchange zone for each output


The file containing the data for the report on the redirections that have been effected

Related Links