|
Home > Archive > BizTalk Server Applications Integration > October 2005 > Integrating SharePoint and BizTalk
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 |
Integrating SharePoint and BizTalk
|
|
| Sumit Pilankar 2005-10-13, 6:00 pm |
| Hi all,
I am trying out an orchestration to pick up files from Document Library of a
SharePoint Site
I am using BizTalk Server 2004 and Windows Sharepoint Services. I habe also
installled the WSSLib Adapter.
I tried a sample program to create xml file in BizTalk orchestration and
write it to a SharePoint Doc Lib and it worked very well.
Next I want to reading those files from an orchestration. i have created a
orchestration to read the file and write it as is to a folder.
Steps i have followed are:
1. Create a document library for Source Documents.
2. Created a view called "biztalk" over it and with a filter on status
field.
3. Created a orchestration with a Send and Receive Port and corresponding
process blocks. Also created XSD for input and output messages.
4. Deployed the orchestration.
5. Created a ReceivePort and then a Receive location. In the receive
location, I am using WSSLib Adapter and then specified the Site URL, Folder
Name and View Name.
6. Created a Send Port and set to to WSSLib Adapter and also set the site
and folder url alongwith filename and extension.
7. I binded the orchestration to the ports and enlisted and started it using
BizTalk Explorer.
After this to my surprise or cause of some mistake of mine  , the
orchestration is not able to pick up any file from the SharePoint Doc Lib. I
hope there are no mistake in these steps. If i have missed anything do let
me know. Please help me find out the solution
If anyone can provide a sample project i would be very grateful. Thanks
Sumit Pilankar
| |
| Jan Eliasen 2005-10-13, 6:00 pm |
| On Thu, 13 Oct 2005 11:52:18 +0530, "Sumit Pilankar"
<sumit.pilankar@gmail.com> wrote:
>1. Create a document library for Source Documents.
>2. Created a view called "biztalk" over it and with a filter on status
>field.
>3. Created a orchestration with a Send and Receive Port and corresponding
>process blocks. Also created XSD for input and output messages.
>4. Deployed the orchestration.
>5. Created a ReceivePort and then a Receive location. In the receive
>location, I am using WSSLib Adapter and then specified the Site URL, Folder
>Name and View Name.
>6. Created a Send Port and set to to WSSLib Adapter and also set the site
>and folder url alongwith filename and extension.
>7. I binded the orchestration to the ports and enlisted and started it using
>BizTalk Explorer.
>
>After this to my surprise or cause of some mistake of mine , the
>orchestration is not able to pick up any file from the SharePoint Doc Lib. I
>hope there are no mistake in these steps. If i have missed anything do let
>me know. Please help me find out the solution
Hi
Just to make sure - you want to read a file from wss and write it to a
filefolder? Or another library in sharepoint?
Your write that your send port uses wsslib as transport, but I read
from your posting at the top that you wanted to write the read
document to a file?!?
Anyway, are you using version 2 of the adapter?
--
Jan Eliasen, representing himself and not the company he works for.
| |
| Sumit Pilankar 2005-10-24, 10:32 am |
| Hi Jan
Thank you very much for the reply.
Yes i am using version 2.0 of the WSSLib Adapter.
Also I am trying to write to a WSS Library only, but anyways thats
immaterial for me at this moment, cause I am stuck with reading a file from
SharePoint Library. Once that read part is done, as I have already
successfully implemented another project to write to SharePoint Library, I
should be able to recreate that. I just wanted to be sure that i havent
missed any steps in the project for reading files from SharePoint.
If you could please help me with a tutorial or a sample implementation to
read file from SharePoint.
Thanks once again,
Sumit Pilankar
"Jan Eliasen" <eliasen@nospam.nospam> wrote in message
news:taosk15j10vdejv6j0aa2gesk8p7gs839j@
4ax.com...
> On Thu, 13 Oct 2005 11:52:18 +0530, "Sumit Pilankar"
> <sumit.pilankar@gmail.com> wrote:
>
> Hi
>
> Just to make sure - you want to read a file from wss and write it to a
> filefolder? Or another library in sharepoint?
>
> Your write that your send port uses wsslib as transport, but I read
> from your posting at the top that you wanted to write the read
> document to a file?!?
>
> Anyway, are you using version 2 of the adapter?
>
> --
> Jan Eliasen, representing himself and not the company he works for.
| |
| Jan Eliasen 2005-10-24, 10:32 am |
| On Mon, 17 Oct 2005 08:56:12 +0530, "Sumit Pilankar"
<sumit.pilankar@gmail.com> wrote:
>Also I am trying to write to a WSS Library only, but anyways thats
>immaterial for me at this moment, cause I am stuck with reading a file from
>SharePoint Library. Once that read part is done, as I have already
>successfully implemented another project to write to SharePoint Library, I
>should be able to recreate that. I just wanted to be sure that i havent
>missed any steps in the project for reading files from SharePoint.
>
>If you could please help me with a tutorial or a sample implementation to
>read file from SharePoint.
Well, there are a couple of gotcha's, that I can mention:
1. The folder name that you specify in the receive location is
actually the first name the folder has had. If you have renamed the
document library, then you must specify the old name, because the
adapter creates a string out of the sitename, foldername and view
name. If you have renamed a library, the path does not correspond to
the name of the library anymore.
2. Click on the view, and make sure the document you want to take is
actually in the view
3. Go to BizTalk Administration Console, go to the WSSLIB adapter, go
to the receive handler, and choose properties on that. Enable
debugging, restart the host and see if that gives you any hints?
--
Jan Eliasen, representing himself and not the company he works for.
|
|
|
|
|