Lack of SSI in AEMaaCS Dispatcher | Community
Skip to main content
T
Tomasz_Sobczyk
Level 2
December 29, 2020
Solved

Lack of SSI in AEMaaCS Dispatcher

  • December 29, 2020
  • 1 reply
  • 27484 views

Reading through the docs for AEM as a Cloud Service for Dispatcher. Obviously there are a lot of limitations imposed there (still working through the "this won't be possible anymore" effects of it. One thing that struck me was this:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/content-delivery/disp-overview.html#local-validation

It seems that the Cloud's Dispatcher doesn't include BASIC! things like support for Server Side Includes... Are there any plans in place to improve this? The docs vaguely mention that in future it could potentially include more modules.... What's the reasoning for not having something as basic as SSI (paired with for example SDI)

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by arunpatidar

I think, this does work now. I checked with local sdk and dispatcher setup. Changes are below

https://github.com/arunpatidar02/aemaacs-aemlab/pull/21/files 

1 reply

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
February 17, 2021

Hi,

I am no expert on AEMaaCS but what I think is the reason for not including everything to AEMaaCS because AEMaaCS is just not a migration to the cloud it is more. e.g. using microservices to do offline processing for assets, changing replication, etc.

There is a lot of feature from traditional AEM has been removed e.g. Campaign, Product etc. and getting added gardually.

 

But you can expore https://sling.apache.org/documentation/bundles/dynamic-includes.html to implement SSI in AEMaaCS if it is not available OOTB.

 

 

Arun Patidar
    T
    Tomasz_SobczykAuthor
    Level 2
    February 18, 2021
    HI Arun, I think you missed the point here a bit. The bundle you mentioned will work ok on AEM as a Cloud. BUT! There is Apache bit to it - a dedicated module needs to be enabled on Apache to get Server Side Includes to work (or alternatively ESI could be turned on in Fastly). None of those currently works on AEM SaaS - which effectively means that it's IMPOSSIBLE right now to do ESI/SSI on what Adobe provides for AEM SaaS. The only option to achieve this right now from what I understand is to set up your own CDN/HTTP server in front of AEM as a Cloud infrastructure and resolve ESI/SSI there - this means extra infra which kind of defeats the purpose of AEM SaaS being a ready to use offering 🙂
      arunpatidar
      Community Advisor
      arunpatidarCommunity AdvisorAccepted solution
      Community Advisor
      August 24, 2022

      I think, this does work now. I checked with local sdk and dispatcher setup. Changes are below

      https://github.com/arunpatidar02/aemaacs-aemlab/pull/21/files 

      Arun Patidar
        Terms & ConditionsAccessibility statement

        Loading footer...