Migrate WebSphere Commerce Version 7 Feature Pack 8 Management Center

Run the Management Center Migration Utility to migrate our customized Feature Pack 8 Management Center to WebSphere Commerce Version 9.0.0.1+.

The utility extracts customizations from your Feature Pack 8 Management Center, and then applies those customizations to a WebSphere Commerce Version 9.0.0.1+ Management Center. The following table outlines the types of customizations that 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 WebSphere Commerce Version 9.0.0.1+ Management Center definition syntax, and then merged into the WebSphere Commerce Version 9.0.0.1+ 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 WebSphere Commerce Version 9.0.0.1+ 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 Feature Pack 8. 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 WebSphere Commerce Version 9.0.0.1+ Management Center definition syntax, and then merged in the WebSphere Commerce Version 9.0.0.1+ 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 WebSphere Commerce Version 9.0.0.1+ version of the file.

Note: Changes made to restricted files are ignored.

Struts configurations Custom struts configurations found in the Feature Pack 8 workspace_dir\LOBTools\WebContent\WEB-INF\struts-extension.xml file are converted to Spring configurations, and then added to the WebSphere Commerce Version 9.0.0.1+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 our own struts actions, the utility will not port these configurations to Spring. Migrate these changes manually, which includes converting your struts actions to Spring controllers.
Image files Custom images used as resources in custom OpenLaszlo code are copied to the WebSphere Commerce Version 9.0.0.1+ 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 WebSphere Commerce Version 9.0.0.1+.
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 WebSphere Commerce Version 9.0.0.1+.

Note: The page layout directory is removed when the Management Center Migration Utility runs, since the Page Layout tool is deprecated.


Before starting

  1. Ensure that our customized Feature Pack 8 LOBTools project is available to the WebSphere Commerce Version 9.0.0.1+ Management Center Migration Utility.

  2. Back up your Feature Pack 8 and WebSphere Commerce Version 9.0.0.1+ LOBTools projects.


Procedure

  1. On the WebSphere Commerce Version 9.0.0.1+ development environment, open a command prompt, and go to the WCDE_installdir\bin directory.

  2. Run the following command to migrate your Feature Pack 8 LOBTools project:

    • migrateLOBTools.bat version7LOBToolsDirectory featurePackNumber [Edition]

    Where:

      version7LOBToolsDirectory
      The fully qualified path of the Feature Pack 8 LOBTools project.

      featurePackNumber
      A number 8, which signifies Feature Pack 8.

      Edition
      The edition from which we are migrating. Use the pro value if we are migration from the Professional edition. If we are migrating from Enterprise edition, omit this parameter.

    Example: WebSphere Commerce Professional Edition Feature Pack 8

      migrateLOBTools.bat Z:\IBM\WCDE_PRO70\workspace\LOBTools 8 pro

  3. Verify that the utility completed successfully 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 the Management Center implementation. Rather than correcting the warnings on Feature Pack 8 and rerunning the utility, use these warnings to help you fix the customization in WebSphere Commerce Version 9.0.0.1+.

  4. If you customized either of the following files in Feature Pack 8, manually merge our changes with the files in WebSphere Commerce Version 9.0.0.1+.


What to do next

  1. If the WebSphere Commerce Version 9.0.0.1+ development environment was active while you ran the Management Center Migration Utility, manually refresh the LOBTools project to view your migrated custom code.

  2. From the WebSphere Commerce Version 9.0.0.1+ development environment, publish application to the test server.

  3. Test your migrated Management Center.

Previous topic: Migrate your EJB entity beans to Java Persistence API.
Next topic: Migrate our custom Physical Service Data Objects.