Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Hi,
I am trying to integrate Salesforce with AEM 6.0 as per this link:
http://docs.adobe.com/docs/en/aem/6-0/administer/integration/third-party-services/salesforce.html
But I am getting this error:
18.03.2015 12:01:40.181 *ERROR* [JobHandler: /etc/workflow/instances/2015-03-18/model_163017207920287:/home/users/geometrixx-outdoors/aaron.mcdonald@mailinator.com/profile] com.adobe.granite.workflow.core.job.JobHandler Process execution resulted in an error
com.adobe.granite.workflow.WorkflowException: Process execution resulted in an error
at com.adobe.granite.workflow.core.job.HandlerBase.executeProcess(HandlerBase.java:218)
at com.adobe.granite.workflow.core.job.JobHandler.process(JobHandler.java:140)
at org.apache.sling.event.jobs.JobUtil$1.run(JobUtil.java:365)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
I read the previous discussions but I didn't get that what could be the setting for Day Commons HTTP Client 3.1. I also tried using SSL enabled proxy https://127.0.0.1:5433/libs/cq/workflow/content/console.html.
I have attached the screenshot of error.log and Day Commons HTTP Client 3.1.
Any reply will be great help.
Regards,
Sandeep Sahu
Gelöst! Gehe zu Lösung.
Zugriffe
Antworten
Likes gesamt
https://chrome.google.com/webstore/detail/rest-console/cokgbflfommojglbmbpenpphppikmonn?hl=en link shows you a rest client that allows oauth. Basically oauth is sent via a header and all clients allow that. WRT your actual issue, IIUC, you have been using the OOB feature as Scott mentioned, please raise a ticket with the logs and a package which can be used to replicate the issue.
Zugriffe
Antworten
Likes gesamt
Hi Sandeep,
You are receiving this exception while doing PUT operation to Salesforce. Please ensure that the integration user which you are using to connect to salesforce has the rights to do PUT operation.
Zugriffe
Antworten
Likes gesamt
Please review this step by step guide and troubleshooting tips in the bottom
http://www.intelligrape.com/blog/integrating-salesforce-with-cq5/
Are you able to connect to sales force from Tools->Cloud Services->Salesforce.
Zugriffe
Antworten
Likes gesamt
If you are following docs and getting this error, please open a ticket. The procedure in the docs should not lead an an exception.
Zugriffe
Antworten
Likes gesamt
yes I am able in doing that. But still getting that jobhanddler error
Zugriffe
Antworten
Likes gesamt
I am using this node to send to salesforce as lead "/home/users/geometrixx/carlene.j.avery@mailinator.com/profile"
Zugriffe
Antworten
Likes gesamt
I referred that link many times but that error still exists.
Zugriffe
Antworten
Likes gesamt
How will get to know whether particular user has right to put or not???
Zugriffe
Antworten
Likes gesamt
sandeep.a.sahu .. Try using RESTClient from any of your browsers(firefox or chrome) and put file directly to the salesforce end point. Please let me know if that works.If it doesnt, then issue is in access rights to salesforce.IF you could submit successfully, then we can analyse issue in AEM.
Zugriffe
Antworten
Likes gesamt
Thank for replying. I tried doing that, I am getting access token in session cookie successfully. But Salesforce needs OAUTH authorization for posting or getting results, so I was not able to do that by RESTClient. And after getting access token in cookie, the workflow goes into STALE state and gives the same jobhandler error when I started the OOB workflow for posting leads into salesforce. Or please suggest me how to do oauth in salesforce.
Zugriffe
Antworten
Likes gesamt
https://chrome.google.com/webstore/detail/rest-console/cokgbflfommojglbmbpenpphppikmonn?hl=en link shows you a rest client that allows oauth. Basically oauth is sent via a header and all clients allow that. WRT your actual issue, IIUC, you have been using the OOB feature as Scott mentioned, please raise a ticket with the logs and a package which can be used to replicate the issue.
Zugriffe
Antworten
Likes gesamt
sandeep.a.sahu wrote...
Thank for replying. I tried doing that, I am getting access token in session cookie successfully. But Salesforce needs OAUTH authorization for posting or getting results, so I was not able to do that by RESTClient. And after getting access token in cookie, the workflow goes into STALE state and gives the same jobhandler error when I started the OOB workflow for posting leads into salesforce. Or please suggest me how to do oauth in salesforce.
I am facing the same issue, Is there a resolution available for this issue??
Zugriffe
Antworten
Likes gesamt
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten