In our project,we are doing AEM Integration with Adobe Target using Adobe I/O we are able to connect to Target.
Is there any way to package the dev Environment Configuration(AEM Target Configuration ) to other Dev Environment or we need to manually create a AEM target Integration for every environment.
Is there any run mode configuration that we do ?
Solved! Go to Solution.
Views
Replies
Total Likes
As you might already know, AEM Adobe integration is a two step process-
So to summarize, you should create your own configs per environments as this is one time activity and it helps in identifying any connection issue during the setup.
Let me share my project experience, we have done integration between AEM 6.5.10 and Target via Adobe I/O (using Adobe IMS configuration) on QA environment first.
We have created certificate , API Key, Client secret , JSON payload and these all are specific to QA environment.
I came to know that we need to perform similar activity on Production separately.
We haven't created any run mode configuration, provided meaningful name for non-prod environment while creating profiles/workspace for our use case.
As you might already know, AEM Adobe integration is a two step process-
So to summarize, you should create your own configs per environments as this is one time activity and it helps in identifying any connection issue during the setup.
Thank you @Anish-Sinha @DEBAL_DAS for your inputs...it helped
Views
Likes
Replies