Management Center: Migration steps required for different types of customizations

Migrate > Take the first steps after WebSphere Commerce migration > Migrating Management Center > Maintenance and migration considerations for the Management Center

Migration steps required for different types of customizations

Some customizations require that you take additional actions during migration to ensure that the changes are migrated properly.
If OpenLaszlo file changes or customizations in a lower version are implemented (for example, in WebSphere Commerce v6 Feature Pack 3.0.1 or in v7 Feature Pack 1), review the following table for specific actions that you should complete when migrating to a later v7 feature pack.

User change or addition User action
Add a new OpenLaszlo file. No action needed.
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, if doing so will not impact customized functions.
Add new comments to a custom new element in a lower v7 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 v7 feature pack file, then delete the comments.
Add a new element.

If the parent of the element is contained in the target v7 feature pack file, add the new element to the corresponding location to maintain the order. If the new element contains children, copy the children at the same time.

If the new element exists in the target v7 feature pack file with the same unique identifier, add the new element and change the unique identifier of the new element.

Delete an existing element. If the parent of the deleted element is contained in the target v7 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 v7 feature pack file; no further action is needed.
Add a new attribute to an existing element. If the element exists in the target v7 feature pack, add the new attribute.
Delete an existing attribute from an existing element. If the element exists in the target v7 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 v7 feature pack, modify the attribute to the customized value.
Reorder the children of an existing element. If the element exists in the target v7 feature pack, reorder the children to the customized order.
Reordering is only detected 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.
Make changes to a dataset A dataset is treated as an atomic unit. If any change is made to a dataset or its children, replace the target v7 feature pack dataset with the entire customized dataset.

+
Search Tips | Advanced Search

User change or addition	User action
Add a new OpenLaszlo file.	No action needed.
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, if doing so will not impact customized functions.
Add new comments to a custom new element in a lower v7 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 v7 feature pack file, then delete the comments.
Add a new element.	If the parent of the element is contained in the target v7 feature pack file, add the new element to the corresponding location to maintain the order. If the new element contains children, copy the children at the same time. If the new element exists in the target v7 feature pack file with the same unique identifier, add the new element and change the unique identifier of the new element.
Delete an existing element.	If the parent of the deleted element is contained in the target v7 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 v7 feature pack file; no further action is needed.
Add a new attribute to an existing element.	If the element exists in the target v7 feature pack, add the new attribute.
Delete an existing attribute from an existing element.	If the element exists in the target v7 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 v7 feature pack, modify the attribute to the customized value.
Reorder the children of an existing element.	If the element exists in the target v7 feature pack, reorder the children to the customized order. Reordering is only detected 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.
Make changes to a dataset	A dataset is treated as an atomic unit. If any change is made to a dataset or its children, replace the target v7 feature pack dataset with the entire customized dataset.