Process: Extended sites deployment

 

Flow

Legend

 

Objective

An extended sites deployment is used to create a selling environment where multiple stores can share different assets in WebSphere Commerce.

 

Description

Extended sites deployment requires a careful organization structure planning showing all the assets stores, extended sites, and hub. Once determined, the use of the extended sites composite and component store archives together with the tools such as Organization Administration Console and Store Creation Wizard can be used to create all the assets in WebSphere Commerce. After the deployment, some proper testing and database tuning will be required before the site can go live.

 

Features

• Can have as many presentations and catalog asset stores as required.
• Can have extended sites refer to different presentation and catalog asset stores.
• Share majority of assets.

 

Customization

See customization sections of inner processes.

 

Edition

Enterprise

 

Tasks

Task	Description	Role
Deploy asset stores	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 as the look and feel will change.	Store developer
Determine access control and organization structure	Derive an access control scheme and an organization structure that can satisfy all the requirements in terms of registered customers and administrators capability. Questions that help determine organization structure are: can shoppers shop across different stores, can administrators manage several stores, etc.	Store developer
Determine assets	Determine what assets are to be shared.	Store developer
Determine your asset stores	Determine the number of presentation and catalog asset stores required. May create separate asset store for marketing campaigns and others.	Store developer
Determine your extended sites	Determine the number of extended sites or customer facing stores that are required. Customer facing stores are the actual stores where shoppers can purchase from.	Store developer
Modify extended sites component	Extended sites components store archives can be used to deploy the neccessary 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. B2BDirectStorefrontAssetStore - contains a presentation asset store that has the flow of a B2B store. ConsumerDirectStorefrontAssetStore - contains a presentation asset store that has the flow of a consumer direct store. ExtendedSitesCatalogAssetStore - contains a catalog asset store.	Store developer
Modify extended sites SAR	ExtendedSites.sar comes with a predefined access control pocies, organization structure, a set of asset stores and a hub that shows how to quickly setup multiple stores sharing all the assets. This sample 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 JSPs that dictate the flow of the storefronts.	Store developer
Publish SAR in test environment	Publish the store archive(s) in the test environment.	Store developer
Publish SAR(s) to staging and production	Publish store archive(s) to staging and production environments.	Store developer
Test extended sites	Test all the extended sites are functioning correctly before promoting to the production environment.	Store developer

 

Business artifacts

• Catalog asset store SAR
• Deployment strategy
• Extended sites hub SAR
• Extended sites SAR
• Go-to-market strategy
• Organization structure SAR
• Published site

Feedback

(C) Copyright IBM Corporation 1996, 2006. All Rights Reserved.