After deployment:

This topic contains advice for dealing with some common problems that can arise when deploying message flows or message sets.

You are not notified of the result of a deploy

You do not receive confirmation that the deployment was successful

You cannot see any deployed message flows or message sets

A deleted broker remains in the domains navigator

Your XMLTransformation node does not work after deployment

There are two scenarios that explain why your XMLTransformation node might not work after deployment:

Error messages are displayed indicating that the style sheets were not found

You get unexpected transformation results.

  • Scenario: You get unexpected transformation results.
  • Explanation: For complex message flows, incompatibility might arise among style sheets and XML files after a deployment. There are two likely reasons for this:
    • Only part of the cooperating style sheets or XML files are deployed and updated (this might be caused by a file system failure).
    • Multiple XMLT nodes that are running inside the same execution group are supposed to use compatible style sheets, but are using different versions to process the same incoming message.
  • Solution: If only part of the cooperating style sheets or XML files are deployed and updated, resolve any incompatibility by redeploying the compatible versions. To avoid multiple XMLT nodes using different versions of the style sheet, pause relevant message flows in the target execution group before performing the deployment, then restart the flows.
Related concepts
Deployment overview