Integrating web applications into an AEM marketing website
summary
Five integration patterns for embedding external web apps into an AEM marketing site are presented with pros and cons and working code on GitHub. Patterns include side‑by‑side subdomains, iframe, bootloader (JS snippet), server‑rendered backend HX API, and a practical backend crawler that periodically requests app pages, uses JSoup to extract HTML snippets and static resources, validates output (size and regex checks), stores assets, generates a cache manifest and delivers the app assets via AEM/dispatcher.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:40Application Integration
- 1:05About CQ
- 1:25What is an application
- 1:57What is interactive content
- 2:24Usability tools
- 2:55Configuration planning tools
- 3:19Calculators
- 3:31Development
- 3:51Why is it complicated
- 4:05Normal production environment
- 4:38Failed deployments
- 5:24Developer experience
- 5:45Expect
- 6:14Failure Analysis
- 6:45Scope Increases
- 7:05Additional Requirements
- 7:34Integration Patterns
- 10:52IFrame
- 13:00Evaluation
- 16:43Summary
- 22:47Copy and paste
- 23:31Maven build
- 24:03Reverse proxy
- 26:48Verify HTML
- 28:33Extract Static Resources
- 30:25Load Static Resources
- 31:19Extract References
- 33:19Post Processing
- 35:21External Content
related talks
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
02mAEM Shorts: Content Reuse and Omnichannel Delivery with AEM
38mSeamless Integration of Experience Manager Assets with Applications
54mAdobe Experience Manager Rock Star: The Headless Challenge
47mCamel and Eye of a Needle: Integration Approaches for SPA-based Micro Frontends
46mThe Past, Present, and Future of Adobe Experience Manager
42mUnleashing Micro Frontends: A Blueprint for Enterprise Growth
02mAEM Shorts: Driving Headless Experiences with AEM