Feature Pack 4 or later

Publishing and deploying smart phone and tablet starter stores

You can publish the mobile web store archives for smart phone and tablet devices, and deploy the hybrid and native application assets.

Feature Pack 7 or laterNote: The responsive Aurora starter store (Aurora.sar) is displayed by default on all devices. There are no mobile or tablet-specific SAR files to publish. For more information, see Responsive Web Design (RWD).

Before you begin

Ensure that you have completed the following tasks:

Procedure

  1. Publish your smart phone and tablet starter stores SAR file by selecting the store archive:
    Feature Pack 5Feature Pack 4Store Archives > Add On Feature > MadisonsMobileEnhancements.sar
    Feature Pack 5Feature Pack 4A starter composite store archive containing pages for smart phone devices for the mobile web.
    Feature Pack 6 or laterStore Archives > Add On Feature > AuroraMobile.sar
    Feature Pack 6 or laterA starter composite store archive containing pages for the Aurora Mobile storefront.
    Feature Pack 5Feature Pack 4Store Archives > Add On Feature > MadisonsTablet.sar
    Feature Pack 5Feature Pack 4A starter composite store archive containing pages for tablet devices for the mobile web.

    Feature Pack 6 or laterThe Aurora starter store is displayed by default on tablet devices. There are no tablet-specific SAR files to publish.

    Feature Pack 6 or laterThe following SAR files are not available to the Publish wizard or publishstore utility by default:
    • MadisonsMobileEnhancements.sar
    • MadisonsTablet.sar
    To publish these SAR files, see Displaying additional stores.
  2. Select the customer facing store.

    The customer facing store is the parent store where the mobile store pages are deployed.

    For instance:
    • Feature Pack 4Madisons, for a consumer direct Madisons starter store.
    • Feature Pack 4MadisonsStorefrontAssetStore, for an asset store.
    • Feature Pack 5 or laterAurora, for a consumer direct Aurora starter store.
    • Feature Pack 5 or laterAuroraStorefrontAssetStore, for an asset store.
  3. Select the Catalog Asset Store.

    For the Catalog Asset Store, choose the store where you want the mobile e-Marketing spots to be defined.

    For instance:
    • Feature Pack 4Madisons, for a consumer direct Madisons starter store.
    • Feature Pack 4MadisonsStorefrontAssetStore, for an asset store.
    • Feature Pack 5 or laterAurora, for a consumer direct Aurora starter store.
    • Feature Pack 5 or laterAuroraStorefrontAssetStore, for an asset store.
    Feature Pack 5Important: Note the following behavior when you are targeting the Aurora starter store in Feature Pack 5:
    • The Aurora sample catalog does not contain department images that are optimized for smart phone and tablet starter stores.
    • Smart phone and tablet starter stores are not optimized for a 3-tier catalog and display 2nd and 3rd-tier categories as a flattened list.
    • If the products that are being compared do not contain similar attributes, product comparisons might result in empty fields.
    • Smart phone and tablet starter stores are not updated to take advantage of the new swatch selection capabilities in the Aurora starter store. As a result, they do not filter attribute dictionary attribute values based on the SKUs.
    • e-Marketing Spot data might not match those found in the Aurora starter store.

      In general, most image e-Marketing spots are smart phone or tablet-specific, and are not sourced from the Aurora sample catalog data. However, product recommendation e-Marketing spots typically share catalog data and use the same web activities as the Aurora starter store.

      You can publish both sets of sample data (Madisons and Aurora) for testing purposes, however, they are not intended to work correctly together. If you publish Madisons sample data and Aurora sample data together, duplicate data appears in the storefront as a result.

    • Feature Pack 6 or later The preceding behavior when you publish the Aurora Mobile (AuroraMobile.sar) store archive.
  4. Verify that the mobile store is published correctly by opening the store.
    For example, the default store URLs are:
    Smart phone mobile web URL

    Feature Pack 5Feature Pack 4http://host_name/webapp/wcs/stores/servlet/m20/en/madisons

    Feature Pack 6 or laterhttp://host_name/webapp/wcs/stores/servlet/m20/en/aurora

    Tablet mobile web URL

    Feature Pack 4http://host_name/webapp/wcs/stores/servlet/tablet/en/madisons

    Feature Pack 5http://host_name/webapp/wcs/stores/servlet/t20/en/aurora

    Note: The store URLs are dependant on the store name. For example, a default Aurora extended site might have auroraesite as the store name in the URL.
  5. Optional: Deploy the hybrid and native application assets to compile your smart phone and tablet starter stores.
    1. Hybrid applications:
      Android
      WCDE_installdir\components\store-enhancements\samples\Android\Madisons-AndroidHybridMobile.zip
      iPhone
      Delivered as a reference application only.

      WebSphere Commerce V7 mobile application sample for Apple iOS devices

      Feature Pack 6 or laterIBM Worklight
      Feature Pack 6 or laterDelivered as a sample project to deploy cross-platform hybrid applications.

      ../concepts/csmmobileappworklight.html

    2. Native applications:
      Android
      Delivered as a reference application only.

      WCDE_installdir\components\store-enhancements\samples\Android\Madisons-AndroidNativeMobile.zip

What to do next

Review the store enhancements features in Starter store enhancements for the Madisons starter store and mobile features in Smart phone and tablet starter stores to take advantage of the WebSphere Commerce store and mobile enhancements.

To work with location-based services in smartphone and tablet starter stores, you must complete the following tasks:Also see: