Hi Derrick,
I've seen similar when doing an HTTP GET. Every time it's because I've forgotten that a "feature" of B2Bi is that if you have a PrimaryDocument it will append it like POST data to the HTTP GET request, which of course is not supported. What you should do is Assign PrimaryDocument to another area of ProcessData (assuming you'll need it again after the GET) and then use the Release service to get rid of PrimaryDocument before using the HTTP Client GET service e.g:
<assign name="Assign" to="myDoc" from="/ProcessData/PrimaryDocument/@SCIObjectID"></assign>
<operation name="Release Service">
<participant name="ReleaseService"/>
<output message="outmsg">
<assign to="TARGET">/ProcessData/PrimaryDocument</assign>
<assign to="." from="*"></assign>
</output>
<input message="inmsg">
<assign to="." from="*"></assign>
</input>
</operation>
Best regards,
Richard.
------------------------------
RICHARD CROSS
------------------------------
Original Message:
Sent: Wed May 22, 2019 12:45 PM
From: Derrick Dantzler
Subject: Using IBM Sterling B2B to call Microsoft Sharepoint API's
Hi,
I'm currently working on a project where I've create a business process to call Sharepoint APIs to create folders, files and get folder information. It's working mostly when I use the HTTP Client Post service. But when I call an API that uses HTTP Client Get service I'm getting 403-Forbidden errors. I've confirm that the HTTP headers look good and are identical to the Postman call. It works in Postman but not from SI.
I was just wondering if anybody else has encountered errors like this and if you have found a resolution?
Derrick
------------------------------
Derrick Dantzler
------------------------------
#B2BIntegration
#SupplyChain