Message flow migration notes

You need to be aware of the following information about each message flow when you use the mqsimigratemsgflows command.

Promoted property name

In Version 2.1, when a promoted property is created through the drag and drop process, the property name (xmi.label) is set to be the translation of the attribute name. The original attribute name must not contain spaces otherwise it is rejected by the broker. However, promoted attributes are never sent to the broker, so they could, in Version 2.1, have contained spaces.

When the flow is migrated, the original name is lost and only the translation is kept. As the promoted attribute can override several attributes the code must ensure that the original name corresponds to the translated name.

The solution is to generate a suitable attribute name by replacing spaces or other offending characters with the unicode representation. The propertyName attribute of the propertyDescriptor is set to key=Property.<the translated attribute name>. The UI returns <the translated attribute name>

However migrated flows have not retained the attribute system name, only the translated name. It is therefore difficult or impossible to locate the original attribute.

Converting Version 2.1 names that are not valid

Flows and properties can contain names that are not valid in Version 5.0. If this situation arises, the following transformation occurs. Each offending character is replaced with a series of characters representing its unicode code point. For example, the "!" is replaced with X0026. This is explained in the report file that is generated.

This transformation is deterministic. If a flow is migrated on another occasion, which refers to a flow with a character that is not valid, both names are transformed in the same way.

These transformations do not result in conflicting names except in extremely rare circumstances. A conflict might occur because a Unicode code point sequence occurs in a name precisely where the corresponding character occurs in another name which is otherwise identical. In this case you must rename one of these flows or properties and re-export the flows. You are recommended to select a new name that does not contain a Unicode code point sequence ('Xnnnn') and to rename the message flow in the Control Center before you migrate. Never rename a .msgflow file in the file system, always use the Control Center or the workbench to perform renaming tasks.

Mapping of node type

Version 2.1 nodes are converted to Version 5.0 nodes as follows:
Version 2.1 node Version 5.0 node
Compute Compute
Filter Filter
Database Database
DataDelete Database
DataInsert Database
DataUpdate Database
Extract Compute
Warehouse Database
Related concepts
Message flows
Related reference
mqsimigratemsgflows command