Contents: Planning, installing, and configuring Mashup Center : Mashup Center 2.0
When you upgrade to Mashup Center 2.0, some of your data mashups might be affected by the new behavior, which includes changes in the Transform, Group, and For Each data mashup builder operators.
The upgrade process will attempt to migrate all affected data mashups so that they return the same results that they returned in version 1.x. If migration of a data mashup is not possible, or if it is unsuccessful, then you might need to edit that data mashup to obtain version 1.x results. If migration of a data mashup succeeds, the migrated data mashup might use version 1.x behavior for some operators. In those cases, you will need to edit the data mashup operators if you want them to benefit from version 2.0 enhancements.
For information about the data mashup builder operators, see the MashupHub User and Administrator Guide
Failed data mashup migration
A failed data mashup migration means that the data mashup could not be automatically migrated. After the upgrade script is completed, the system log file will contain a list of all data mashups that failed automatic migration. The log file will include warnings indicating the reason for each failure. The log file will also contain statistics about how many data mashups were affected by version 2.0 changes and how many of those were successfully migrated.
If you run a data mashup for which migration has failed, the results from the data mashup will be the same as they were prior to upgrade. However, if you open the data mashup for editing, it will adopt version 2.0 behavior for all editing and saving operations. You might need to modify the data mashup so that it behaves as it did prior to upgrade.
Parent topic: Upgrading : Mashup Center 2.0
Previous topic: Running the configuration task cluster : Mashup Center 2.0