Introduced in Feature Pack 1

First steps after enabling features

Procedure

  1. If your previous environment used WebSphere Commerce Solr search, you must migrate the WebSphere Commerce search server.
    Note: If your previous environment used WebSphere Commerce Solr search and you want to publish a new store model, such as Aurora, then after you enable features, you must first migrate the WebSphere Commerce search server, then publish the new store.
  2. Feature Pack 4 or laterIf you migrated or updated from a lower feature pack level to a higher feature pack level, you must restart the server after you enable a feature.
  3. Feature Pack 5 or laterIf you want to improve performance by setting up JSP snippet caching based on activity behavior, see Setting up JSP snippet caching based on activity behavior.
  4. Feature Pack 5 or laterIf your site plans to set a default catalog you must migrate any WebSphere Commerce Feature Pack 3 SEO URLs used by your site. Migrating your SEO URLS ensures the URLs can use the default catalog.
    To migrate the SEO URLs you must run a migration script. For more information, see Migrating SEO URLs to use the default catalog.
  5. Feature Pack 5 or laterIf your extended site store is published on a lower-level WebSphere Commerce feature pack, you must prepare your store before you load the catalog description overrides for your store.
    If you migrate your extended site store, you can use the Management Center catalog upload or the Data Load utility to load description overrides. Loading description overrides provides your store with the capability to set store-specific storefront descriptions for catalog entries inherited from your asset store. When you load a description override, the inherited description no longer displays on your storefront. Your description override displays to shoppers on your storefront for the catalog entry. For more information, see Migrating a store to use catalog entry description overrides.