For example, if the copyextensions target runs as part of an upgrade from Version 8.5 to 9.2, the Sterling Selling and Fulfillment Foundation updates the UpgradeLog.xml file to include the following element:
<Task EndTime="11/09/2012 01.56.35 AM" Name="copyextensions"
StartTime="11/09/2012 01.56.30 AM" Status="Finished" Version="9.1"/>
LogFile is not included in the element because the log file is provided by the user and is not generated internally by the upgrade process.
The copyextensions target runs only once as part of a multi-hop upgrade from Version 8.5 to 9.2; however, some targets run multiple times in a multi-hop upgrade. In this case, the UpgradeLog file includes information about the child hop versions for the target. Information is grouped by target. For example, if the migration-validation target runs as part of a multi-hop upgrade from Version 8.5 to 9.2, the UpgradeLog.xml file is updated with the following element:
<Task EndTime="11/09/2012 01.57.56 AM" Name="migration-validation"
Starttime="11/09/2012 01.57.40 AM" Status="FAILED" Version="9.1>
<Task EndTime="11/09/2012 01.57.55 AM" LogFile="./9.0/migration-
validation-9.0-9.1.log" Name="migration-validation"
StartTime="11/09/2012 01.57.45 AM" Status="FAILED" Version="9.0">
<Task EndTime="11/09/2012 01.57.53 AM" LogFile="./8.5/migrtion-
validation-8.5-9.0.log" Name="migration-validation"
StartTime="11/09/2012 01.57.49 AM" Status="FINISHED"
Version="8.5" />
</Task>
</Task>
In this example, the root migration-validation element corresponds to the Version 9.1 to 9.2 hop and contains nested child elements that correspond to the Version 8.5 to 9.0 hop and the Version 9.0 to 9.1 hop. The status indicates that the Version 8.5 to 9.0 hop succeeded but the Version 9.0 to 9.1 hop failed. Thus, the root migration-validation target failed.