|
Home > Archive > BizTalk Server Orchestration > June 2005 > Posting InfoPath document to Sharepoint via HTTP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Posting InfoPath document to Sharepoint via HTTP
|
|
|
| A couple of questions regarding this configuration:
1. When I want to create a send port that has a transport type of HTTP, in
my orchestration I always have to put a req/resp type of logical port. I
don't really need to return value within the orchestration but I always have
to put a receive shape. What do people normally do with the receive portion,
check for errors or something?
2. I have a WSS site and forms library folder setup. In the send port I set
the authentication to basic and put in the username and password that should
work, but I continue to get an 401 error. What permissions should be set to
be able to http to Sharepoint?
Thanks.
STom
| |
| Stephen W. Thomas 2005-06-20, 8:49 pm |
| Hello.
I have not looked at using HTTP to post messages to Sharepoint. I have
always used the Sharepoint Adapter available on GotDotNet. Have you looked
into that?
You should be able to set up a single Send Shape and then catch the errors.
You might be reusing an existing Orchestration port and it will not let you
change from Request-Response to just a Request. Try creating a new port that
will just send a message with no response.
When using the HTTP Adapter you can use Delivery Notification to catch the
errors returned. So if you get a 500 error the Adapter would return a
Delivery Exception. You can then cast this into a SOAP Exception and get the
Http error details.
I have some samples and labs on my website that shows how to use Delivery
Notification and how to use the Sharepoint Adapter. They might help you.
Just go to http://www.biztalkgurus.com and look under the Hand On Labs
section.
Hope this helps.
Stephen W. Thomas
http://www.biztalkgurus.com
"STom" wrote:
> A couple of questions regarding this configuration:
>
> 1. When I want to create a send port that has a transport type of HTTP, in
> my orchestration I always have to put a req/resp type of logical port. I
> don't really need to return value within the orchestration but I always have
> to put a receive shape. What do people normally do with the receive portion,
> check for errors or something?
>
> 2. I have a WSS site and forms library folder setup. In the send port I set
> the authentication to basic and put in the username and password that should
> work, but I continue to get an 401 error. What permissions should be set to
> be able to http to Sharepoint?
>
> Thanks.
>
> STom
>
>
>
| |
|
| Stephen,
I am currently using the SharePoint adapter but my client said that they do
not want to use anything downloaded from GotDotNet. They want something that
can be supported from Microsoft. Therefore, it doesn't even matter if I can
prove it works, its not supported.
Whenever you have an HTTP send port and you are going to bind it to a
logical orchestration port, that logical port needs to be request/response,
meaning there is a return. This is a new port, so conflicts exist in the
form.
The error I am getting is 401, which is unauthorized. I will look at your
samples though.
Thanks.
STom
"Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
message news:8D5BFDD2-69C3-4F3D-82E8-394F228639AD@microsoft.com...[vbcol=seagreen]
> Hello.
>
> I have not looked at using HTTP to post messages to Sharepoint. I have
> always used the Sharepoint Adapter available on GotDotNet. Have you
> looked
> into that?
>
> You should be able to set up a single Send Shape and then catch the
> errors.
> You might be reusing an existing Orchestration port and it will not let
> you
> change from Request-Response to just a Request. Try creating a new port
> that
> will just send a message with no response.
>
> When using the HTTP Adapter you can use Delivery Notification to catch the
> errors returned. So if you get a 500 error the Adapter would return a
> Delivery Exception. You can then cast this into a SOAP Exception and get
> the
> Http error details.
>
> I have some samples and labs on my website that shows how to use Delivery
> Notification and how to use the Sharepoint Adapter. They might help you.
> Just go to http://www.biztalkgurus.com and look under the Hand On Labs
> section.
>
> Hope this helps.
>
> Stephen W. Thomas
> http://www.biztalkgurus.com
>
>
> "STom" wrote:
>
| |
| Stephen W. Thomas 2005-06-20, 8:49 pm |
| Hello.
The only thing I can think off would be to check the host the isolated
adapter is running under and make sure that user have rights to Sharepoint.
Also, make sure the site you are posting to will allow posts and it not just
set to read only. I would think you would get a different error if this was
the case.
Or, maybe the site you are posting to is running under an Application Pool
that does not have permission to write to sharepoint?
Stephen W. Thomas
http://www.biztalkgurus.com
"STom" wrote:
> Stephen,
>
> I am currently using the SharePoint adapter but my client said that they do
> not want to use anything downloaded from GotDotNet. They want something that
> can be supported from Microsoft. Therefore, it doesn't even matter if I can
> prove it works, its not supported.
>
> Whenever you have an HTTP send port and you are going to bind it to a
> logical orchestration port, that logical port needs to be request/response,
> meaning there is a return. This is a new port, so conflicts exist in the
> form.
>
> The error I am getting is 401, which is unauthorized. I will look at your
> samples though.
>
> Thanks.
>
> STom
> "Stephen W. Thomas" <StephenWThomas@discussions.microsoft.com> wrote in
> message news:8D5BFDD2-69C3-4F3D-82E8-394F228639AD@microsoft.com...
>
>
>
|
|
|
|
|