Configuring the AEM <-> Workfront Native Connector

[MikeDu2]

Hi there-

Our company is migrating to AEM Cloud from prem, and wants to establish a linked connection b/w AEM Assets and Workfront, through folder taxonomy and metadata.

I need to pass off detailed requirements to my IT team about what configurations need to be made in the AEM platform to facilitate my setup of the Workfront side- IP Whitelisting, etc. Is there one place where it lists what AEM configurations need to be made to do this? So much documentation and videos on Experience League is regarding the deprecated Enhanced Connector. Thanks in advance.

[SureshDhulipudi · Accepted solution]

It is better to start with understanding both APIs.

Please note that developing a custom integration like this requires a good understanding of both systems.

AEM APIs

https://experienceleague.adobe.com/docs/experience-manager-65/content/implementing/developing/introd...

Assets HTTP API

https://experienceleague.adobe.com/docs/experience-manager-65/content/assets/extending/mac-api-asset...

Workfront API :

https://developer.workfront.com/other.html

Workfront Integration: Integrating AEM Assets with Workfront involves setting up a connection between the two systems. This usually involves configuring the Workfront API in AEM and setting up the necessary permissions and workflows in Workfront. You'll need to refer to the Workfront documentation and the AEM documentation for the specific steps.

IP Whitelisting: If your company's network security policies require it, you might need to whitelist the IP addresses of the AEM as a Cloud Service instances in your network firewall. The specific IP addresses will depend on your AEM as a Cloud Service deployment and should be provided by Adobe.

Folder Taxonomy and Metadata: You'll need to set up your folder taxonomy and metadata in AEM Assets to match your requirements in Workfront. This might involve creating custom metadata schemas in AEM and configuring your folders and assets to use these schemas.

[Sujatha_TS]

helpful, thank you!

Is there anything to considered when its applied to templates ? 

we were using enhanced connector - DAM and WF. however recent suggestion was to use native connector and we are testing the same today. 

It seems like its working fine (the DAM linked folders are created) for few templates but few arent working fine. 

Do you recommend any settings at WF level to be taken care at this point ? appreciate any help! thank you!