Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Samples
Extended sites starter store
Use an extended sites starter store to get started on setting up an extended sites solution that will allow your selling organization to provide unique storefronts for different enterprise customers or showcase a number of branded storefronts.
Setting up the Extended Sites environment
To setup an Extended Sites environment you must publish the required Extended Sites starter store archives and enable inventory tracking for your Extended Sites. You can then schedule site-level jobs, configure e-Mail notifications, load your Extended Site catalog data, and modify your Extended Site and asset store archive flows to share and deploy the assets for your Extended Sites.
Modify component store archives flow
Extended sites component store archives can be used to deploy the necessary assets.

User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
  - Aurora starter store
    The Aurora starter store showcases the latest in storefront features, and models best practices in store development, demonstrating a wide scope of retail scenarios. Simplify your responsive B2C or B2B direct web store implementation and reduce your time-to-market by using the Aurora starter store as your development base.
  - Extended sites starter store
    Use an extended sites starter store to get started on setting up an extended sites solution that will allow your selling organization to provide unique storefronts for different enterprise customers or showcase a number of branded storefronts.
    - Setting up the Extended Sites environment
      To setup an Extended Sites environment you must publish the required Extended Sites starter store archives and enable inventory tracking for your Extended Sites. You can then schedule site-level jobs, configure e-Mail notifications, load your Extended Site catalog data, and modify your Extended Site and asset store archive flows to share and deploy the assets for your Extended Sites.
      - Enabling 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.
      - Scheduling a site-level job
        Use the Administration Console to schedule a job on the site level.
      - Configuring outbound email notification messages
        Use the Administration Console to configure outbound email notification messages.
      - Creating a master catalog
        You can create master catalogs by loading XML files or CSV files into the database.
      - Setting up shared assets for Extended Sites
      - 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 your 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.
      - 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.
      - Modify component store archives flow
        Extended sites component store archives can be used to deploy the necessary assets.
    - Creating and configuring an Extended Sites store
      You can create an Extended Site by creating the site stores with WebSphere Commerce Accelerator. Then, you can use the Management Center to configure store information and flows to have the store serve as an extension of your asset store. You can then upload catalog data and catalog filters for the Extended Sites store.
    - Creating a new asset store
      You can create a new storefront asset store by customizing an existing asset store and then publishing the new asset store.
    - Opening and closing stores
      Use the Store Management tool to open or close a store. For example, if you want to perform maintenance on a store, you might want to close the store so that shoppers cannot shop in the store until the maintenance work is complete Then you can open the store once this work is complete so that shoppers can shop in the store.
    - Hosting support
      Support for the hosting business is provided in WebSphere Commerce through the extended sites business model. You may publish the ExtendedSitesHub.sar store archive with your ExtendedSites.sar in order to see an example of a hosting site provided with WebSphere Commerce. Use this sample to get started on setting up a hosting site where you will be able to host sellers with a partitioned catalog (that is, independent catalog).
  - Sample stores
    A sample store is for learning purposes and some tutorials can use a sample store. Do not use a sample store as the base for building your site. Sample stores might not be accessible or translated.
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting

Modify component store archives flow

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

The following component store archives are provided:

ExtendedSitesOrganizationStructure.sar: Contains the sample organization structure for a simple extended sites solution. XML data files can be modified to create new organizations, and modify existing ones.
ExtendedSitesHub.sar: Sample hub that is used to manage all the extended sites created through the Store Creation Wizard.
Aurora.sar: Contains a presentation asset store that has the flow of a B2B store and has the flow of a B2C consumer direct store.
ExtendedSitesCatalogAssetStore.sar: Contains a catalog asset store.

For example, the following changes can be made to any of these store archives:

Rename the data that will be loaded into the database such as organization names, asset store names, and catalog tree.
Add or change JSP files that define the store flow for your presentation asset stores.