WebSphere Message Brokers
File: au16544_
Writer: Jane Brockbank

Task topic

This build: July 31, 2007 21:39:33

Resolving problems that occur after deployment of message flows:

This topic contains advice for dealing with some common problems that can arise after 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 XSLTransform node does not work after deployment

There are two scenarios that explain why your XSLTransform 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 XSLTransform 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 XSLTransform 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
Notices | Trademarks | Downloads | Library | Support | Feedback

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

au16544_ This topic's URL is: