Migrating Management Center
Run the Management Center Migration Utility to migrate your customized version 7.0 Management Center to version 8.0.
Previous versions of Management Center were written in OpenLaszlo and compiled into Flash. If you customized the OpenLaszlo Management Center and want to use those customizations in version 8.0, the Management Center Migration Utility can facilitate the migration. The migration utility supports migrations from WebSphere Commerce Version 7.0 Feature Pack 2 - Feature Pack 8. Migrations from version 6.0, version 7.0 base, or version 7.0 Feature Pack 1 are not supported by this utility.
The utility extracts customizations from your version 7.0 Management Center, and then applies those customizations to a version 8.0 Management Center. The following table outlines the types of customizations are extracted and migrated:
Customization type | Description |
---|---|
OpenLaszlo source code | Custom OpenLaszlo code that is found under the
workspace_dir\LOBTools\WebContent\WEB-INF\src\lzx directory
is converted to the version 8.0 Management Center definition syntax, and then merged into the
version 8.0
workspace_dir\LOBTools\WebContent\WEB-INF\src\xml directory.
Changes made to customizable files are detected, and if possible, the changes are applied to the
version 8.0 version of the file. Note: Changes made to restricted files are ignored. The
migration utility is able to convert custom OpenLaszlo code that is similar to the code that was
delivered by IBM in version 7.0. If you wrote code that extends or uses IBM OpenLaszlo classes, the
conversion is likely to work well. If you wrote code that uses OpenLaszlo classes that were not used
by IBM, such code cannot be migrated. |
Definition files | Custom definition code that is found under the
workspace_dir\LOBTools\WebContent\config directory is
converted to the version 8.0 Management Center definition syntax, and then merged in the version 8.0
workspace_dir\LOBTools\WebContent\WEB-INF\src\xml directory.
Changes made to customizable files are detected, and if possible, the changes are applied to the
version 8.0 version of the file. Note: Changes made to restricted files are ignored. |
Struts configurations | Custom struts configurations found in the version 7.0 workspace_dir\LOBTools\WebContent\WEB-INF\struts-extension.xml file are converted to Spring configurations, and then added to the version 8.0 workspace_dir\LOBTools\WebContent\WEB-INF\spring-extension.xml file. The migration utility is able to port struts configurations for struts actions that were provided by IBM. If you wrote your own struts actions, the utility will not port these configurations to Spring. Migrate these changes manually, this includes converting your struts actions to Spring controllers. |
Image files | Custom images that are used as resources in custom OpenLaszlo code are copied to the version 8.0 workspace_dir\LOBTools\WebContent\images directory. |
Resource bundles | Custom properties files that are found under the workspace_dir\LOBTools\src directory are copied to the same directory in version 8.0. |
Configuration XML files | Custom XML configuration files that are found under the workspace_dir\LOBTools\WebContent\WEB-INF\config directory are copied to the same directory in version 8.0. |
Before you begin
- Verify that WebSphere Commerce Developer Version 7.0 is at a minimum level of Feature Pack 2.
- Verify that WebSphere Commerce Developer Version 8.0 is at a minimum level of Mod Pack 1.
- Ensure that your customized version 7.0 LOBTools project is available to the version 8.0 Management Center Migration Utility.
- Back up your version 7.0 and version 8.0 LOBTools projects.
Procedure
- On WebSphere Commerce Developer Version 8.0, open a command prompt, and go to the WCDE_installdir\bin directory.
-
Run the following command to migrate your version 7.0 LOBTools
project:
migrateLOBTools.bat version7LOBToolsDirectory featurePackNumber [Edition]
- version7LOBToolsDirectory
- The fully qualified path of the version 7.0 LOBTools project.
- featurePackNumber
- A number 2 - 8, which represents the version 7.0 feature pack level to migrate.
- Edition
- Optional: A value, express or pro, which represents the version 7.0 edition to migrate. If you are migrating from Enterprise edition, omit this parameter.
Examples: -
Verify that the utility successfully completed by reviewing the
WCDE_installdir\logs\migrateLOBTools.log log file.
Tip: The migration utility continues until completion, migrating as many customizations as it can. Warning messages appear in the log file for any customizations that could not be migrated. These warnings are likely caused by inconsistencies in your Management Center implementation. Rather than correcting the warnings on version 7.0 and rerunning the utility, use these warnings to help you fix the customization in version 8.0.
-
If you customized either of the following files in version 7.0, manually merge your changes
with the files in version 8.0.
- workspace_dir\LOBTools\WebContent\WEB-INF\web.xml
- workspace_dir\LOBTools\WebContent\xml\StorePreviewAlias.xml
What to do next
- If your WebSphere Commerce Developer Version 8.0 was active while you ran the Management Center Migration Utility, manually refresh the LOBTools project to view your migrated custom code.
- In WebSphere Commerce Developer Version 8.0, publish application to the test server.
- In WebSphere Commerce Developer Version 8.0, test your migrated Management Center.