When you upgrade to IBM® Mashup Center, v220.127.116.11, some of your data mashups might be affected by changes that have been made to the Transform operator.
The upgrade attempts to migrate all affected data mashups so that they return the same results that they returned in version 2.x. If automatic migration of a data mashup is not possible, or if it is unsuccessful, then you might need to edit that data mashup after the migration to obtain your earlier version 2.x results.
Failed data mashup migration
A failed data mashup migration means that the data mashup could not be automatically migrated. After the upgrade completes, review the system log file located at <installDir>/Hub/installedApps/Mashup Hub.ear/mashuphub-enterprise.war/META-INF/logs/javamashuphub.log
. The log file contains a list of failed data mashup migrations and warnings indicating the reason for each failure. The log file also contains statistics about how many data mashups were impacted by v18.104.22.168 changes and how many of those data mashups were successfully migrated.
Mashup Center v22.214.171.124 introduces two changes for the Transform operator in the data mashup builder:
Changes to nonexistent text node copying in the Transform operator
Mashup Center v126.96.36.199 corrects a data mashup builder behavior that affects how nonexistent text nodes are treated by copy operations in the Transform operator. As a result of this correction, data mashups affected by the behavior in v2.x might behave differently after they are migrated to v188.8.131.52.
Changes to the default Output tree in the Transform operator
In previous versions of Mashup Center, the initial Output tree for all Transform operators included an empty namespace declaration that displayed as xmlns=""
. During the data mashup migration to v184.108.40.206, the empty namespace declaration is removed from all Transform operator Output trees.
Parent topic: Upgrading and migrating data to Mashup Center 220.127.116.11