This topic tells you what to be aware of when migrating a message
flow containing XMLTransformation nodes
Prior to Version 6.1,
the XSLTransform node was known
as the XMLTransformation node. When you migrate a flow containing XMLTransformation
nodes to Version 6.1, consider the following
enhancements:
- You can no longer set the style sheet search and character set information
search priorities in the node properties in the workbench.
The following fixed search priorities are adopted. However, search priorities
set on existing flows are still respected.
- The node searches for the name of the style sheet to be used by interrogating,
in the following order:
- The input message. The node searches the message XML data for stylesheet
location information. For example, the XML data might contain:
<?xml-stylesheet type="text/xsl" href="foo.xsl"?>
and
"foo.xsl" would then be used as the stylesheet name.
- The LocalEnvironment. If no stylesheet name is found in the input message,
the node searches the LocalEnvironment associated with the current message
for stylesheet information stored in an element called XSL.StyleSheetName.
This
node was available in versions prior to Version 6.1 (when
it was known as the XMLTransformation node), and element ComIbmXslXmltStylesheetname
was used for the name of the style sheet, so the current node checks both
elements. If both are present, the value in XSL.StyleSheetName takes precedence.
- The node's properties. If no stylesheet name is found in the input message
or LocalEnvironment, the node uses the Stylesheet
Name and Stylesheet Directory properties
to determine the correct values.
- The node searches for the character set to use for the output message
by interrogating, in the following order:
- The LocalEnvironment. The node searches the LocalEnvironment associated
with the current message for character set information stored in an element
called XSL.OutputCharSet; for example, to encode the output of the transformation
as UTF-16, enter the value 1200 as
a string in this element.
This node was available in versions prior to Version 6.1 (when it was known as the XMLTransformation
node), and element ComIbmXslXmltOutputcharset was used for the output character
set, so the current node checks both elements. If both are present, the value
in XSL.OutputCharSet takes precedence.
- The node's properties. If no character set information is found in the
LocalEnvironment, the node uses the Output
Character Set property to determine the correct value.
If the node cannot determine the output character set from either of
these two sources, either because no value is set or the selection priorities
are set to zero, the default value of
1208 (UTF-8)
is used.
- You can set additional node properties for message domain. message set,
message type, and message format. If you have included a ResetContentDescriptor node
to set these values before passing the message to the XSLTransform node,
you can now optimize the message flow by removing the ResetContentDescriptor node.