WebSphere Message Brokers
File: ah35007_
Writer: Pete Seddon

Concept topic

This build: July 31, 2007 21:30:46

Migrating style sheets and XML files from Version 5.0

You might have to make changes to message flows and to the style sheet and XML files that they use when you migrate from Version 5.0 to Version 6.1.

If you do not plan to include the style sheets and XML files with the message flows that use them in the broker archive file that you deploy, and your XSLTransform nodes reference style sheets with partially-qualified paths (relative referencing), you might need to migrate both the message flows and the style sheets. If your XSLTransform nodes reference style sheets with fully-qualified paths (absolute referencing), migration is not necessary.

Note: The XSLTransform node has been renamed in Version 6.1. In Version 5.0 it was called XMLTransformation. The node behavior, properties, and terminals are unchanged. Message flows that include this node do not have to be modified, and can be deployed as they are to Version 6.1 brokers.

You can continue to deploy your style sheets and XML files manually into the broker file systems, but you must store relatively-referenced style sheets and XML files (and their dependants) in the broker work path/{XSL,XML}/external directories.

In Version 5.0, any relative references to manually-deployed style sheets are relative to the location of the file directory where the message broker is started. In later versions, any relative references to manually-deployed style sheets are relative to the directory broker work path/{XSL,XML}/external on the broker file system. You must therefore complete the following actions:
  1. Move the relatively-referenced style sheets (and their descendants), to the correct directory structure under broker work path/{XSL}/external.
  2. Move all their dependent XML files to the correct directory structure under broker work path/{XML}/external.
For example, a relatively-referenced principal style sheet, a/b.xsl, must now be stored as broker work path/{XSL}/external/a/b.xsl on the broker file system. An XML file that is referenced by a/b.xsl as c/d.xml must be stored as broker work path/{XML}/external/a/c/d.xml.

An embedded style sheet is handled in the same way as a file that is loaded from the root of the broker’s deployed storage, therefore move any descendant style sheets or XML files of embedded style sheets to the broker work path/{XSL,XML}/external tree. If you cannot move the files, you can reference them with a fully-qualified path (absolute reference).

Related tasks
Migrating and upgrading
Adding files to a broker archive
Renaming objects that are deployed to execution groups
Related reference
XSLTransform node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:30:46

ah35007_ This topic's URL is: