See information about the latest product version
MQGet node message tree examples
The MQGet node generates message trees based on the input message assembly that it receives, and the options that you have set on the node properties.
The message trees, shown in the following table, are generated according to the rules described in A request-response scenario that uses an MQGet node.
With a message assembly like this: | The message that the MQGet node returns is: |
---|---|
|
|
With the following node property settings: | The resulting output message assembly is: |
---|---|
|
|
|
This tree is effectively the result of doing an assignment from ${resultDataLocation} to ${outputDataLocation}. The value of the source element is copied, as are all children including attributes. |
|
This tree has the MQMD that is used for the MQGET call in the OutputLocalEnvironment, because the input MQ parameters location had an MQMD element under it. Even though the input tree is not copied, the presence of the MQMD element causes the MQMD that is used for the MQGET call to be placed in the output tree. |
|
The value that you set for the Copy Message property makes no difference to the eventual output tree in this case. |