Hello, guys, I am curious to know how to fully configure the Launch DTM library which we import in our website's pages.
A little background: we have configured our instances to work with Launch through the gateway of Adobe IO. Now, under the chosen /conf path we have these nodes:
While in the configuration panel we have:
I have a series of questions and curiosities and I'd be very thankful if anyone of you could share their knowledge and experience.
They're quite a few, I understand, but I genuinely appreciate the wisdom of people with more experience and indepth than I have.
THE CURIOSITIES I HAVE
1. how come in the configuration I see only Staging and Production, but not the Development library (even though on Launch this has been configured)? If you look at the nodes, it seems like there is a possibility to configure it/retrieve it from Adobe IO, but how?
2. when the library is included, it appears as if AEM includes the staging library on author and the production library on the publish instances. Is this the expected and typical behavior? Can anyone explain the reasoning behind it? In our case, it would make much more sense to have the staging library on the author and publish instances of our staging enviroments (which we specify with the runmodes) and our production library on all the author and publish instances of our production enviroments.
3. and ultimately, my main question is, what do all the properties on that node in the image do? And where are they configured? Is there documentation online I might have missed that details those functionalities? The async property is pretty clear to me, as it's configured in that panel configuration. The archive option appears to be disabled in the panel configuration, and I was wondering how to activate it.
While, on the other hand, I have no idea what archiveEncrypted, enablePollingImporter, useMinified do and - above everything else - where they are configured.
As always, thanks for reading all of it and for sharing your knowledge with the Community,