Resolving problems that occur when preparing to deploy message
flows
This topic contains advice for
dealing with some common problems that can arise during preparations
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 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 operation shows any errors, and makes the project resources available
to be added to a BAR file.
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. 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 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.
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 ESQL
or mapping files, the overall file path length of those files
must not exceed 256 characters, due to a Windows file system limitation.
If you have a message flow that includes mapping
or ESQL files that have a path length that exceeds 256 characters,
the message flow cannot be compiled when you try to add it to a BAR
file, and therefore cannot be deployed.
- Solution: To ensure that the path length does not
exceed 256 characters, use names that are as short as possible for
the following resources:
- The installation path
- Project names and broker schema names
- ESQL and mapping file names