If I understand correctly, number of targeted profile attribute and experiences mapped to them are too many, and that is why you are not comfortable driving these variations with dedicated audience. If you are not building dedicated audience, you can create single qualifying audience and put the var...

Can you provide some expected issues that we might run into.

@Brian_Johnson_ Intent is to send data to two different set of reporting suites in two different org's. One currently in place, implemented via Launch is focused towards tracking experience on the web property only. There is another parent exp (lets called is Exp A), from which the user can navigate...

Can we have 2, AA instances running on the same page. One AA is being hosted by Tealium and another one from Launch.

You were right, value for Auth was not correct. Fixed it, and was able to connect. Thanks for your help !!

I did create a namespace and was able to download the config file. Updated the ".wskprops" as shown in the attached screenshot. But still, continue to get the same error  

 I am trying to set up the IO runtime dev environment locally. Directions here state that I need to setup a ".wskprops"file with following details :AUTH=<Your UUID>APIHOST=adobeioruntime.net NAMESPACE=<Your namespace>What should be Auth variable set to ? I understand that this is basic authenticatio...

What you are trying to run is the API jar, not the AEM standalone jar and that is why it is not executing. Download the standalone jarand that would run.

AEM is restful in nature and if you are relying on HTTP SESSION, then you are breaking the restful nature of AEM. You'll also not able to cache anything that is HTTP SESSION dependent.So to use HTTP SESSION inside AEM is strongly NOT advisable.Having said that, just to resolve your issue. You are se...

6.2 deprecates client context and you should use context hub instead.