Samples > Sample stores > Extended Sites starter store


Set up the extended sites environment

  1. Publish a store archive using the Publish wizard
    Use the Publish wizard to create stores and store related components.

  2. Enable inventory tracking for Extended Sites
    Reseller stores, supplier stores, and extended sites are created with the Availability To Promise (ATP) feature enabled but with inventory tracking disabled by default.

  3. Schedule a site-level job
    Use the Administration Console to schedule a job to run for the site.

  4. Configure outbound e-mail notification messages
    Use the Administration Console to configure outbound e-mail notification messages.

  5. Load the catalog
    In WebSphere Commerce you can create a catalog either by using the Product Management tools in the WebSphere Commerce Accelerator, or by using the loading utilities to mass load the catalog. Usually, a catalog is mass loaded and then maintained by using the Product Management tools.

  6. Set up shared assets for Extended Sites

  7. Modify extended sites starter store archive flow
    The Extended Sites starter store archive, ExtendedSites.sar, comes with predefined access control policies, organization structure, a set of asset stores, and a hub that shows how to quickly setup multiple stores sharing all the assets. This starter store archive can be modified to meet the requirements. The store archive is composed of XML data files that are loaded into the database and JSP files that dictate the flow of the storefronts.

  8. Modify asset store archives flow
    Additional presentation asset stores can be created as required. For example, you may want to create an asset store per geography, per brand, or per segment to give each a unique presentation.

  9. Modify component store archives flow
    Extended sites component store archives can be used to deploy the necessary assets.


+

Search Tips   |   Advanced Search