Transformation Extender map and DataPower processing
To use an IBM Sterling Transformation Extender map in a DataPower® processing policy, you must create a binary transform action. The map can use one or more input contexts and can create results in one or more output contexts.
Before you define inputs and outputs, you must first create a DataPower service with a processing policy.
When you create a binary transform action for a Transformation Extender map,
define the following properties.
- ITX map file
- Fully qualified name of the map file.
- Locate named inputs and outputs
- Indicates how the transform determines the input contexts and
the output contexts. The following choices are available.
- Default
- Use the input and output contexts that are defined for the action. This value works when the map defines only one input and only one output. For more information, see Defining a single input and output.
- Explicit
- Use the contexts that are explicitly defined for the action. The input and output contexts that are defined at the action level are ignored. For more information, see Defining multiple inputs and outputs.
- Dynamic (deprecated)
- Use the contexts that are defined dynamically during processing. This deprecated method was for IBM Sterling Transformation Extender Design Studio testing purposes only.
For the XML manager associated with the DataPower service, edit its configuration to enable the Support ITX Warnings property. When enabled, the DataPower Gateway supports this feature. When the map file defines warnings and a warning is met, the DataPower Gateway returns a warning and sets it to the var://service/multistep/tx-warn variable and continues processing.