Replacing an existing store with Aurora

Usually, new features that are introduced in feature pack releases require storefront changes. These changes can be in the form of data model changes, or modifications to the storefront JSP files to use new or updated APIs. For this reason, moving to the latest starter store is the easiest way to have newer components work on your existing store. Depending on the age and design of your site, this retrofitting can be done through several different approaches. If your site is relatively up-to-date, and you are interested in a particular feature, then you can find the migration steps for that solution or component and apply them to your store. Alternatively, you can attempt to replace the entire store with the Aurora starter store by following this set of high-level instructions.

There are alternative approaches to achieve this move to the latest starter store. These methods are not discussed in this document, but involve replacing the front-end JSP files, or moving production data from an old store to a new store. You can choose either of the approaches depending on your comfort level and expertise in these areas.

Note: This task applies to stores that use the extended sites business model.

Procedure

Switch your existing storefront asset store to the Aurora storefront asset store.
1. Publish the store archive that contains the Aurora storefront asset store.
  The store archive differs depending on your feature pack level:
  - Publish the Aurora.sar store archive. In the store publish wizard, choose this option: Publish an asset store for use in the extended sites business model.
2. Migrate all custom modifications to the Aurora storefront asset store. The approach to this step depends on the amount of customization that is done to your original asset store. It might be easier to implement these changes again, rather than migrate changes from your previous asset store.
3. Optional: To test, publish a new extended site store to see that it functions properly.
4. Change existing extended sites stores to point to the new Aurora storefront asset store by modifying the STOREREL table.
5. Populate your extended site stores with all the store functions that storefront asset store has.
  This step is required regardless of whether your existing extended site stores already have store functions or not. The store function settings are stored in the EMSPOT and DMEMSPOTDEF tables in rows in which the USAGETYPE value is either STOREFEATURE or STOREFILEREF.
  1. To get a list of all the store function entries in these two tables for your new storefront asset store, run these two SQL statements:
```
select * from emspot where usagetype in ('STOREFEATURE','STOREFILEREF') and storeent_id=storeent_id; 
```
```
select * from dmemspotdef where emspot_id in (select emspot_id from emspot where usagetype in ('STOREFEATURE','STOREFILEREF') and storeent_id=storeent_id);
```
    Where the storeent_id is the store entity ID of the new storefront asset store, for example, 10001, as defined in the STORE_ID column of the STORE table.
  2. Create equivalent entries in the EMSPOT and DMEMSPOTDEF tables for your extended site stores. You must have all the same entries for extended site stores. Consider by using the Data Load utility to create the entries.
6. Change the access controls for each extended site store that is being moved over.
  1. Log in to Organization Administration Console.
  2. Select the organization that owns the current extended site store you want to switch over, then click Policy Subscription.
  3. Remove the old storefront asset store policy group.
  4. Add the new Aurora storefront asset store policy group.
  5. Click OK.
The Aurora starter store requires that the search solution features be properly configured to function. Therefore, you must set up search, and build the search index.

Results

Your extended sites are now using the new features available in the latest starter store.