XMLTransformation node

Use the XMLTransformation node to transform an XML message to another form of XML message, according to the rules provided by an XSL (Extensible Stylesheet Language) style sheet.

This topic contains the following sections:

Purpose

You can specify the location of the style sheet to apply to this transformation in three ways:

  • Use the content of the XML data within the message itself to transform the message according to a style sheet that the message itself defines.
  • Set a value within the LocalEnvironment folder. You must set this value in a node that precedes the XMLTransformation node (for example, a Compute node). You can therefore use a variety of inputs to determine which style sheet to use for this message, such as the content of the message data, or a value in a database.
  • Use node properties to ensure that the transformation that is defined by this single style sheet is applied to every message that is processed by this node.

An XSLT (Extensible Stylesheet Language for Transformations) compiler is used for the transformation if the style sheet is not embedded within the message, and the node cache level (node property Stylesheet Cache Level) is greater than zero. If the XSLT is cached, the performance is improved because the XSLT is not parsed every time it is used.

If the prologue of the input message body contains an XML encoding declaration, the XMLTransformation node ignores the encoding, and always uses the CodedCharSetId in the message property folder to decode the message.

The XMLTransformation node is contained in the Transformation drawer of the palette, and is represented in the workbench by the following icon:

XMLTransformation node icon

Using this node in a message flow

For an example of how to use this node, consider two news organizations that exchange information on a regular basis. One might be a television station, the other a newspaper. Although the information is similar, the vocabulary that is used by the two is different. This node can transform one format to the other by applying the rules of the specified style sheet. If you specify the style sheet in the message (either the XML data or the LocalEnvironment), the same node can perform both transformations.

Look at the following sample for more details about how to use the XMLTransformation node: You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.

Be aware of the following considerations if the input to the XMLTransformation node is generated from the XMLNSC parser or the MRM parser. The XMLNSC parser discards certain information in XML documents, such as processing instructions and comments, if you do not set properties to retain this information in a preceding node. To ensure that the XMLTransformation node transforms the message correctly, set the Retain mixed content, Retain comments, and Retain processing instructions properties correctly on the preceding node (for example, an MQInput node). The MRM parser also discards this information, but you cannot retain information for this parser, therefore avoid using the MRM domain if such information is vital to your transformation.

Deployed and non-deployed style sheets

You can use style sheets in two different ways with the XMLTransformation node:
Deployed style sheets
Deployed style sheets are style sheets that you import into a broker archive (BAR) file and deploy to target systems. Deployed style sheets are managed by the broker. A principal style sheet is the root style sheet that is referenced in a message flow; for example, a reference to a principal style sheet in the Eclipse workspace, C:\\project1\a\b.xsl must be specified as a/b.xsl (or ./a/b.xsl). A principal style sheet can reference (include or import) its descendent style sheets.
Non-deployed style sheets
Non-deployed style sheets are style sheets that you store in a location where the XMLTransformation node can access them. Non-deployed style sheets are not managed by the broker.
For more information, see Migrating style sheets and XML files.

Deployment of deployed style sheets or XML files

Before you can configure the XMLTransformation node, you must understand how to work with style sheets. A style sheet can refer to both another XML file and a style sheet. To use deployed style sheets or XML files:
  1. Make sure that the files have the correct file name extensions.

    Style sheets that are to be deployed must have either .xsl or .xslt as their file extension, and XML files to be deployed must have .xml as their file extension.

  2. Import the files into the Eclipse workspace.

    Import into an Eclipse workspace project all style sheets and XML files that are to be deployed. Put location-dependent descendant style sheets, or XML files that are to be deployed, in the correct directory structure relative to their parent style sheets. Do not put in the Eclipse workspace location-dependent descendants that you do not want to deploy.

  3. Make sure that all references to the files are relative.

    Typically, all references to a deployed style sheet must be made relative, no matter where they are displayed. A reference to a principal style sheet must be made relative to the root of the relevant Eclipse workspace project.

    The only exception is when you specify a principal style sheet as the Stylesheet name property on an XMLTransformation node; you can use an absolute path that points to the correct directory structure in the Eclipse workspace. If the principal style sheet is found, the system resets the node property automatically to the correct relative value.

    The system also performs an automatic deployment of the principal style sheet, together with all of its location-dependent descendant style sheets that are available in the relevant Eclipse workspace project. All references to the location-dependent descendant style sheets (or XML files) of a principal style sheet must be made relative to the location of their parent style sheets. For example, if style sheet //project1/a/b.xsl references style sheet //project1/a/c/d.xsl, the reference must be changed to c/d.xsl (or ./c/d.xsl).

  4. Handle non-deployed child style sheets or XML files.

    Start of changeStyle sheets can refer to other style sheets. If you have a relatively-referenced child style sheet (or XML file) that is not to be deployed, yet its parent is, make sure that the child style sheet is placed in the correct location under workpath/XSL/external (workpath/XML/external), where workpath is the full path to the working directory of the broker. You can use the MQSI_WORKPATH environment variable to find the location of the workpath on your system; for example, on Windows® systems, the default workpath is MQSI_WORKPATH=C:\Documents and Settings\All Users\Application Data\IBM\MQSI.End of change

    A broker automatically associates the execution group deployed storage tree, workpath/XSL/external, and workpath/XML/external tree, together. Therefore if, for example, the document b/c.xml is not found in the broker's deployed storage, the broker automatically searches for a reference to it in the workpath/XML/external/a/b directory in the deployed principal style sheet a/style.xsl. Relative path references must also be used for files that have been deployed but which are not available in the workspace.

  5. Deploy the files.

    Deploy manually only those style sheets or XML files that are not picked up by the system (the Message Brokers Toolkit provides warnings about these files). If you click Browse for the node, or provide the full path of the location of the style sheet in the Eclipse workspace, the style sheet is included automatically in the BAR file.

    To deploy manually, add the files to be deployed to a broker archive. For more information, see Adding files to a broker archive and Adding keywords to XSL style sheets.

    For every execution group that uses the XMLTransformation node, perform one of the following actions:
    • Include the style sheet in the workpath/XSL/external directory on the broker; do not include the style sheet in the BAR file.

      If a style sheet in the workpath/XSL/external directory shares the same path and name with a deployed style sheet, the deployed style sheet is used.

    • Include the style sheet in the BAR file and deploy the BAR file. If multiple BAR files include the same style sheet name, the style sheet from the last BAR file that was deployed is used.
    • Deploy the style sheet in its own BAR file. If the BAR files use XMLTransformation nodes, but do not include the style sheet, the Message Brokers Toolkit issues warning messages.

Configuring the XMLTransformation node

When you have put an instance of the XMLTransformation node into a message flow, you can configure it; see Configuring a message flow node. The properties of the node are displayed in the Properties view. To display the properties of the node in the Properties dialog, right-click the node and click Properties. (If you double-click the XMLTransformation node, you open the XSL Selection dialog box.)

All mandatory properties for which you must enter a value (those that do not have a default value defined) are marked with an asterisk.

Configure the XMLTransformation node:

  1. Optional: On the Description tab, enter a Short description, a Long description, or both. You can also rename the node on this tab.
  2. On the Stylesheet tab, to specify a style sheet using node properties, enter the required value for Stylesheet name. This value is ignored if style sheet information is found in a preferred location (determined by the selection priority values that you have set).
    Specify a principal style sheet using one of the following methods:
    • Click Browse next to Stylesheet name. The identified principal style sheet and all its relatively-referenced descendant style sheets are added automatically to the BAR file when you add a message flow to a BAR file (if both they and their parent style sheets are available).
    • To identify an already deployed, or ready to be deployed, style sheet, use the Stylesheet name property, and leave the Stylesheet directory property blank.
    • In the Message Flow editor, drag an .xslt file onto the XMLTransformation node; the Stylesheet name is set automatically.
  3. On the Advanced subtab:
    1. If the style sheet identification is fully qualified, Stylesheet directory is ignored; otherwise, the value that you set in this property is added to the beginning of the specification, regardless of where it is found.
    2. In Stylesheet cache level, specify the number of compiled or parsed style sheets that are stored in this instance of the node; the default value is 5. The style sheet cache is retained for the life of the node, and is cleared when the node is deleted from the flow, when the flow is deleted, or when the execution group is stopped.

      If you change a cached style sheet (by redeploying or replacing the file in the file system), the XMLTransformation node that is holding the cache replaces the cached version with the modified (latest) version before a new message is processed. However, if you are changing several style sheets, stop relevant message flows before you make any changes. If you do not stop the relevant message flows before you make the changes, the order of the changes cannot be guaranteed by running message flows, which might cause an incompatibility between the style sheets that are changed. Use the mqsireload command to reload a style sheet; however, this command does not prevent incompatibility.

    3. Select values for the XML embedded stylesheet selection priority, Message environment selection priority, and Broker node attribute selection priority properties. The values that you set determine the order in which alternative locations are searched for the style sheet information. The highest priority setting is 1. The default order is:
      1. XML embedded stylesheet selection priority, which has a default value of 1. The node searches the message XML data for style sheet location information. For example, the XML data might contain:
        <?xml-stylesheet type="text/xsl" href="foo.xsl"?>
      2. Message environment selection priority, which has a default value of 2. The node searches the LocalEnvironment that is associated with the current message for the style sheet information that is stored in an element called ComIbmXslXmltStylesheetname.

        This node was available in a SupportPac™ for Version 2.1, and element ComIbmXslMqsiStylesheetname was used for the name of the style sheet, therefore, the current node checks both elements. If both are present, the value in ComIbmXslXmltStylesheetname takes precedence.

      3. Broker node attribute selection priority, which has a default value of 3. The node uses the Stylesheet name and Stylesheet directory properties to determine the correct values.

      You can set more than one property to the same value, although if you do, the order of priority that is set by the node is the default order that is indicated previously.

      If you set a value of 0, the node does not search the corresponding location for the style sheet identification. If you set all three properties to 0, a runtime error is generated.

  4. On the Output Character Set tab, specify the order in which the node searches valid locations to find the character set to use for the output message. The highest priority setting is 1. The default order is:
    1. Message environment selection priority, which has a default value of 1. The node searches the LocalEnvironment that is associated with the current message for the character set information that is stored in an element called ComIbmXslXmltOutputcharset; for example, to encode the output of the transformation as UTF-8, enter the value 1208 as a string in this element.

      This node was available in a SupportPac for Version 2.1, and element ComIbmXslMqsiOutputcharset was used for the output character set, therefore, the current node checks both elements. If both are present, the value in ComIbmXslXmltOutputcharset takes precedence.

    2. Broker node attribute selection priority, which has a default value of 2. The node uses the property Output character set to determine the correct value.

      If you set a value for Output character set, the value that you enter must be numeric; for example, to encode the output of the transformation as UTF-16, enter 1200.

    You can set more than one property to the same value, although if you do, the order of priority that is set by the node is the default order that is indicated previously.

    If you set a value of zero, the node does not search the corresponding location for the character set identification.

    If the node cannot determine the output character set from either of these two sources, either because no value is set, or because the selection priorities are set to zero, the default value 1208 (UTF-8) is used. (The XSL specification indicates that the output character set can be specified in the style sheet; however, the XMLTransformation node ignores this value.)

  5. On the Detail Trace tab, set the Trace setting property to trace the actions of the XMLTransformation node. The default value is Off. To activate trace, set the property to On.

    The trace information is written to a trace file XMLTTrace.log:

    • z/OS platform On z/OS® systems, the file is located in install_dir/output, where install_dir is the directory in which you have installed the broker.
    • Windows platform On Windows systems, if you set the workpath using the -w parameter of the mqsicreatebroker command, the location is workpath\log. If you have not specified the broker workpath, the location is C:\Documents and Settings\All Users\Application Data\IBM\MQSI\common\log.
    • Linux platformUNIX platform On Linux® and UNIX® systems, the file is located in /var/mqsi/common/log.

    If you set Trace setting to On for one XMLTransformation node, it is on for all of the nodes in the execution group.

    This property is deprecated. Start user trace instead. The user trace contains the same XML trace information. If you set Trace setting in the XMLTransformation node, it does not affect user trace.

If you have large XML messages and receive an out of memory error, use the mqsireportproperties command to see the current value of the Java™ Heap size for the XSLT engine:
mqsireportproperties brokerName -e executionGroupLabel 
                                 -o ComIbmJVMManager -n jvmMaxHeapSize
Use the mqsichangeproperties command to increase the Java Heap size:
mqsichangeproperties brokerName -e executionGroupLabel 
                                 -o ComIbmJVMManager -n jvmMaxHeapSize -v newSize
In the previous examples, replace brokerName, executionGroupLabel, and newSize with the appropriate values.

The value that you choose for newSize depends on the amount of physical memory that your computer has, and how much you are using Java. A value in the range 512 MB (536870912) to 1 GB (1073741824) is typically sufficient.

Terminals and properties

The XMLTransformation node terminals are described in the following table.

Terminal Description
In The input terminal that accepts the message for processing by the node.
Failure The output terminal to which the original message is routed if an error is detected during transformation.
Out The output terminal to which the successfully transformed message is routed.

The following tables describe the node properties. The column headed M indicates whether the property is mandatory (marked with an asterisk if you must enter a value when no default is defined); the column headed C indicates whether the property is configurable (you can change the value when you add the message flow to the BAR file to deploy it).

The XMLTransformation node Description properties are described in the following table.

Property M C Default Description
Node name No No The node type The name of the node.
Short description No No   A brief description of the node.
Long description No No   Text that describes the purpose of the node in the message flow.

The XMLTransformation node Stylesheet properties are described in the following table.

Property M C Default Description
Stylesheet name No Yes   The name of the style sheet, used if the style sheet specification is searched for in node properties.

The XMLTransformation node Advanced properties are described in the following table.

Property M C Default Description
Stylesheet directory No Yes   The path where the style sheet is located. This path is used by all location methods.
Stylesheet cache level No No 5 The number of compiled or parsed style sheets that are stored in this instance of the node.

Enter a positive integer between zero (0) and 100. The default value is 5. If you set this property to a character other than a positive integer, a flow configuration exception error message is issued.

If you set this property to zero (0), no style sheet is cached, and style sheets are interpreted rather than compiled.

XML embedded stylesheet selection priority Yes No 1 The priority value for searching for style sheet location information in the XML data.
Message environment selection priority Yes No 2 The priority value for searching for style sheet location information in the LocalEnvironment folder of the current message.
Broker node attribute selection priority Yes No 3 The priority value for searching for style sheet location information as a property of the node

The XMLTransformation node Output Character Set properties are described in the following table.

Property M C Default Description
Output character set No No   The numeric value of the Output character set
Message environment selection priority Yes No 1 The priority value for searching for the Output Character Set ID in the LocalEnvironment folder of the current message.
Broker node attribute selection priority Yes No 2 The priority value for searching for the Output Character Set ID as a property of the node.

The XMLTransformation node Detail Trace properties are described in the following table.

Property M C Default Description
Trace setting Yes No Off Start of changeThis property is deprecated. Start user trace instead. The user trace contains the same XSL trace information. If you set this property, it does not affect user trace.

In previous versions of WebSphere® Message Broker, this property controls whether tracing is on or off. If tracing is on, low level tracing is recorded in a file.

End of change
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:20:20

ac12490_