2 eCommerce and Microsoft's next generation Web Ryan Donovan Commerce Server Product Unit Session code: WUX05-IS

3 Agenda eCommerce & Microsoft's next generation Web Scenario Overview Multi-Channel: It’s beyond the browser! Solution Architecture Overview Leveraging Commerce Server “Mojave” & SharePoint Building a Next Generation eCommerce Site Using the APIs Extending the APIs Integrating with SharePoint

The World… Is now Multi-Channel beyond the PC CPG X Distributor X SCM Merch. WMS EnterpriseBPM Sell-Side Trading Partner X ERP

Today: Commerce Server 2007

6 Common Pain Points & Feedback Challenges for Developers Multiple APIs with Consistent Inconsistency APIs do not leverage.NET patterns APIs are not extensible SharePoint and CS2007 do not get along well Challenges for Businesses No Visual Preview Look-and-Feel Changes Require a Developer Tricky to Implement New Content & Mediums Time to Market - given extensive development

Microsoft Commerce Server code name “Mojave” delivers the ability to increase your business reach by selling through multiple channels through a new default out-of-the-box shopping site based on ASP.NET 2.0 Web Parts deployed in SharePoint and other SharePoint commerce services, and a compelling new multi-channel commerce foundation API, with a new unified run-time calling model, new extensibility points and new built-in features. Multi-channel is here now Out-of-the-box shopping experiences Tools to empower Merchandisers and Marketers Commece Server “Mojave” Out of the box integrated consumer centric multi-channel capabilities over multiple mediums, brands, and locales 3 out-of-the-box channels ready to go: Web, Mobile, Live Services New channels require configuration and not customization Out of the box ASP.NET web part shopping site Web 2.0 social networking paradigms via SharePoint and Live integration E-commerce web features easily added by business users, skin-able by designers (Expression), extendable by developers (Visual Studio) Inline WYSIWYG product information and presentation editing and preview Content management capabilities: workflow, approval, and publishing Familiar Office-like environment minimizing learning curve

Next-Gen eCommerce Architecture Based upon Commerce Server "Mojave" & SharePoint CS2007 IT Pro Tools CS2007 IT Pro Tools Commerce Server 2007 Catalog, Orders, Profiles, Marketing, Analytics, Staging, Web Services, BizTalk AdaptErs Commerce Server 2007 Catalog, Orders, Profiles, Marketing, Analytics, Staging, Web Services, BizTalk AdaptErs CS2007 Business User Tools Catalog Manager, Marketing Manager, Customer & Order Manager CS2007 Business User Tools Catalog Manager, Marketing Manager, Customer & Order Manager * SharePoint installation required “Mojave” SharePoint commerce services E.g.: Shopping, Checkout, Profile, … Shopping Web Site* Experience (white label) Shopping Web Site* Experience (white label) CS2007 IT Pro and Designer Tools CS2007 IT Pro and Designer Tools “Mobile” Template Site templates “Rich” Template Custom UX: Customize Web Parts “Mojave” multi-channel commerce foundation Unified and simplified run-time calling model Multi-Channel Interface New Core E-Commerce Shopping Features Custom Logic: Op/Entity Model Custom Logic: Op/Entity Model Custom UX: Direct to Mojave API

9 Commerce Server "Mojave" Multi-channel commerce foundation

Multi-Channel commerce foundation Multi-channel commerce foundation E-Commerce Site Store Kiosk On-line Community Supply Chain Systems CRMERPMerchWHMPIMSCMPOSSCM

11 Principles of the API Design For the Multi-channel commerce foundation Reduce developer ramp-up time by providing a consistent API model across all Commerce Server functional areas Provide the out-of-the-box “business logic” layer that is currently produced as a one-off for every Commerce Server deployment Clear separation of presentation logic and business logic, facilitating multi-channel e ‑ commerce Provide an extensibility model that will allow both Microsoft and 3rd party developers to more easily enhance functionality both for general and business specific purposes Allow the ability to accomplish multiple operations in a single call Support migration of existing CS2007 sites to Mojave by residing side-by-side with an existing CS2007 implementation Multiple presentation support

var productQuery = new Query (“Product”); productQuery.Properties.Add(“Id”); productQuery.Properties.Add(“DisplayName”); productQuery.SearchCriteria.Model.Properties.Add(“Id”, “1243”); productQuery.SearchCriteria.Model.Properties.Add(“CatalogId”,”Adventure Works Catalog”); Response response = OperationServiceAgent.ProcessRequest(requestContext, productQuery.ToRequest()) Mojave foundation exposes a single generic class which represents all Commerce Server entities called a “CommerceEntity” Different types of Commerce Entities are distinguished by the “ModelName” property Example query: Commerce Entities Overview

Property Bag Getters/Setters - GetPropertyValue() & SetPropertyValue() methods Contains both CommerceEntity properties and relationships Commerce Entities: PropertyCollection

14 CommerceEntity: Relationships Relationships are also returned in the Properties collection RelationshipList offers paging support Relationships are manipulated in the same manner as other Commerce Entities Relationships are extensible QueryRelatedItem queryVariants = new QueryRelatedItem (Product.RelationshipName.Variants); productQuery.RelatedOperations.Add(queryVariants);

15 Using the API Scott Cairney Commerce Server Product Unit

OperationOperation API Message Flow Operation Sequence SequenceOperation Operation Operation Operation Operation Operation Operation Web Browser Mobile Application Etc...Etc... Public API BrokerBroker CS 2007 SQL Server Presentation Application Data Presentation Tools Cloud Services POSPOS

Commerce Entities Encapsulates a single business concept such as a product or a catalog Encapsulates both properties and relationships Can be extended to include new properties and new relationships Supported by Metadata that provides descriptive information about the Commerce Entity that can be retrieved via the API Operations Provides CRUD capabilities on Commerce Entities Consists of 1 or more Operation Sequences May be extended The response of the operation may be extended Operation Sequences Operation Sequences can be plugged/unplugged on a per channel basis. Out of the box Operation Sequences can be replaced by custom ones Operation Sequences are reusable components that can be created and reused on other projects Third parties may create new operations that may be purchased rather than custom built API Extensibility points

18 Operation Based commerce foundation A request can access or manipulate data using one or more of these operations: Query Create Update Delete The general interaction pattern is: 1.Create a request comprising one or more operations on specified items 2.Submit the request to the service for processing 3.Interpret the result returned by the service

19 Operation Based API Operations span all classic Commerce Server subsystems: Catalog Orders Profiles Marketing New operations can be created that communicate with other non-Commerce Server services: Other Microsoft Products Non-Microsoft products Cloud-based Services

20 Extending the API Scott Cairney Commerce Server Product Unit

21 Commerce Server "Mojave" SharePoint commerce services

22 SharePoint Integration Technical Integration Touch Points Search Web Parts Site Map Document Lists Templates Processes Work flow Versioning Approval Publishing Catalog Management Portal Configuration Styling Content Binding CommerceEntity Relationships

23 SharePoint Integration Goals Provide a higher-level experience when producing an e-commerce site If you can “use” SharePoint, you can “use” Commerce Server Components based on logical groups of e-commerce functionality Works in Windows SharePoint Services 3.0; lights up in Office SharePoint Server 2007

24 SharePoint Integration Authentication and User Profiles Commerce Server is authoritative source for authentication and user profile information User Profile Manager (UPM) Membership provider authentication Usable in SharePoint Web Part(s) supplied for account creation and editing of profile information by an end user Forms-based authentication login page supplied for SharePoint (to include password retrieval, etc)

25 SharePoint Integration Out of the Box Web Parts Content Management Property Picker Inline Product Editor Catalog and Navigation Product Content Product Query Results Image Viewer Search Box Search Results Search Paging Store Locator Product Provider Product Filter Site Map Provider Marketing Advertisement List Transaction / Payment Order Details Checkout Baskets & Orders Add to Cart Shipping Cart Mini-cart My Shopper Lists Shopper List Detail Profile Address List Address Detail Credit Card List Credit Card Detail My Profile Registration Wizard Change Password Forgot Password Order History

26 Drill-Down: Web Parts Design Philosophy Minimize Commerce Server calls from similar web parts Concrete example: Product Details Display Identified as most customized page, and recipient of most frequent customizations Optimized using headless controller web part which queries slave concrete UI web parts for required Commerce Server properties for the product being displayed, performs a single Sonora request to retrieve all of the required properties for the product Once properties are retrieved, they are distributed via web part connections Net result: Reduction in Commerce Server API calls Easy for 3rd party developers to build specific UI implementation web parts which “just connect” to Commerce Server without the developer needing to understand detailed Commerce Server mechanics

27 Drill-Down: Web Parts Product Controller Web Part Product Controller Generalistic web part providing the ability to query the Commerce Server catalog based on criteria such as category, property value or full-text search Based loosely on the SharePoint Content Query Web Part Styleable using XSL transforms

28 Drill-Down: Web Parts Customization via XSL Transforms XSL transforms stored in a template Templates may be managed in a document library when the web part is used with SharePoint Allows multiple templates to be built and tested, and applied by a business user

29 SharePoint commerce services Building a Site in 20 Minutes Scott Cairney Commerce Server Product Unit

30 Putting it All Together Base Platform.NET 3.5 SP1, SQL2005 or SQL2008, WSS 3.0 / MOSS 2007 No breaking changes from CS2007 Service Pack 2 to CS In-place upgrade from SP2 Commerce Server “Mojave” availability CTP available now on Connect Complete at end of 2008 Generally Available Q Pricing and Licensing TBD Performance and Scale API aligned to CS2007 SP2 numbers Current result show slightly faster than CS2007, given calling efficiencies SharePoint Web Parts target to CS2007 SP2 +-10%; work in progress Full performance Whitepaper to be published

31

32 Related Content CS2007 Performance Guide: 940C-5D3A679C5526&displaylang=en 940C-5D3A679C5526&displaylang=en 940C-5D3A679C5526&displaylang=en Commerce Server “Mojave” CTP Available on Microsoft Connect Site!! Commerce Server “Mojave” CTP Available on Microsoft Connect Site!! Commerce Blog: MSDN Forum Our Contact Info for any Questions : Ryan Donovan: or Scott Cairney :

With an amazing line up of international speakers, there are even more chances to win an evaluation prize! So make sure you submit feedback for all the sessions you attend! Don’t forget to complete your session feedback forms via the CommNet terminals or the Registered Delegate Pages for your chance to win a HTC Touch Dual! Now extended from 2 to 24 hours after session for more chance to WIN

Tech·TalksTech·Ed Bloggers Live SimulcastsVirtual Labs Developer’s Kit, Licenses, and MORE! Resources for Developers

35 © 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.