Alexander_Prikhodko

Re: Understanding /systemalive service logic - Adobe Experience Manager 29-12-2021

@DEBAL_DAS Thanks for the materials.They describe how to configure this service. What about details of what it does? I'm mostly interested in two things:what exactly "GREEN" status means (is it e.g. the status of some specific bundle or component?)what "Framework started" means (the same question, does it mean that some specific bundle(s) or (component(s) have started?)

157

Understanding /systemalive service logic - Adobe Experience Manager 29-12-2021

I came to know that any AEM instance provides a web service with /systemalive path which responds with a JSON object like this:{ "systemStatus": "GREEN", "checks": [ { "check": "Framework Start Ready Check", "status": "GREEN", "details": "Framework started. Start level: 30; Target start level: 20; Framework state: 32" }, { "check": "Services Check", "status": "GREEN", "details": "" } ] }However, I could not find documentation on what exactly the response fields mean and what the logic of their c...

170

Re: Possible sources of offer request parameters - Adobe Target 23-12-2021

I have found the additional source of parameters. They are configured inside Adobe Launch rules, the way it's described at https://experienceleague.adobe.com/docs/platform-learn/implement-in-websites/implement-solutions/target.html?lang=en in "Add parameters" section.

129

Possible sources of offer request parameters - Adobe Target 22-12-2021

I need help to understand how Target determines what parameters to include in the /mbox/json request when getting offers. The exact issue I have seems to be caused by some legacy from people who don't work at the company anymore and left no documentation, so it's quite puzzling.When I check the request in the browser's debugger, I can see:parameters added out of the box, like screenHeight or mboxTimeparameters added by our custom codea few more that come from elsewhereThe ones from the last part...

142

Re: Initializing JS components after loading offers - Adobe Target 21-12-2021

Sorry for the confusion, our at.js version is actually 1.8.2.

148

Re: Custom transformer for exporting Experience Fragments to Target - Adobe Experience Manager 20-12-2021

I have managed to resolve this. In case anyone is interested, here is how it can be done:You should have a rewriter configuration in /apps/{your-site}/config/rewriter/{your-rewriter}The node's "transformerTypes" property should contain pipeline type from the configuration of the TransformerFactory that produces the transformer.The node's "resourceTypes" property should contain the resource type(s) of the Experience fragmet variations you need to export.More information on configuring rewriters:h...

119

Initializing JS components after loading offers - Adobe Target 19-12-2021

We are using Target loaded by Launch and consider using Target's Visual Composer with Experience Fragments exported from AEM. We also have quite a lot of components with custom JS initialization code which will be used in these fragments if we start using them.What is the recommended way of calling this initialization right after an offer with a component is loaded? What event should our code handle to achieve this, if we don't know exactly when the offer will be loaded? Also, what will change i...

162

Custom transformer for exporting Experience Fragments to Target - Adobe Experience Manager 19-12-2021

We are considering using Target's Visual Composer with Experience Fragments exported from AEM. We also have a custom transformer Java class (extending com.adobe.acs.commons.rewriter.ContentHandlerBasedTransformer) used for some of our components' content, and those components may be included in exported fragments if we start using them.It looks like, when a fragment is exported, the transformer is not applied. Also, another processing seems to be applied, and most likely it's jsoup-html-generato...

140

Re: Old JS and CSS served under new name after deployment - Adobe Experience Manager 09-09-2021

Hi @kchaurasiya When the issue was reproduced, we also tried clearing CDN cache. It did help for new visitors, but the ones who visited the site during the issue had the wrong file cached in their browsers already. So I would like to find the root cause of this and prevent it in future.

497

Re: Old JS and CSS served under new name after deployment - Adobe Experience Manager 07-09-2021

Hi @Fanindra_Surat So far we have observed it on Dispatchers and CDN. We haven't yet managed to reproduce it on Publisher on intent, but apparently it does happen there: since Dispatcher has JS with a new name cached, it means it requested it from Publisher after deployment, when Publisher had already generated the new name.

508

Likes from

User

Count

Learn

Documentation

Community

Support

Resources

Adobe account

Adobe