Migration of message mappings from Version 5.0

Use the mqsimigratemfmaps command to migrate message mappings. This command is part of the Message Brokers Toolkit, not the run time on Windows and Linux, and is not available in the command path by default. You can find the command under the Eclipse directory of the tooling installation. There are some restrictions on migrating message mappings.

The following table lists the mapping functions that are supported in Version 5.0 but not supported in Version 6.0, and shows the error messages that you might see. Mappings that contain these Version 5.0 functions cannot be migrated to Version 6.0, and must be re-created and redeployed using another node, such as a Java Compute node. Alternatively, try to migrate as much of the mapping as possible using the migration command, view the error report to see details of the functions that could not be migrated, and create a new node that will execute the non-migrated functions.
Supported in Version 5.0 Migration utility error message
Expressions that involve multiple instances of a repeating source element, for example:

src_msg.e[1] + src_msg.e[2] -> tgt_msg.e

Error:102: Unexpected index '2' encountered for target mappable 'e'. The expected index is '1'. Migration currently provides no support for expressions involving more than one instance of the same repeating-element.
ESQL field references that contain the asterisk wildcard character "*". For example:

src_msg.e.* or src_msg.e.*[]

Error:130: ESQL field-reference 'src_msg.e.*' cannot be migrated. Migration currently provides no support for field-references containing '*'.
Dynamic ESQL field references. For example:

src_msg.e.{'a' || 'b'}

Error:131: ESQL field-reference 'src_msg.e.{'a' || 'b'}' cannot be migrated. Migration currently provides no support for dynamic field-references.
ESQL expressions that contain a reference to the temporary index-variable "#I". For example:

src_msg_e || "#I" -> tgt_msg.e

Error:128: ESQL expressions containing the variable '#I' anywhere other than the index of a repeating-element cannot be handled by the migration.
Expressions within an index of a repeating element. For example:

src_msg.e[src_msg.a] or src_msg.e["#I" +5] or src_msg.e[< 3]

Error:116: ESQL field-reference 'src_msg.e[< 3]' cannot be migrated. Migration currently provides no support for indexes other than the variable '#I' and plain integer indexes.
Aggregation functions MIN, MAX, and COUNT, used with the ESQL SELECT expression. For example:

SELECT MAX("#T".FIRSTNAME) FROM Database.CUSTOMER AS "#T" WHERE "#T".CUSTOMERID = 7

Error:135: The ESQL expression 'SELECT MAX("#T".FIRSTNAME) FROM Database.CUSTOMER AS "#T" WHERE "#T".CUSTOMERID = 7' could not be migrated. The expression contains syntax which has no direct equivalent in the new map-script language.
ESQL's IN operator. For example:

src_msg.e IN (1, 2, 3)

Error:135: The ESQL expression 'SELECT MAX("#T".FIRSTNAME) FROM Database.CUSTOMER AS "#T" WHERE "#T".CUSTOMERID = 7' could not be migrated.
Related concepts
Client environment
Related reference
mqsimigratemfmaps command
Restrictions on migrating message mappings
Commands