Resolving problems when deploying message flows or message sets
Use the advice given here to help you to resolve common problems that can arise when you deploy message flows or message sets.
Initial checks
Procedure
- To debug problems when deploying, check the following logs:
- The administration log
- The local error log (the Windows Event log or the syslog)
- The WebSphere® MQ logs
These logs might be on separate computers, and must be used with the IBM Integration Toolkit output to ensure that the deployment was successful.
Use the mqsilist command to check that the deployment was successful, or look in the Windows Event or Administration Log view.
- Use this checklist when you have deployment problems:
- Make sure that the mode that your integration node is working in is appropriate for your requirements. See Operation modes.
- Make sure that the client connection to a remote queue manager is running.
- Make sure that channels are running.
- Display the channel status to see if the number of system messages sent increases.
- Check the channel from the remote end.
- Check the queue manager name.
- Determine whether the channel is a cluster channel.
Common problems
About this task
- Resolving problems that occur when preparing to deploy message flows
- Resolving problems that occur during deployment of message flows
-
- You receive a warning message about the mode of your integration node
- The message flow deploys on the test system, but not elsewhere
- Error messages about your integration node mode are issued when you create an integration server
- Error messages about your integration node mode are issued when you deploy
- Error messages about your function level are issued when you deploy
- Error messages are issued when you deploy to z/OS
- Expected serialization of input is not occurring for a shared queue that serves multiple instances of a message flow on z/OS
- You create a configurable service, then deploy a message flow and inbound adapter, but the deployment fails
- Error messages are issued when you deploy
- You get an authority check failure when you deploy to z/OS
- Resolving problems that occur after deployment of message flows