Migrating or importing message flows:
This topic contains advice for dealing with some common problems
that can arise when importing or migrating resources:
The mqsimigratemsgflows command
gives unexpected results
- Scenario: You have imported your Version 2.1 or Version
5.0 message flows into the workbench using
the mqsimigratemsgflows command,
but the results are not what you were expecting.
- Explanation: The mqsimigratemsgflows command
creates a report called mqsimigratemsgflows.report.txt in
the directory from which you ran the command (typically the /eclipse directory).
Read the report for details of the actions taken by the command.
Message flows that have been migrated from Version 2.1 cannot
resolve subflows
- Scenario: A set of message flows has been migrated from Version 2.1 to Version 6.0 and
an error message is issued indicating that: Subflow message
flow name cannot be located.
- Explanation: The subflow in the message flow has not been
migrated correctly. The message flow was exported from Version 2.1 without
the subflow or it was exported into a different file to the subflow.
- Solution: Export everything from Version 2.1 into
one large export file, then migrate the export file to Version 6.0. Alternatively, if the subflow has been imported but the message flow
still shows the error, right-click the node that is causing the error and
click Locate subflow.
A broker has been migrated from Version 2.1 to Version 6.0 and some message flows are now stopped
- Scenario: A broker has been migrated from Version 2.1 to Version 6.0 and some message flows are now stopped
- Explanation: This error can be caused by invalid ESQL in
the deployed message flows that was not detected on the Version 2.1 broker.
- Solution: Remove the affected message flows from the execution
group, then redeploy the message flows. This provides more information
about the error so that you can resolve it.
Deployment of message flows fails when you migrate them from Version 2.1 to Version 6.0
- Scenario: After migration from Version 2.1 to Version 6.0, the deployment of message flows fails
and a BIP2493 error message is displayed.
- Solution: Modify the ESQL so that it references a list rather
than a scalar value. A list is denoted by an empty set of square brackets
("[ ]"), as in the example:
InputRoot.XMl.Field1[]