Migrate > Migrating WebSphere Commerce Developer

Take the first steps after migrating WebSphere Commerce Developer

After completing the migration of WebSphere Commerce Developer, perform these additional actions.

Procedure

1. After migration, the WebSphere Commerce configuration file is a default WebSphere Commerce version 7 configuration file. Manually merge any customizations to the WebSphere Commerce configuration file in previous releases into the version 7 file.

2. After migration, the WebSphere Commerce Accelerator, Administration Console, and Organization Administration Console tools are version 7 default tools. Manually merge any customizations you may have made to the WebSphere Commerce Accelerator, Administration Console, or Organization Administration Console tools in previous releases into the version 7 environment.

3. After migration, your Stores project web.xml file is a default WebSphere Commerce version 7 file. Manually merge any customizations you may have made to this file in previous releases into the version 7 file.

4. After migration, the workspace_dir\WC\xml\member\MemberRegistrationAttributes.xml is a default WebSphere Commerce v7 file. If you customized this file in a previous release, manually merge the customizations. In WebSphere Commerce version 6, this file was located in the following directory: workspace_dir\XML\member\MemberRegistrationAttributes.xml

5. To use the e-Marketing Spot JSP snippet for WebSphere Commerce Accelerator on the store pages instead of the e-Marketing Spot JSP snippet for Management Center, set the marketing version to classic. See Configure the site to use WebSphere Commerce Accelerator Marketing instead of the Management Center Marketing tool.

What to do next

Continue with the post-migration steps:

• After migration, the WebSphere Commerce test server is a default WebSphere Commerce v7 test server. Reapply customization, for example:

  • Global security settings

  • Add or changing the virtual host

  • Changing the heap size

  • JDBC Connection Pool Settings

• Upgrade the tiles-defs.xml file to the 1.1 level:

  1. Open the Stores/WebContent/WEB-INF/tiles-defs.xml file.

  2. Find the line

     <!DOCTYPE tiles-definitions PUBLIC "-//Apache Software Foundation//DTD Tiles Configuration//EN" 
             "http://jakarta.apache.org/struts/dtds/tiles-config.dtd">
     

  3. Replace with this line:

     <!DOCTYPE tiles-definitions PUBLIC "-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
             "http://struts.apache.org/dtds/tiles-config_1_1.dtd">
     

  4. Save and close the file.

  5. Restart the test server.

• Changing the development database type using the setdbtype command
  After you install WebSphere Commerce Developer, the development environment is configured to use the Apache Derby database.

  To change the database type to DB2, Oracle, or back to Apache Derby, run the setdbtype command. Verify the database you are switching to, exists in the network. Changing development database types does not carry over any schema customizations or custom data to the new database.

• Update the cachespec.xml file
  The cachespec.xml is not completely migrated during application migration, to preserve the customizations. You must update the cachespec.xml file manually before continuing with the production migration process.

Previous topic:

Verify the migrated WebSphere Commerce Developer application

+

Search Tips   |   Advanced Search