Completing post-migration tasks for WebSphere Commerce Version 8

After you migrate of WebSphere Commerce Version 8 Developer to WebSphere Commerce Version 9 Developer, complete the following post-migration steps.


Procedure

  1. In WebSphere Commerce Version 9, data cache properties are defined in the WebSphere Application Server Administrative Console. In WebSphere Commerce Version 8, the data cache properties were defined in the cacheinstances.properties file. If the WebSphere Commerce Version 8 store was configured to use data cache, there is no need to migrate your data cache configuration. Delete the cacheinstances.properties from your migrated Stores.war. For more information about data caches, see Enable WebSphere Commerce data cache.

  2. If you customized any searchable attributes in WebSphere Commerce Version 8 and plan to use them in WebSphere Commerce Version 9, we must update KEYS table for the SRCHATTR table.

    1. Connect to the database

    2. Run the following SQL command: 

        update keys set counter = case when (select max(srchattr_id) from srchattr) > 
counter then (select max(srchattr_id) from srchattr) else counter end where tablename = 'srchattr';

  3. Update your cachespec.xml file. The cachespec.xmlis not automatically migrated. If the WebSphere Commerce Version 8 environment was configured to use the cachespec.xml file, we must reapply your configurations to the WebSphere Commerce Version 9 cachespec.xml file.

    1. Open the cachespec.xml file in a text editor. The file can be found in the WCDE_installdir/workspace/Stores/WebContent/WEB-INF directory.

    2. Review the cachespec.xml file. Ensure that the store-cookies property is defined for all cache entries, and it is set to false. It is also recommended that the save-attributes property is set to false for all cache entries.

    3. Save and close the file.

  4. Restart the WebSphere Commerce test server.


What to do next

  1. After migration, the WebSphere Commerce test server is a default WebSphere Commerce Version 9 test server. Reapply any of the following customizations:

    • Global security settings

    • Adding or changing the virtual host

    • Changing the heap size

    • JDBC Connection Pool Settings

Previous topic: Migrate your Watson Content Hub integration.
Next topic: Verify your migrated application.