Integration between Adobe Target and AEM through Adobe I/O

Avatar

Avatar

rosamart

Avatar

rosamart

rosamart

06-08-2020

Hi there!

 

In our project we are trying to configure the integration between AEM and Target using Adobe I/O, we have followed all steps described in the note

 

https://docs.adobe.com/content/help/en/experience-manager-65/administering/integration/integration-i...

And it looks fine. But when we try to export to Adobe Target an Experience Fragment, we are getting an error

 

Screenshot_1.png

 

We’ve been testing more things and we think the problem lies on Target default workspace.

We have defined the following configuration for the Experience Fragments:

 

Screenshot_2.png

If we try exporting it we get the error on the first screenshot.

In the error.log file we get this:

{"httpStatus":400,"requestId":"yFOYfxyaS11AeybyJnPOKInot1MNYb6C","requestTime":"2020-07-31T11:41:29.155Z","errors":[{"errorCode":"WorkspacesEnabledClient.offerDTO.workspaces","message":"workspaces not enabled for the client","meta":{"workspaces":"invalid"}}]}

 

 

Once we’ve seen this error we’ve tried to delete AEM from the equation so we are testing the integration using the Target API you have available here:

http://developers.adobetarget.com/api/#introduction

 

There we can download a Postman collection to interact with Adobe Target directly:

Screenshot_3.png

The first step is to obtain a JWT token from Adobe IO following this instructions:

https://www.adobe.io/authentication/auth-methods.html#!AdobeDocs/adobeio-auth/master/JWT/JWT.md

 

With this token we can invoke the first service in Postman to obtain the access token for the following service calls:

Screenshot_4.png

We define the global variables used by the Postman requests:

Screenshot_5.png

And now we can retrieve the offers we have on Target, for example:

Screenshot_6.png

But if we try to create a new offer we get the same error that we can see at AEM:

Screenshot_7.png

 

In the previous image we can see we are using the default workspace. In our orject we have 2 workspaces:

Screenshot_8.png

In the integration tab we can see the role configured to ‘Editor’ which it's assigned to several people it’s also OK or that's how it looks:

Screenshot_9.png

 

On the other hand, we’ve tested to create an offer without specifying the workspace in Postman and we could do it (but AEM cannot do it of course).

Screenshot_10.png

Screenshot_11.png

 

Please, can you help us know where the problem is?

I think it’s in at the ‘default Workspace’ but we don’t know what to configure and where. Do any of you know what is happening?

 

PS: 

We’ve realized is that we cannot switch between workspaces in target despite we’ve seen we have 2 workspaces and the user has approver role for both.

We expected to see a selector at the upper right corner of the screen but we can only see the user name and the role… (I don’t know if this is normal).

 

Thanks a lot!

View Entire Topic

Avatar

Avatar

karandhawan

Avatar

karandhawan

karandhawan

26-08-2020

@rosamart  Can you please confirm if your account is provisioned for Target Standard or Target Premium?

From the error, it looks that the Default Workspace could probably not set for your account. You could write an email to Target support (clientcare@adobe.com) for verifying this.

Please also confirm if you are able to export Experience Fragment using the legacy integration?

 

Regards,

Karan Dhawan