Taking your first steps after migrating WebSphere Commerce Developer

After you migrate of WebSphere Commerce Developer to version 8.0, complete the following steps.


  1. In version 8.0, data cache properties are defined in the WebSphere Application Server Administrative Console. In version 7.0, the data cache properties were defined in the cacheinstances.properties file. If your version 7.0 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 Enabling WebSphere Commerce data cache.
  2. If you used catalog filters and pricing rules in version 7.0 and plan on using those functions in version 8.0, you need to enable them manually.
    1. Connect to your database.
    2. Set the VALUE for the wc.search.entitlement property to 1 by using the following SQL command:
      The STOREENT_ID for your store.
    3. Repeat for all applicable STOREENT_ID entries.
  3. If you customized any searchable attributes in version 7.0 and plan to use them in version 8.0, you must update KEYS table for the SRCHATTR table.
    1. Connect to your 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. Restart the WebSphere Commerce test server.

What to do next

  1. Update your database to the latest Mod Pack and Fix Pack level by running the updatedb utility.
  2. After migration, your WebSphere Commerce test server is a default WebSphere Commerce Version 8.0 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