Resolving problems that occur when preparing to deploy message flows
This topic contains advice for dealing
with some common problems that can arise when preparing to deploy message
flows or message sets.
Migrated message flows are not available to add to a broker archive
file
- Scenario: You have migrated your Version 5.0 message
flows and message sets into the workbench using mqsimigratemsgflows and mqsimigratemsgsets commands,
but the message flows are not available to add to a broker archive (bar) file.
- Solution: Migrated message flows and message
sets are displayed in the workbench as
a closed project. To make the message flows and message sets available
to be added to a bar file:
- Open the project by right-clicking it and clicking
- Clean the project by right-clicking it and clicking Clean.
This shows any errors, and makes the project resources available to be added
to a bar file.
An error is issued when you add a dictionary to a broker archive file
- Scenario: An error is issued when you add a dictionary 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 versions prior to WebSphere Message Broker Version 6.0.
- Solution: Use the information in the user.txt file
to diagnose the error. The service.txt file contains
rudimentary dictionary information as 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. When you use drag and drop, you cannot drop the bar file onto a broker
in the Broker Topology editor or in the Domains navigator.
- Solution: Drop the bar file onto an execution group in the
Domains navigator, or 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 plug-in message flow.
- 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.
The compiled message flow file (.cmf) has not
been generated
- Scenario: The compiled message flow file (.cmf)
has not been generated. Therefore, it is not added to the broker archive file
and cannot be deployed.
- Explanation: When you create mapping files, the overall
file path length must not exceed 256 characters, due to a Windows file system
limitation. If you try to add a message flow to a BAR file with mapping or
ESQL files, that have a path length that exceeds 256 characters, the compiled
message flow is not generated and cannot be deployed.
- Solution: To ensure that the path length does not exceed
256 characters, make sure that the following names are as short as possible:
- The installation path
- Any project names and broker schema names
- Any ESQL and mapping file names