Enabling store-related fixes

When you install a maintenance package, fixes that update you store (such as starter store JSP files) are not automatically enabled on your environment. The fixes are not automatically enabled to ensure that your store customizations are not overwritten.

If you need to enable a store-related fix, then merge the changes with the files that are currently on your environment. You do not have to complete this procedure if you do not want or need to enable store-related fixes.

Procedure

  1. Enable widget updates to your environment:
    1. Go to the following directory to view widget-related files:
      • AIXLinuxWindowsWC_installdir/wc.ear/Stores.war/Widgets_701/
      • WebSphere Commerce Developerworkspace_dir/Stores/WebContent/Widgets_701
      Tip: To find the files that were updated by the maintenance package, sort the files by Date modified. Review the files that were modified on the same day that you installed the maintenance package. If there are no new updates, then you can skip this step. Proceed to step 2.
    2. If there are updates to the default widgets, then merge the updates with your currently deployed widget files:
    OptionDescription
    If you customized any widgets that were included with WebSphere Commerce:
    1. Compare the updated widget-related files with your customized widgets that are in
      • AIXLinuxWindowsWC_eardir/Stores.war/Widgets_701/
      • WebSphere Commerce Developerworkspace_dir/Stores/WebContent/storename/Widgets
    2. Merge any differences into your customized widget files.
      Note: If you have multiple stores, then you need to repeat this step to merge the changes into all your stores.
    3. Deploy the changes.
    If you did not customize any widgets that were included with WebSphere Commerce
    1. Zip the following directory:
      • AIXLinuxWindowsWC_installdir/wc.ear/Stores.war/Widgets_701/
      • WebSphere Commerce Developerworkspace_dir/Stores/WebContent/Widgets_701
    2. Deploy the compressed file.
  2. Enable store-level JSP updates to your environment:
    1. Go to the following directory.
      • AIXLinuxWindowsWC_installdir/starterstores/ConsumerDirect/
      • WebSphere Commerce DeveloperWC_installdir/starterstores/ConsumerDirect/
    2. Use an extraction utility to extract and view the updated version of Aurora.sar.
    3. After you extract, go to the Aurora.sar/StoreAssetsDir directory to view the store-related files.
      Tip: To find the files that were updated by the maintenance package, sort the files by Date modified. Review the files that were modified on the same day that you installed the maintenance package. If there are no new updates, then you can skip this entire step and you are done.
    4. If there are updates to the default store-related files, then merge the updates with your currently deployed store-related files:
    OptionDescription
    If you customized your store:
    1. Compare the files that are in StoreAssetsDir with the files that are currently in your published store.
      For example,
      • AIXLinuxWindowsCompare the files in WC_installdir/starterstores/ConsumerDirect/Aurora.sar/StoreAssetsDir with the files in WC_eardir/Stores.war/storename/
      • WebSphere Commerce DeveloperCompare the files in WC_installdir/starterstores/ConsumerDirect/Aurora.sar/StoreAssetsDir with the files in workspace_dir/Stores/WebContent/storename/
    2. Merge any differences between the files that are in the StoreAssetsDir with your current store files.
      Note: If you have multiple stores, then you need to repeat this step to merge the changes into all your stores.
    3. Open the following file /starterstores/ConsumerDirect/Aurora.sar/WEB-INF/struts-config-update-common.tpl.xml.
    4. Compare the contents with your current store file:
      • AIXLinuxWindowsWC_eardir/Stores.war/WEB-INF/struts-config-ext.xml
      • WebSphere Commerce Developerworkspace_dir/Stores/WebContent/WEB-INF/struts-config-ext.xml
    5. Merge the changes with your customized store files accordingly.
    6. Deploy the changes.
    If you did not customize your store: You have three options:
    • A) Re-publish the Aurora.sar file through the Administration Console and use the same parameters that you entered when you first published the Aurora.sar. All files will be overwritten for the specific store that corresponds to the parameters that you enter. For more information about publish parameters, see Publishing the Aurora starter store.
    • B) Re-publish the Aurora.sar file through the Administration Console as a new store by entering store identifier and store directory values that are different from your current store. After the store is published, use the new store.
    • C) Re-publish the ExtendedSites.sar file through the Administration Console.
      Note: If you decide to re-publish ExtendedSites.sar, ensure that all your storefront asset stores were not customized. All files for all storefront assets stores will be overwritten.