Successfully reported this slideshow.
1 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSDAY CQ integration with ATG10.x.x
3© Sapient Corporation 20132 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSTable of Contents1....
5© Sapient Corporation 20134 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSAdobe as a CMS prov...
7© Sapient Corporation 20136 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSApproach for Conten...
9© Sapient Corporation 20138 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSD - Use CQ search a...
DAY CQ integration with ATG 10.x.x
Upcoming SlideShare
Loading in …5
×

DAY CQ integration with ATG 10.x.x

3,197 views

Published on

In today’s fast-paced, changing markets, brands cannot afford long waits for their web presences. With top dollars being invested by organizations to promote their sales via all possible channels, there is a definitive need to have seamless integration between ecommerce and CMS systems, while keeping in consideration the application performance and unified user experience across all channels.

In this paper, Vikrant Shirbhate, Senior Associate Platform L2, will discuss some of the options available for integrating the ATG/Endeca ecommerce solution with the Adobe Day CQ CMS.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

DAY CQ integration with ATG 10.x.x

  1. 1. 1 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSDAY CQ integration with ATG10.x.x
  2. 2. 3© Sapient Corporation 20132 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSTable of Contents1. Introduction 3a) Audience 3b) The Problem 3c) Assumption 3d) DAY CQ Overview 3e) ATG Overview 32. Day CQ: ATG/Endeca Approaches 4a) Migrate (one-time and ongoing) content metadata from CQ into ATG 5b) Migrate (one-time and ongoing) content metadata from CQ into ATG and from ATG to Endeca 6c) Migrate (one-time and ongoing) content metadata from CQ into Endeca 7d) Use CQ search along with Endeca experience manager (no metadata migration) 83. Data Sheet 94. Conclusion 9DAY CQ integration with ATG10.x.xDAY CQ OverviewDay CQ is a web content management software (CMS). It hastwo logical divisions: authoring for content management andpublishing for content delivery.The authoring portion is the environment that the contentauthors input contents, administrate the entire system,configure layout and design of content, and create workflowsto activate (or publish) content.Replication agents in the author environment are used topublish the content and functionality from the author to thepublish instance. The content to be published is packaged andplaced in the replication queue in the author environmentand the content is then received and published.The publishing portion is the customer-facing environment,which holds the content changes after a successful publishingcycle.For performance optimization, it is possible to convertdynamically published content (excluding any personalizedparts) to static HTML, serviced by a static web server.Static web servers are very simple, but fast. Examplesinclude Apache and IIS. The dispatcher can then be used inconjunction with the web server to realize an environmentthat is both fast and dynamic and with moderate hardwarerequirements.ATG OverviewATG Ecommerce provides an open, server-side environmentfor building and deploying dynamic, personalized applicationsfor the web and other communication channels, such asemail and wireless devices. With ATG 10.1.x, Oracle hasprovided OOB ATG integration with Endeca for indexing allProduct Catalog data into Endeca.ATG’s content capabilities (BCC/ATG merchandising tool)offer the basic features of a CMS with enough features tocomplement the online site with basic content managementneeds. However, it is not feature-rich enough to replace theCMS in an enterprise with heavier CMS needs.With organizations investing large sums on rich mediacontent for campaigns and interactive promotions, ATGintegration with CMS platforms is necessitated to create asuccessful user experience, and a multitude of factors governthe integration of ATG with a CMS platform to deliver a first-hand user experience.1. IntroductionIn today’s fast-paced, changing markets, brands cannotafford long waits for their web presences. With top dollarsbeing invested by organizations to promote their sales via allpossible channels, there is a definitive need to have seamlessintegration between ecommerce and CMS systems, whilekeeping in consideration the application performance andunified user experience across all channels.In this paper, I will discuss some of the options available forintegrating the ATG/Endeca ecommerce solution with theAdobe Day CQ CMS, in order to provide a flexible, reliable,and scalable digital commerce platform.AudienceIt is my hope that ATG solution/technical architects andengagement leads will find some clarity and answers withinthis document.The ProblemIf you are like most ecommerce businesses today, youhave two systems: one for ecommerce and the other forcontent assets. If this is not handled in an efficient andseamless manner, it can turn into a maintenance nightmarefor retailers. And not only that, it can also negate the endusers’ experiences and significantly water down the revenuegeneration. Because of this, there is a compelling needfor seamless and instantaneous integration between theecommerce and CMS systems.AssumptionIn order to arrive at a usable solution to this problem, thecontent creation and management will be owned by CQ,and ATG/Endeca will provide the user-interfacing layer of theapplication.Author — Vikrant ShirbhateVikrant has over nine years of experience indriving complex and multi-functional projects inclose coordination with global and local sponsorsforleadingclientsinecommercedomains.Vikranthas worked extensively on ecommerce packagedesign implementation along with enterprisesearch engine customizations.
  3. 3. 5© Sapient Corporation 20134 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSAdobe as a CMS provides the entire framework to manageand deliver content. Its content delivery capabilities alsocover the ability to manage page templates (or layouts)and widgets on pages. Given that Endeca provides similarfunctionality, CQ will be used as a content provider and thecombination of ATG and Endeca will be used to author pagesand page components.There are four ways to integrate CQ with ATG and Endeca aslisted below, assuming CQ will still be used as the overall CMS,and after all the content is approved and published in CQ,it will be displayed on the website. Given that CQ will exist2. Day CQ: ATG / Endeca Approachesalong with the other systems, content will not be migratedinto ATG/Endeca, as that can create unnecessary redundancyand the need to synchronize multiple systems.a) Migrate (one-time and ongoing) content metadata fromCQ into ATGb) Migrate (one-time and ongoing) content metadata fromCQ into ATG and from ATG to Endecac) Migrate (one-time and ongoing) content metadata fromCQ into Endecad) Use CQ search along with Endeca experience manager(no metadata migration)Approach for Content MigrationOne timeIn the one-time migration, all CQ metadata contents will benavigated and all content item metadata information will betransferred to the ATG content repository.OngoingIn the ongoing migration, only revised CQ metadata contentswill be navigated and a select set of content item metadatainformation will be transferred to ATG.ATG/CQ Integration Approach1. One timeCreate a scheduler that will call full update () method presentin ATG CRX repository browse component to navigate to CRXand retrieve a sample set of attribute values for all contentitems (pages in CQ) including the:• Title of the content item (page)• Tags that are associated with a content item• Language that the content is written in• Content alias to be used with content item• Segments with which content item is associated• Page title of the content item (page)• Navigation title, which is often shorter than the full title,for the content item within the navigation map• Subtitle for use on the content item (page)• Description containing more information about thecontent item• Absolute path of the content item in the CRX repository2. OngoingAn event listener should be created, which will listen to theauthor and publishing event and will use a partial update ()method present in the CRX repository browse component.XML documents would be used to upload the contentmetadata into the ATG repository These XMLs can begenerated by any CMS, as a part of a workflow or an eventlistener.3. DetailsThe ATG scenario rule manager functionality will use theabove set of attributes to create the targeter. In addition,content paths retrieved based on the ATG scenario rulemanager are used for fetching content from the publish CQ.A - Migrate (one-time and ongoing) content metadata from CQ into ATG
  4. 4. 7© Sapient Corporation 20136 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSApproach for Content MigrationOne timeIn the one-time migration, all CQ metadata contents will benavigated and all content item metadata information willbe transferred to the ATG content repository. From the ATGcontent repository, content items will be migrated to Endeca.OngoingIn the ongoing migration, only revised CQ metadata contentswill be navigated and a select set of content item metadatainformation will be transferred to ATG. From the ATG contentrepository, select content items will be migrated to Endeca.ATG/CQ Integration Approach1. One timeCreate a scheduler that will call full update () method presentin ATG CRX repository browse component to navigate tothe CRX repository, which will be stored in the ATG contentrepository.2. OngoingAn event listener should be created, which will listen to theauthor and publishing event and will use a partial update ()method present in the CRX repository browse component.3. DetailsThe ATG repository CQ contents will be indexed into Endeca.In the Endeca experience manager, a targeter cartridge willbe created.Based on rules present in the cartridge (the ATG scenariomanager rule is optional), a set of content paths will beretrieved from the Endeca index. The contents path retrievedwill be used for fetching content from the publish CQ.B - Migrate (one-time and ongoing) content metadata from CQ into ATG and from ATG to EndecaApproach for Content MigrationOne timeIn the one-time migration, all CQ metadata contents will benavigated and all content item metadata information will betransferred to Endeca.OngoingIn the ongoing migration, only revised CQ metadata contentswill be navigated and a select set of content item metadatainformation will be transferred to Endeca.ATG/CQ Integration Approach1. One timeCreate a scheduler that will call full update () method presentin the search engine indexing component to navigate to theCRX repository, which will be stored in Endeca.2. OngoingAn event listener should be created, which will listen to theauthor and publishing event and will use a partial update ()method present in the search engine indexing component.3. Details:In this approach, the Day CQ publish repository will bebrowsed and metadata (like the title and tags), along with thecontent path, will be stored within Endeca.Create the cartridge in the Endeca experience manager. Thecartridge will use the Endeca index and a set of content pathswill be retrieved from the Endeca index. Rules will be createdwithin the cartridge. The contents path retrieved will be usedfor fetching content from the publish CQ.C - Migrate (one-time and ongoing) content metadata from CQ into Endeca
  5. 5. 9© Sapient Corporation 20138 © Sapient Corporation 2013DAY CQ integration with ATG 10.x.xIDEA ENGINEERSD - Use CQ search along with Endeca experience manager (no metadata migration)<CQservername>:<cqpublishport>/bin/querybuilder.json?group.1_property=jcr:content/jcr:title&group.1_property.value=shirtproduct&group.p.or=true&group.2_property=jcr:content/cq:tags&group.2_property.value=saks:men3. Data SheetMigrate (one-time and ongoing)content metadata from CQ intoATGMigrate (one-time and ongoing)content metadata from CQ intoATG and from ATG to EndecaMigrate (one-time and ongoing)content metadata from CQ intoEndecaUse CQ search along with Endecaexperience manager (no metadatamigration)Software CQ 5.5ATG 10.1.xCQ 5.5Endeca 6.3ATG 10.1.xEndeca experience manager(XM)3.1CQ 5.5Endeca 6.3ATG 10.1.x (optional)Endeca experience manager (XM)3.1CQ 5.5Endeca 6.3ATG 10.1.x (optional)Endeca experience manager (XM)3.1Scenario rulemanager /PersonalizationATG Preferably XM but can be achievedby ATG alsoXM XMComponentneeds to becreatedATGCRXRepository BrowseComponent-component to pushmetadata contents into ATGrepositoryATGa) CRXRepository BrowseComponent- component topush metadata contents intoATG repositoryb) Component to push CQmetadata contents to EndecaEndecaExperience manager cartridgeCQSearch Engine indexingcomponent- component to pushcontents from CQ to Endeca (usingCAS service)EndecaExperience manager cartridgeEndecaExperience manager cartridgePros Personalization will be controlledfrom ATG1) Personalization will becontrolled from ATG2) Endeca Search features likerelevance, ranking canbe utilized whilst displayingcomponent on webpage.1) In this case, personalizationwill be achieved usingexperience manager cartridge.2) Endeca Search features likerelevance, ranking canbe utilized whilst displayingcomponent on webpage.1) In this case, personalizationwill be achieved usingexperience manager cartridge.2) Metadata content don’t needto be stored into ATGrepository3) Incase content changes aretoo frequent, this approach isrecommended.Cons 1) CQ Repository needs to bebrowsed and event listenerneeds to provide updatedcontents to ATG.2) Endeca Search features likerelevance, ranking can’tbe utilized whilst displayingcomponent on webpage.1) Repository needs to bebrowsed and event listenerneeds to provide updatedcontents to ATG.2) Incase content changes are veryfrequent, there will be delay inactual content display onwebsite pagesRepository needs to be browsedand event listener needs toprovide updated contents toEndeca.Endeca and day CQ will be tightlycoupled.4. ConclusionWhen trying to determine the system architecture for yourcompany’s integration between ecommerce channels andCMS systems, there are multiple factors that come into play.And while a one-size-fits all approach would be ideal, no suchsilver bullet exists.A combination of business use cases and non-functionalrequirementsshouldbeusedtodefinethesystemarchitecturebased on the above approaches — or a hybrid approach canbe formulated to overcome any shortfalls. Only then will yoube able to find the right digital commerce platform that worksfor you and your business.Approach for Content MigrationIn this approach, no one-time or ongoing migration is needed.ATG/CQ Integration Approach1. One timeNot applicable.2. OngoingNot applicable.3. DetailsIn this approach, the component will be created in CQ andthe Endeca experience manager will use the CQ selectorsearch component to retrieve contents. Those contents willbe created and managed within CQ. Use the out-of-the-boxCQ json component (i.e., querybuilder.json). For example,content search will accept a set of parameters such as tags,title, or segments. The output of the json search componentwill be json results consisting of a list of content paths. Asample json query wherein the title = shirtproduct and tagsvalue = saks:men is as follows:EndecaThe Endeca experience manager cartridge will accept valuesfor search attributes (e.g., tag ID). While displaying thecartridge, a CQ search selector request will be submitted andwill return a list of content paths wherein particular searchcriteria is matched. Based on content paths, respectivecontents can be retrieved from Day CQ on a webpage.

×