Core Adobe Expe­ri­ence Man­ag­er Con­fig­u­ra­tions for hybris inte­gra­tion

The AEM Com­merce frame­work is the back­bone for expe­ri­ence-dri­ven com­merce in Expe­ri­ence Man­ag­er. The sys­tem is easy to access via APIs and can be extend­ed for many PIM engines includ­ing hybris. The frame­work sup­ports the fol­low­ing Con­tent func­tions that can be owned by Expe­ri­ence Man­ag­er and pow­ered by PIM engines via APIs:

  1. Cat­a­log Man­age­ment
    1. Prod­uct Importer
      1. Par­tial, Express and Full Imports
      2. Tax­on­o­my cre­ation
    2. Cat­a­log Blue­print­ing
      1. Cat­a­log Tem­plate
      2. Sec­tion Tem­plate
      3. Prod­uct Tem­plate
    3. Cat­a­log Pages
      1. Con­crete Eng­lish Cat­a­log
    4. Prod­uct Edi­tor
    5. Prod­uct Change event across sys­tems
    6. Prod­uct Search
  2. Shop­ping Expe­ri­ence
    1. Cat­a­log pages
    2. Cat­e­go­ry / Sec­tion pages
    3. Add to Cart
    4. Check­out process
  3. Site Expe­ri­ence
    1. Head­er
    2. Foot­er
    3. Mis­cel­la­neous Site Com­po­nents
  4. Per­son­al­iza­tion
    1. Pro­mo­tions & Vouch­ers
    2. Order His­to­ry trait
    3. Cart restora­tion
  5. Mar­ket­ing Cloud Inte­gra­tion
    1. DAM
    2. Tar­get rec­om­men­da­tions
    3. Search & Pro­mote feeds


Adobe Experience Manager and hybris integration diagram

AEM hybris integration

Expe­ri­ence Man­ag­er Con­fig­u­ra­tions

The fol­low­ing con­fig­u­ra­tions should be acces­si­ble from the Felix Con­sole on your Expe­ri­ence Man­ag­er instance:

Hybris OAuth Han­dler

  • Update Client ID from mobile_android to <project_specific_value>
  • Update Client Secret from secret to <project_specific_value>
  • Update Trust­ed Client ID from trusted_client to <project_specific_value>
  • Update Trust­ed Client Secret
  • Update REST end­point. e.g. /rest/v1/ to /b2bocc/v2/

Day CQ Com­merce fac­to­ry for Hybris

  • Update Com­merce provider from hybris to <project_specific_value>

Day CQ Com­merce Hybris Cat­a­log Importer

Day CQ Com­merce Hybris Con­fig­u­ra­tion

  • Switch between Stag­ing or Online val­ues as appro­pri­ate.

Day CQ Com­merce Hybris Con­nec­tion Han­dler

  • Update Base URL val­ue
  • Update user­name
  • Update pass­word
  • Update REST end­point val­ue if hybris OCC v2 API is being used. e.g. /b2bocc/v2/

Day CQ Com­merce Hybris Default Import Han­dler

  • Update DAM path from /con­tent/­dam/­ge­ometrixx-out­doors/prod­uct­s/im­port to /content/dam/<org>/products/import
  • Update Tag name­space from geometrixx-out­doors to <org>
  • Update Cat­e­go­ry page tem­plate from /app­s/­ge­ometrixx-out­doors/tem­plates/­page_­cat­e­go­ry to /apps/<org>/templates/page_category
  • Update Prod­uct page tem­plate from /app­s/­ge­ometrixx-out­doors/tem­plates/­page_prod­uct to /apps/<org>/templates/page_product

Day CQ Com­merce Hybris Default Response Pars­er

Day CQ Com­merce Hybris Polling Cus­tomer Groups Updater

The above con­fig­u­ra­tions can not be sub­sti­tut­ed for a well defined Project Plan, Prod­uct RoadMap or Project Pre-dis­cov­ery items.

The lead Busi­ness Prac­ti­tion­er, Ana­lyst or Archi­tect for the project should cov­er the fol­low­ing areas in-depth before start­ing an Expe­ri­ence Man­ag­er and hybris imple­men­ta­tion.

  1. Project Tax­on­o­my must be defined.
  2. The Prod­uct page should be defined includ­ing pos­si­ble vari­ants
  3. A sand­box envi­ron­ment for hybris should be set­up. This should be dif­fer­ent from the QA hybris instance.
  4. The devel­op­ment machine should be (at the least) Mac with 8GB RAM and SSD.
  5. Define the URL map­ping strat­e­gy, if prod­uct cat­e­gories and cat­a­log cre­ation is dynam­ic.
  6. Define the can­di­date web sites to use the inte­gra­tion, includ­ing any region­al and mul­ti-lin­gual web por­tals.
  7. Iden­ti­fy oth­er Adobe Prod­ucts inte­gra­tion with Expe­ri­ence Man­ag­er & hybris.
  8. Define Prod­uct Launch­es in hybris and Expe­ri­ence Man­ag­er.
  9. Iden­ti­fy the usage of proxy pages, if need­ed, in Expe­ri­ence Man­ag­er for prod­uct pages.
  10. Review exist­ing Expe­ri­ence Man­ag­er infra­struc­ture to make sure AEM Com­merce can be sup­port­ed.
  11. Rede­fine Expe­ri­ence Man­ag­er Con­tent mod­el, as we have now cat­a­logs along with AEM Sites and AEM Assets.
  12. Iden­ti­fy work­flows to sup­port cus­tom hybris inte­gra­tion.

Addi­tion­al doc­u­men­ta­tion (docs​.adobe​.com) and arti­cles can be found in the AEM Help Forum (https://​helpx​.adobe​.com/​m​a​r​k​e​t​i​n​g​-​c​l​o​u​d​/​e​x​p​e​r​i​e​n​c​e​-​m​a​n​a​g​e​r​.​h​tml)