Migration of style sheets and XML files

If you do not intend to use the new deployment feature, and your XMLTransformation 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 XMLTransformation nodes reference style sheets with fully-qualified paths (absolute referencing), migration is not necessary.

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

In Version 2.1 and 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 Version 6.0, any relative references to manually-deployed style sheets are relative to the directory broker work path/{XSL,XML}/external on the broker file system. This means that you must 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.

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

Related tasks
Adding files to a broker archive
Renaming objects that are deployed to execution groups