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 2.1 and Version
5.0 message
flows into the workbench using mqsimigratemsgflows,
but the message flows are not available to add to a broker archive (bar) file.
- Solution: Migrated message flows are displayed in the workbench as
a closed project. To make the message flows 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.
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.
The compiled message flow (.cmf) file 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