ibm feature pack 8 webinar
TRANSCRIPT
www.crossview.com 12015 |BM and CrossView Confidential | CrossView Intellectual Property
CROSSVIEW COFFEEBREAK
IBM FEATURE PACK 8 HIGHLIGHTS
www.crossview.com 2
Aurora B2B Store Model
• Added B2B functionality
• Additional templates and widgets to support B2B
• Common look and functionality with B2C
REST API Enhancements
• RESTification of the Aurora store model
Search Feature Updates
• Rule based sales category
• Search relevancy enhancement
• Auto-suggest enhancement
Search Architecture Updates
• Price indexing and facets
What’s New & Big in WebSphere Commerce Feature Pack 8
www.crossview.com 4
What WebSphere Commerce Feature Pack are you currently running?
A. Feature Pack 8
B. Feature Pack 7
C. Below Feature Pack 7 (i.e. 6, 5, 4)
D. I am not using WebSphere Commerce
Poll Question
www.crossview.com 5
Merged the B2B and B2C functionality into a single store model. This allows us to leverage within a B2B store model the:
• Commerce Composer
• Responsive Web Design (RWD)
• Search Solution Improvements
• REST Services
Additional templates and widgets created specifically for B2B support have been added.
Aurora B2B Store Model Features and Enhancements
www.crossview.com 6
Buyer Capabilities
• Added self-service organization management
• Allow organization and contract selection after sign-in
• B2B optimized catalog browsing widgets
• Requisition lists
• CSV upload for requisition lists
• Saved orders
• Allow admin to buy on-behalf-of a buyer
Admin Capabilities
• Enable B2B and B2C features (store management)
• Use of Commerce Composer for B2B specific pages
Specific B2B Features & Capabilities
www.crossview.com 7
Storefront Features
• Self Registration for new organizations and buyers
• Manage buyers and organization
• Assign roles to buyers
• Approve buyers and orders
Buyer Organization Management
www.crossview.com 8
• SKU List widget• Catalog Entry List widget • Add to Requisition List widget
B2B Optimized Widgets
www.crossview.com 9
• Organization and contracts are selected after sign-in.
• Contract defines product entitlement and pricing.
Contract Selection
www.crossview.com 10
Enhancements
• REST APIs now supported for all B2C and B2B page flows
• RESTification of the Aurora store pages (all pages now use REST calls)
• Search, interoperability, security, and framework enhancements
• Configuration based command/data-bean mappings
Benefits
• Allows for the alternative use of web UI technologies for storefront presentation
• Create integrations more easily by leveraging available REST APIs
• JSON and XML response formats are supported by default
REST API Enhancements
www.crossview.com 11
• Significant enhancements over the Elite store model, especially in regards to buyer-side and organization management
• No longer is Organization Administration required to handle organization changes, and role assignments.
• Common code and feature base shared with B2C and B2B stores, resulting in easier maintenance.
• Store management capabilities available with the B2B Aurora store model allow the enablement and disablement of store functions and widgets.
Why Adopt B2B in Aurora?
www.crossview.com 12
Is there a straight migration path?
• No. It will need to be a re-base!
• Significant changes from the Elite store model.
Previous B2B store models are now deprecated
• AdvancedB2B
• Elite
Is Migration Possible?
www.crossview.com 13
Search Feature Updates
• Rule based sales category
• Search relevancy enhancement
• Auto-suggest enhancement
Search Architecture Updates
• Price indexing and facets
IBM WebSphere Commerce FEP8
www.crossview.com 14
• Remove the need for business team members to actively manage category pages
• Based on continuous data feed updates, category pages are dynamically updated without user intervention
• Example: I want a holiday category for Christmas items. Create a rule based category page to show all products where
• Attribute dictionary attribute Occasion = ‘Christmas’
• Other examples…
• Additionally, can refine by additional attributes, other categories, or properties on the product or sku.
• Can specify multiple criteria
• In practice, requires good data modeling and use of the attribute dictionary
Business Example
www.crossview.com 16
• When a user searches for “Red Dress”, I want to show not just red items, and not just dresses, but Red Dresses.
• Typically, a Product may come in multiple colors. By using a search rule to boost the red item of the dress versus a random color, then the hero image in the results can be the more relevant sku within the set of skus on the product.
• This is very significant in terms of visual attributes such as color and size.
Business Example
www.crossview.com 19
Strategy• Small to medium size contracts (< 1000 contracts)
• Out-of-the-box B2B price index• Append to existing Product index
• Enterprise size contracts• Custom implementation using separate price index
Technique• Run scheduler/utility on WC to preprocess price data into temporary table
• Instead of pulling on demand which tends to be not effective• Preprocess component data at its own pace into temporary table and have others to
read from it. • Two approaches for preprocessing – full recalculation, or white list
Assumption• Only one active contract for navigation (browsing, faceting, sorting)• Contract based price is calculated based on quantity of one item
Restriction• B2B prices shown in store preview are only from approved content.• Future prices can be previewed provided future contract is indexed.• Cannot index dynamic price conditions but can still display using Price API and
therefore cannot facet and sort against calculated price
Price Indexing and Facets
www.crossview.com 20
Which topic area is of greatest interest to your business needs?
A. The New Aurora B2B Starter Store
B. Search and Marketing Enhancements
C. Merchandising, Marketing and Utilities Enhancements
Poll Question