Migration steps required for different types of customizations
Some customizations require that you take additional actions during migration to ensure that you migrate the changes properly.
If OpenLaszlo file changes or customizations in a lower version
are implemented (for example, in WebSphere Commerce Version 6 Feature
Pack 3.0.1 or in Version 7 Feature Pack 1), review the following table
for specific actions to complete when you migrate to a later Version
7 feature pack.
| User change or addition | User action |
|---|---|
| Add an OpenLaszlo file. | No user action needed. This action is done automatically. |
| Delete an existing OpenLaszlo file. | After the new Feature pack is installed and
enabled, the files you deleted might exist again. You might want to
delete them again, but the migration tool does not report the deleted
file names. You can delete the files manually, but you must ensure
that deleting the file does not adversely affect the customized functions.
|
| Add new comments in a lower Version 7 feature pack | The Migration compare editor cannot detect new or changed comments. You need to add the new comments within the target Feature Pack manually. |
| Delete existing comments. | If the same comments are found under the parent element in the target Version 7 feature pack file, then delete the comments. |
| Add an element. |
|
| Delete an existing element. | If the parent of the deleted element is contained in the target Version 7 feature pack file, then delete the element and its children from the parent. If the parent of the deleted element is not contained in the target Version 7 feature pack file; no further action is needed. |
| Add an attribute to an existing element. | If the element exists in the target Version 7 feature pack, add the new attribute. |
| Delete an existing attribute from an existing element. | If the element exists in the target Version 7 feature pack, then delete the attribute. |
| Modify the value of an existing attribute within an element. | If the element and same attribute exists in the target Version 7 feature pack, modify the attribute to the customized value. |
| Reorder the children of an existing element. | If the element exists in the target Version
7 feature pack, reorder the children to the customized order. Note: Reordering
is detected only if the only change to the element is that the children
are reordered. Any other type of reordering, for instance if new children
are added or if children are deleted, is not detected. |
| Change a data set | A data set is treated as an atomic unit. If any change is made to a data set or its children, replace the target Version 7 feature pack data set with your entire customized data set. |
| Modify the text value of an element | If the element and same text node exists in the target Version 7 feature pack, modify the text value to the customized value. |
You can examine the files to determine which
ones you want to delete, then delete them manually. Alternatively,
you can delete the file using click-to-merge, but you must migrate
that file individually, using the