Integration with Adobe Target | Community
Skip to main content
S
Sb2512
Level 3
April 27, 2022
Solved

Integration with Adobe Target

  • April 27, 2022
  • 2 replies
  • 961 views

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 ?

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 Anish-Sinha

As you might already know, AEM Adobe integration is a two step process-

  1. Creating the IMS configuration - When you create "Adobe IMS Configurations" for AEM and Target integration, the values gets stored at /apps/system/config/com.adobe.granite.auth.oauth.accesstoken.provider.c023ae85-c724-46d5-8512-ef02442ffc78.config
    You can go ahead and create run modes at this location - examples in /libs/system. But as you see this a location for AEM OOTB generated configurations, it is not recommended to do so. You should set it up manually for each environment since this is a one time activity for different environments
  2. Creating the cloud configurations - this resides at location /etc/cloudservices/testandtarget. You cannot create a runmode for this one. You have create cloud configuration for each environment separately as the creds will be different.

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.

2 replies

DEBAL_DAS
DEBAL_DAS
April 27, 2022

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.

    Anish-Sinha
    Adobe Employee
    Anish-SinhaAdobe EmployeeAccepted solution
    Adobe Employee
    April 27, 2022

    As you might already know, AEM Adobe integration is a two step process-

    1. Creating the IMS configuration - When you create "Adobe IMS Configurations" for AEM and Target integration, the values gets stored at /apps/system/config/com.adobe.granite.auth.oauth.accesstoken.provider.c023ae85-c724-46d5-8512-ef02442ffc78.config
      You can go ahead and create run modes at this location - examples in /libs/system. But as you see this a location for AEM OOTB generated configurations, it is not recommended to do so. You should set it up manually for each environment since this is a one time activity for different environments
    2. Creating the cloud configurations - this resides at location /etc/cloudservices/testandtarget. You cannot create a runmode for this one. You have create cloud configuration for each environment separately as the creds will be different.

    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.

      S
      Sb2512Author
      Level 3
      April 27, 2022

      Thank you @anish-sinha @debal_das for your inputs...it helped

        Terms & ConditionsAccessibility statement

        Loading footer...