®

IBM Software Group

Understanding WebSphere Commerce Extended-Sites

Mike Callaghan ([email protected])

WebSphere® Support Technical Exchange

IBM Software Group

Agenda
Overview and scenarios of Extended-Sites
Comparison to traditional models
Starter stores
Shared Assets and store path
Organizational Structure
Contracts
Tooling Flow
Catalog configurations
Designing Extended-Sites
Questions?

WebSphere® Support Technical Exchange

2

IBM Software Group

What are Extended-sites?
Different strategies required for different segments or brands
Each may require separate storefronts
Key is to share as many assets as possible between these sites, to minimize management and maintenance
E-sites provide an infrastructure to share assets, whether it be catalog data, presentation JSPs, or business objects (ie. Promotions/campaign data)
Hub in Accelerator allows for creation and management of the extended sites
Extended-site store can be a B2B direct or Consumer Direct store
Allows greater scalability and ease of deployment for larger number of sites

WebSphere® Support Technical Exchange

3

IBM Software Group

Scenarios for Extended-Sites
Different geographies
based on same set of products, filtered per geography
Tax regulations, shipping rules, may differ per geography


Different brands
customize look and feel, or marketing for each brand (promotions, cross-sells)


Different market segments
separate B2C or B2B customer segments, or by industry
based on same catalog, but filtered per segment


Different customers
customers could require specific taylorings of approvals, pricing, product entitlement, billing options

WebSphere® Support Technical Exchange

4

IBM Software Group

Traditional Model versus Extended-Sites

CATALOG

JSPs/IMAGES

CATALOG

BUSINESS LOGIC

WebSphere® Support Technical Exchange

JSPs/IMAGES

BUSINESS LOGIC

CATALOG

JSPs/IMAGES

BUSINESS LOGIC

5

IBM Software Group

Traditional Model versus Extended-Sites

CATALOG

JSPs/IMAGES

BUSINESS LOGIC

WebSphere® Support Technical Exchange

6

IBM Software Group

When to use Extended-Site model
If multiple customer facing store is indeed needed, decide if extended-sites store model must be used.
Considerations for E-sites include:
Do you have an WC Enterprise license?
Will Catalog Assets, Contracts and/or JSP be shared ?
Will Storefront Assets (JSPs/images) be shared selectively, including multiple branded store fronts?


Table highlights what you can do and cannot do in the different OOB models

Single catalog Multiple look & feel Different prices Different shippings Different promotions Add stores in future

ConsumerDirect B2C

Advanced B2B

E-Sites

YES NO NO NO YES

YES NO YES YES YES

YES YES YES YES YES

NO

NO

YES

WebSphere® Support Technical Exchange

7

IBM Software Group

Extended-Site Starter Stores
Publish an ExtendedSites.sar to create the necessary stores
Extended Sites Hub
Catalog Asset Store
ConsumerDirect & B2BDirect Storefront Asset Stores
Sample Hosted Stores (Extended Site)

WebSphere® Support Technical Exchange

8

IBM Software Group

Hosted Stores
‘Extended-Site’ , ‘Customer-Facing store’
From Accelerator (Store Creation Wizard)
Log in as new admin user
Select ‘Extended Sites Hub’
Extended Sites -> New Store


Configurations to select:
Parent organization
Store type (StorefrontAssetStore) for available commands, views, policies
Initial catalog (CatalogAssetStore)
Payment Methods (Bill customer later, credit cards, etc)


After store creation, you can view, export, re-import the created Service Agreement WebSphere® Support Technical Exchange

9

IBM Software Group

Hosted Stores (cont..)
Creating a hosted store really means making: An organizational unit (placed under the org you select from wizard) Store entity (owning member is the new organization) Fulfillment Center Store relationships (defining the store path, pointing to asset stores for storefront, business logic and commands, store data)
Catalog selection (using catalog filter, product sets)
Business policies (ie. Payment, ShippingMode, Price)






Creates a hosting contract referencing:






PriceList policy (ie. MasterCatalogPriceList) Catalog selection (ie. Extended Sites Catalog Asset Store) Product set Price adjustment Participants (organizations who take part in the contract)


Not the same as a SAR publish
No additional assets (catalogs) are loaded into the DB or placed on filesystem (JSPs)

WebSphere® Support Technical Exchange

10

IBM Software Group

Shared Assets
E-sites build upon shared assets (storefront, business logic, store data) from asset stores
Out of the box we have:
Catalog asset store • Sharing of catalog data including categories, products, items, pricing
Storefront asset store • Sharing of presentation JSPs, promotions, campaigns, commands and URLs, contracts


Could create additional asset stores to group other shared assets

WebSphere® Support Technical Exchange

11

IBM Software Group

Shared Assets (through store path)
Storepath built through STOREREL relationships
Directional, each store has related stores, including itself
Several relationship types (STRELTYP_ID) exist upon store publish, but can be customized to meet needs of E-site

CatalogAssetStore

StorefrontAssetStore


com.ibm.commerce.catalog
com.ibm.commerce.storeitem
com.ibm.commerce.price
com.ibm.commerce.businessPolicy
com.ibm.commerce.measurement.format
com.ibm.commerce.currency.supported
com.ibm.commerce.currency.format
com.ibm.commerce.currency.conversion


com.ibm.commerce.shipping.calculation
com.ibm.commerce.shipping.shipjurisdiction
com.ibm.commerce.shipping.shipmode
com.ibm.commerce.promotions
com.ibm.commerce.contract
com.ibm.commerce.propertyFiles
com.ibm.commerce.storeitem
com.ibm.commerce.view
com.ibm.commerce.URL
com.ibm.commerce.command
com.ibm.commerce.campaigns
com.ibm.commerce.businessPolicy

WebSphere® Support Technical Exchange

12

IBM Software Group

Shared Assets – Example #1 Extended-Site (Hosted Store) com.ibm.commerce.calculation (-27) com.ibm.commerce.promotions (-23) com.ibm.commerce.segmentation (-9) com.ibm.commerce.catalog (-4)

com.ibm.commerce.campaigns (-3)

com.ibm.commerce.price (-7)

com.ibm.commerce.command (-5) com.ibm.commerce.URL (-10) com.ibm.commerce.view (-11)

Catalog Asset Store Storefront Asset Store

MASTER CATALOG

WebSphere® Support Technical Exchange

13

IBM Software Group

Shared Assets – Example #2 Extended-Site (Hosted Store)

com.ibm.commerce.calculation (-27) com.ibm.commerce.catalog (-4)

com.ibm.commerce.promotions (-23)

com.ibm.commerce.command (-5)

com.ibm.commerce.price (-7)

com.ibm.commerce.segmentation (-9)

com.ibm.commerce.URL (-10)

com.ibm.commerce.campaigns (-3)

com.ibm.commerce.view (-11)

Catalog Asset Store Storefront Asset Store 1

Storefront Asset Store 2

MASTER CATALOG

WebSphere® Support Technical Exchange

14

IBM Software Group

Relationships to consider
Promotions
Can greatly slow performance if you share a large number, consider NOT sharing them at storefront asset store level


Customer segments
Need to define segments at organization level, not store level


Inventory not shared
No way to share inventory OOB, have been some customizations to do this however


Shopping Carts not shared
Shoppers do not share the same shopping cart across multiple sites; a customer has shopping cart at each location
Could transfer shopping carts from one store to another


Tax partially supported (see technote #1302881)

WebSphere® Support Technical Exchange

15

IBM Software Group

Organizational Structure
Used to group users and resources together for authorization purposes
Organizational structure plays key role in e-site model, and access control
Shoppers (browse sites, browse catalog, place orders)
Administration policies (update catalog, manage orders, create promotions)


In which organziation a role is played, will determine extent of access
ie. Allow registered customer to shop at one e-site? Or all e-site stores?
Roles are inherited by any descendant organizations


Following diagrams depict general org structures for B2B or B2C e-sites
Note: Could have both B2B and B2C in same site, organizations would be shared

WebSphere® Support Technical Exchange

16

IBM Software Group

Organizational Structure (E-sites with B2C) Root Org

Default Org Site Administrators Customers (reside here)

Extended Sites Seller Org Extended Sites Org Seller admins

Extended Sites Seller OrgB2C Store 1

Customers (Registered B2C Store 1 customer role)

Extended Sites Seller OrgB2C Store 2

Customers (Registered B2C Store 2 Customer role)

WebSphere® Support Technical Exchange

Extended Sites Hub Org

Channel E-sites Hub Managers

Asset Store Org

Catalog asset B2C Storefront store asset store

17

IBM Software Group

Organizational Structure (E-sites with B2B) Root Org

Buyer Org

Site Administrators Extended Sites Seller Org Extended Sites Org

Buyers

Seller admins Extended Sites Seller OrgB2B Store 1

Buyers (Registered B2B Store 1 customer role)

Extended Sites Seller OrgB2B Store 2

Buyers (Registered B2B Store 2 Customer role)

WebSphere® Support Technical Exchange

Extended Sites Hub Org

Channel E-sites Hub Managers

Asset Store Org

Catalog asset B2B Storefront asset store store

18

IBM Software Group

Hosting Contract
Each extended site store should have a base contract which governs the interactions between the store and its customers
An account is not necessary
When the extended site is created, a default contract must also be created for the site, and it would refer to the base contract
A customer of the extended site can then browse your site, and is governed by the specific terms and conditions that comprise the contract for which they are eligible
Example, having a site that does business in both Canada and United States:
Create two e-sites, one for a unique store front to each of the countries
Create a default contract
Each e-site would have a base contract
All customers in a given geography are members of a single buying unit (Canadian site customers browse according to the T&C defined in the contract for the "Canadian" extended site, and same with Amercian customers and American contract)

WebSphere® Support Technical Exchange

19

IBM Software Group

Hosting Contract (B2C Example)

WebSphere® Support Technical Exchange

20

IBM Software Group

Hosting Contract (B2B base contract)

WebSphere® Support Technical Exchange

21

IBM Software Group

Hosting Contract (B2B E-site contract)

WebSphere® Support Technical Exchange

22

IBM Software Group

Extended Sites Tooling Flow Publish Extended Sites SAR (Admin Console)

Publish additional Asset stores (Admin Console)

Create Buyer or Seller Organizations (OrgAdmin Console)

Create administrative users (OrgAdmin Console)

Catalog Asset Store • Master Catalog • Enable Sales Catalog • Create products and items • Create bundles, kits, • Merchandising Associations

Storefront Asset Store • Marketing Campaigns • Customer segments • Promotions • E-marketing spots •

Create Customer-Facing Stores (Accelerator  Extended Sites Hub)

B2C

B2B

WebSphere® Support Technical Exchange

Sales Catalog Tooling Catalog Import

Marketing and Promotions Base Contracts

Base contracts

Customer-Facing Store • Filter products from Master catalog • Create non-shared products • Sales Catalogs • Shipping and taxes • Change Look & Feel, Flow • Inventory • •

Product Management Tooling

Customer Accounts (B2B) Contracts (B2B)

Catalog Filter Sales Catalog Tooling Create Business accounts Create Contracts

23

IBM Software Group

Catalog Filters
In Customer-Facing store, Catalog Filter displays filter settings from:
Current contract and all parent base contracts (if applicable)
The hosting contract for the store
Using a multiple contract hierarchy, with several base contracts, Catalog Filter displays the relevant settings from all the base contracts


Markup/Markdown
Set percentage adjustments based on base contract (shared) price (adjustment cannot be higher markdown than base contract adjustment)


Incusion/Exclusion:
Allows you to create subset of master catalog categories and products to set at the store


For example, we could …
Carry all products in shared catalog
Markdown 5% on certain categories
Add other catgroup/products applicable only to hosted store (not-shared)

WebSphere® Support Technical Exchange

24

IBM Software Group

Commerce Accelerator XML
Configuration XML used to determine which menus appear in which store models
\xml\tools\common\ CommerceAccelerator.xml


corresponds to STORE.STORETYPE field (see diagram on the right)


Can ‘customize’ menus, add new entries, or enable features not enabled OOB for certain store models

B2C

Consumer Direct

B2B

Advanced B2B Direct

HCP

Extended Sites Hub

CPS

Catalog Asset Store

MPS

B2C Storefront Asset Store

BMP

B2B Storefront Asset Store

MHS

B2C Hosted Store

BMH

B2B Hosted Store


Enable Sales Catalog Tooling for Master Catalog
Enable Sales Catalog Tooling for Hosted Stores (only enabled for Catalog Asset Store OOB)

WebSphere® Support Technical Exchange

25

IBM Software Group

Sample Catalog Configurations Extended-Site (use Filtered Master Catalog) Extended-Site 1

Extended-Site 2

(use Sales Catalog 1)

(use Sales Catalog 2)

Extended-Site (use Master Catalog)

Catalog Asset Store

MASTER CATALOG

Sales Catalog 1

Sales Catalog 2

Catalog Asset Store

MASTER CATALOG

WebSphere® Support Technical Exchange

Catalog Filter on Master Catalog

Catalog Asset Store

MASTER CATALOG

26

IBM Software Group

Registered Customers (Role Assignment)
Configure which organizations a user is registered to during runtime from the MemberRegistrationAttributes.xml
Register to parent organization (ie. Shop at all stores):