AEM & Adobe Target Integration | Community
Skip to main content
Level 6
August 24, 2025

AEM & Adobe Target Integration

  • August 24, 2025
  • 1 reply
  • 981 views

Hello Community,

We are in the process of setting up the integration between AEM and Adobe Target. Could you please let me know which PIDs I need to use to create OSGi configs so that they are deployed as part of the code? Additionally, there are some existing configs that were created manually. I want to ensure that these existing configurations are not overwritten and that the new config is added as part of the deployment.

 

Security -> Adobe IMS Configurations

Adobe IMS Technical Account Configuration

Cloud Services -> Legacy Cloud Services -> Adobe Target Configurations

 

1 reply

Umesh_Thakur
Community Advisor
Community Advisor
August 25, 2025

for IMS configuration you can use com.adobe.granite.auth.oauth.accesstoken.provider as PID to configure this thru your code I would suggest first configure IMS in your local then from /apps/system copy or move it to your code
cloud configuration for target can be found at /etc/cloudservices/testandtarget path.
same here first configure then move it to code.
for existing configuration you can follow the same but keep filter.xml change with proper mode in mind.
hope this helps

Umesh Thakur

Level 6
August 25, 2025

Thanks for your reply. For the PID com.adobe.granite.auth.oauth.accesstoken.provider, do I also need to add a suffix to the PID, as shown below, to avoid overriding the existing configuration?

com.adobe.granite.auth.oauth.accesstoken.provider-project.cfg.json

Umesh_Thakur
Community Advisor
Community Advisor
August 25, 2025

Yes you can add suffix, in-fact if you add the configuration thru IMS console, you can find a hash string as suffix with the PID so that is alway a good practice to have one with suffix if you are expecting more than one configuration .

Hope this helps

Umesh Thakur