Wanted to read jcr and make the data available on back-end. Kind of caching the data on backend. Is there an object like aemcontext or server context? | Community
Skip to main content
adobecq-venkat
adobecq-venkat
Level 2
March 16, 2020
Solved

Wanted to read jcr and make the data available on back-end. Kind of caching the data on backend. Is there an object like aemcontext or server context?

  • March 16, 2020
  • 1 reply
  • 1201 views

Wanted to read jcr and available to all the components. Is there an object like aemcontext or server context?

 

I wanted to store the data until the server is down/restarted.

In Java sever side, servletxcontext can hold the data and available to all the servlets with access to servletcontext.

I tried the same in AEM, it didnt work.

Please suggest if any such object available which holds the data in the back end.It is like caching.

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 BrianKasingli

How are you using the data stored in the JCR? Assuming that the cached data is exposed via JSON, you can try this strategy.

 

In AEM 6.5, it's suggested that all content should live within the /content folder structure. Knowing this is the case when you are creating a caching strategy with your sling servlet, you can write cached data directly into the /content structure with the servlet validating an expiry date against the target root node. When the criteria are met, then you can re-write and re-publish the /content structure.

 

When deactivating your servlet, you can write some logic to wipe out the data stored in your designated structured data store:

 

protected void deactivate() { cleanup(); }

 

1 reply

BrianKasingli
Community Advisor and Adobe Champion
BrianKasingliCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
August 10, 2020

How are you using the data stored in the JCR? Assuming that the cached data is exposed via JSON, you can try this strategy.

 

In AEM 6.5, it's suggested that all content should live within the /content folder structure. Knowing this is the case when you are creating a caching strategy with your sling servlet, you can write cached data directly into the /content structure with the servlet validating an expiry date against the target root node. When the criteria are met, then you can re-write and re-publish the /content structure.

 

When deactivating your servlet, you can write some logic to wipe out the data stored in your designated structured data store:

 

protected void deactivate() { cleanup(); }

 

    Terms & ConditionsAccessibility statement

    Loading footer...