FAQs June 24, 2015- IBM WebSphere Commerce + Adobe Experience Manager = The Ultimate Transformation! (Q- With this integration will AEM always be the "glass" with IBM Commerce being headless (just like you have with lsaticPath) oris there a diferentarchitecture here? Act's the recommended integration approach. But you can use parts ofthe integration also if you pick a different integration approach. To expand on that, ultimately the customers need will dictate the integration pattern that makessense for their implementation. The current out-ofthe-box features assume WC is headless, but can be extended to enable the opposite approach. More out-of the-box integration capabilities are anticipated that include enablement of other implementation patterns. tls there outof-the box support for bi-directional integration as well, ors it always unidirectional -from IBM as commerce to ‘Adobeas experience? Act's like the Elasticpath and Hybris integration. For product data its unédlrectional. But we have seen several installations where projects implemented a bidirectional integration. @ Are there any API docs available for review of this connector? A. Yes, they are available here: http://docs.adobe,com/content/docs/en/aem/6-Lhtm| ‘@ Can you give some technical specifics on how a shopping cart isdisplayedon an AEM page but managed on WCS?Is ita client side NAX call? ‘A:You can either request the price with an AJAX callor you get it on the AEM instance and send the rendered page to the client. ‘Q: Does the IBM connector import product data into the AEM CRX repository? so, to what extent? Just basic product ID/SKU/category metadata (45 fields) or more full representation of product data imported from IBM commerce? ‘Ac We replicate static product data into AEM. Volatile attributes are usually fetched directly. This caching makes the whole authoring ‘experience much smoother as we don't have to rely ona fast connection to WebSphere. It also allows powerful caching with the default AEM architecture, Therefore, it helps you to avoid a lot of unknown issues. ‘Q How is the relationship of PDP templates (managed in AEM) and actual products in WCS managed? & there 21 to 1 mapping between SKU and # of pages in AEM ‘A: Usually, one product is one AEM page. The variants are part ofthe product page. Butt depends on your usecase. The framework allows different ways. When will this be available for us to work within the Package Share? ‘A: This week [June 22, 2015] (Q:Makes sense not to stor pricelinventory in AEM. ‘A: Depends on the use case. If you sell expensive Swiss Watches, these attributes are not volatile. You could also do some price «cachingon the AEM side ‘Q-Are there any components provided with the Commerce Connector? Where can we see what alls included (API reference, scope of included features etc. ‘A: We provide a couple of reference components with the integration. We recommend to look atthe package and the documentation: hhttp'//docsadabe.com/content/dacs/en/aem/é-Lhim| {Qils this search on AEM or real time on WCS? ‘A: QOTB yes. It depends on the project requirements. We provide all the hooks to include any search engine you want to use. Q:Whereis the product detail managed? ‘A:Do you mean product data? This would be managed in WebSphere. ‘what if there was an external search engine in play? How would this work in that scenario? ‘A: We provide all the hooks to include your own search engine. We also provide with Adobe Search + Promote a search engine we included the same way. ‘QiIs this package which was justconfigured (in the demo) provided by Adobe or IBM? ‘A: The integration was built by Adobe and is provided by Adobe, but its also an IBMvalidated integration.(Q:How do you deliver indexed marketing content + indexed product data both in search results? Oris it only product data search from Commerce? ‘A: Depends on your project in theory you have product data and marketing data in AEM. You can use Lucence and Solr for search tls the WC catalog copied into AEM? Orisit referenced in realtime, example: on a product detail page? A Ifyou want to use the catalog 1:1, you could import the information and use it to create the pages. If you use dynamic navigation you would do choose a diferent way. QiIs the catalog stacked and copied over? Is the promotion being configured first on the Commerce side before you can configure content here? ‘A: Depends on your usecase. You can import the catalog structure or use our tools to create your catalogs. You need to setup the promotion first in WebSphere in order to use it in AEM, @All promotions are automatically pulled in by AEM? ‘The framework allows you to access all promotions with details. What you do with it depends on your use-case. In our example we Use it to create this free shipping banner. (Q:This checkout configuration does not make sense when connected to the slide where you showed what would be managed by ‘AEM vs what would continue to be respected as delivered by WSC. ‘A: You can use AEM to render the whole checkout workflow or you could hand it over to IBM. ‘QeJust confirming -showing the integration of AEM to WC- for things like Abandoned Carts, Order History, etc. you have in the Connector created a "shared customer context" between AEM and WC- correct? ‘A: The context hub is NOT integrated with WebSphere in Version 1. just showed what you can do. Q:Will the solution escalate to e-Commerce with more than TMM products catalog and a daily turnover of IK products? ‘A: AEM 6.1is able to handle millions of products Are you stil relying on the strategy of importing acopy of the product catalog from IBM to AEM? Do you need the full product ‘catalog copied from IBM into AEM? ‘A: Depends on your usecase. You can just import product data and create the catalog in AEM. (@ What kind of scale can we promise withthis integration pattem - how many million products and SKUs, how many transactions? ‘Arethere performance benchmarksavailable to back up ths architecturelintegration pattern? ‘A: AEM can scale horizontally, This should help with the transaction volumes. | see the biggest challengearound updating products. f you need to update Im products every day, that could be an issue. ‘how would you rate the "feature richness and completeness" compared to the other existng commerce integrations like Hybris, EP etc? ‘cI would say version 1 covers 60%. (@ How far back is this compatible? 5.6.7 6.0? 6.12? ‘A The integration is tested with 61 Are there any separate cost considerations for this CQ/WCS package/connector? ‘A: The only extra cost isthe Commerce integration Framework for AEM - The Connector works with that ls the Connector a product that is sold by Adobe? Which implies support~or i it anaccelerator“asis" asset? ‘A: The Connector is a"no cost’ download available on Adobe PackageShare. In order to function it requires AEM 61 and the ‘Commerce integration Framework. (Q:How diferent is this from the AEM + HYBRIS platform? ‘8: The Geometrit implementation is very similar to Hybris, but there are some differences.