- The FxhStandardsProcessing node checks whether the result location
of the message to be processed contains the element
ComIbmDni.MsgStandardInfo.Domain.
If this element contains the value DNIUNPARSABLE, the node performs
no further processing and propagates the message on the failure terminal.
- The FxhStandardsProcessing node checks the information from the
request folder in LocalEnvironment. If no request data is available,
the corresponding node property values are used.
- If transformation or validation is to be
done, the FxhStandardsProcessing node determines which message definition
set is to be used:
- If the
<ResultLocation>.ComIbmDni.MsgStandardInfo.DefinitionSet element
is specified, the message definition set it specifies is used.
- Otherwise, the domain that is specified by the
<ResultLocation>.ComIbmDni.MsgStandardInfo.Domain element is searched for the most
recently activated message definition set that corresponds to the message type of the input message.
- If transformation or validation is to be done, the FxhStandardsProcessing node uses the message type that
is specified for the message to determine which message definition is to be used.
- If validation is to be done, the FxhStandardsProcessing node validates
the message according to the message definition set determined in
step 3.
- If transformation is to be done, the FxhStandardsProcessing node
determines the representation type of the input message:
- If the message body is provided by the
Root.XMLNSC element,
the FxhStandardsProcessing node assumes that the message is an MTXML
message.
- If the message body is provided by the
Root.BLOB.BLOB element,
the FxhStandardsProcessing node checks the first character of the
body of the input message:
- If it is a left angle bracket (<), the message is assumed to
be an MTXML message.
- Otherwise, the message is assumed to be an MTFIN message.
The following tables describe how the consequences of the transformation processing depend on initial
conditions.
Table 1. Transform MTFIN to MTXML
(transformation mode 1)
| Conditions |
Root subelement that contains the body of the input message. |
.BLOB.BLOB |
.XMLNSC |
| Parser that is used for the input message. |
(none) |
XMLNSC |
| Representation type of the body of the input message. |
MTFIN |
MTXML |
MTXML |
| Consequences |
The input message is transformed. |
X |
|
|
| Transformation is not possible; an exception is not thrown. |
|
X |
X |
| Root subelement that contains the body of the output message. |
.XMLNSC |
.XMLNSC |
.XMLNSC |
| Representation type of the body of the output message. |
MTXML |
MTXML |
MTXML |
Table 2. Transform MTXML to MTFIN
(transformation mode 2)
| Conditions |
Root subelement that contains the body of the input message. |
.BLOB.BLOB |
.XMLNSC |
| Parser that is used for the input message. |
(none) |
XMLNSC |
| Representation type of the body of the input message. |
MTFIN |
MTXML |
MTXML |
| Consequences |
The input message is transformed. |
|
X |
X |
| Transformation is not possible; an exception is not thrown. |
X |
|
|
| Root subelement that contains the body of the output message. |
.BLOB.BLOB |
.BLOB.BLOB |
.BLOB.BLOB |
| Representation type of the body of the output message. |
MTFIN |
MTFIN |
MTFIN |