WebSphere Message Broker, Version 8.0.0.7
Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS
See information about the latest product version
See information about the latest product version
Resolving problems that occur when preparing to deploy message flows
Use the advice given here to help you to resolve common problems that can occur during preparations to deploy message flows or message sets.
An error is issued when you add a message set to a broker archive file
- Scenario: An error is issued when you add a message set to a broker archive (BAR) file.
- Explanation: After you create a BAR file and add a message set project to it, two files are created in the BAR file: messageset.user.txt and messageset.service.txt. The user.txt file contains user log information, such as warning message BIP0177W, which states that the dictionary that you have created is not compatible with earlier versions.
- Solution: Use the information in the user.txt file to diagnose the error. The service.txt file contains detailed information that is used by the broker, and can be used by the IBM® Support Center to diagnose problems.
You cannot drag a broker archive file to a broker
- Scenario: You cannot drag a broker archive (BAR) file to a broker.
- Explanation: BAR files can be deployed only on an execution group.
- Solution: Select an execution group in the deploy dialog.
You cannot deploy a message flow that uses a user-defined message flow
- Scenario: You have created a message flow that contains an input node in a user-defined node project. However, you cannot deploy a message flow that uses this node.
- Explanation: Validation, compilation, and deployment do not recognize that a user-defined message flow contains an input node.
- Solution: To work around the problem, add a dummy input node to the flow that you intend to deploy.