Hi,

I am trying to use the Windows SharePoint Services adapter with BizTalk
Server 2006 Beta 2.
Everything works fine when I follow walkthrough #1 where I am able to move
files.

I would like to process the file with an orchestration :
scenario 1 : file will be received from an external application (local
directory at this time) and the orchestration will send this file to a
SharePoint library
scenario 2: file will be received from a SharePoint library and the
orchestration will send this file to an external application (local
directory at this time)

Scenario 1 works fine when I am processing an xml file but I am not able to
process a binary file (currently using a txt file).
I receive the following errors:

-----------------------------------------
Error  ------------------------------------------------------------
Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5778
Date:  2/23/2006
Time:  1:01:41 PM
User:  N/A
Computer: QCMTL111941W2K3
Description:
The Messaging engine failed to process a message submitted by adapter:
FILE Source URL:c:\WSS_SOURCE\*.txt. Details:The published message could
not be routed because no subscribers were found. This error occurs if the
subscribed orchestration schedule or send port has not been started, or if
some of the message properties necessary for subscription evaluation have
not been promoted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

----------------------------------------------------------------------------
--------------------

Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5753
Date:  2/23/2006
Time:  1:01:41 PM
User:  N/A
Computer: QCMTL111941W2K3
Description:
A message received by adapter "FILE" on receive location "ReceiveSourceTxt"
with URI "c:\WSS_SOURCE\*.txt" is suspended.

Error details: The published message could not be routed because no
subscribers
were found. This error occurs if the subscribed orchestration schedule or
send
port has not been started, or if some of the message properties necessary
for
subscription evaluation have not been promoted.

MessageId:  {9A21428D-D211-4A75-91FD-8EC8D83D2DC4}
InstanceID: {26C82030-FB63-4D5E-9A5B-0629E77BB873}

For more information, see
Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-----------------------------------------
Error  ------------------------------------------------------------

I am specifying 'PassThruTransmit' for both the receive location and the
send pipeline in the send port properties since I do not want to alter the
content of the file.

From what I read in the SharePoint adapter I should be able to move files to
and from document library but I do not have a working sample that give me
all the steps I have to perform.

Does anybody has a sample to send a binary file to a SharePoint library ?
Does anybody has a sample to retrieve a binary file from a SharePoint
library ?

Any help / links / reference will be appreciated.

Regards,

Didier

[ Post a follow-up to this message ]

Your orchestration is subscribed to a particular XML schema message and as
a result it's not receiving binary messages. This error message is raised
when BizTalk does not find a subscription for the received message so it
does not know what to do with the message. Your scenario is very simple,
you don't even need an orchestration for this. You can use CBR (content
based routing) with just a receive port and send port that processes
messages received from that receive port. In order to configure the send
port to process the message you need to define a filter ("filter" is
misleading, it's more like a subscription) on the send port . See Filter
tab for that. All WSS adapter properties begin with WSS.In*.   Look at the
documentation to see which properties are promoted, since only promoted
properties can be used for CBR.

If you want to change your orchestration to receive binary messages, you
will have to change the message type (I think it needs to be XmlDocument
.. yeah ...  ... strange) ... and make sure you don't touch the message in
any way that would require BizTalk to load the document in DOM (you can
access context properties but don't access message promoted properties,
don't use the actual message for anything else except message assignment -
don't forget it's a binary message). I think there are improvement in BT'06
in the way it handles binary messages, the approach I described works with
BT'04 as well.

Take a look at this sample as well.
http://objectsharp.com/blogs/matt/a...02/03/3801.aspx

This posting is provided "AS IS" with no warranties, and confers no rights.

Adrian Hamza [MSFT]
http://blogs.msdn.com/ahamza/
My blog on BizTalk 2006
Windows SharePoint Services adapter

--------------------[vbcol=seagreen] 
to[vbcol=seagreen] 
--[vbcol=seagreen] 
"ReceiveSourceTxt"[vbcol=seagreen] 
to[vbcol=seagreen] 

[ Post a follow-up to this message ]

Hi,

Thanks for the reply.

1) I agree the present scenarios are simples and could be done with CBR. But
they are just a proof of concept so orchestration capabilities will be
required.

2) I will try to use XmlDocument for the message.

I will not modify the message (which is binary file).

2a) I will only assign it to an output message for the send requirements.

2b) I will also access the context properties that will drive my decisions
in orchestration.

I will do a follow-up with my results, to share with others.

Didier

"Adrian Hamza [MSFT]" <adrianhamza@online.microsoft.com> wrote in messag
e
news:OgXrQX9OGHA.608@TK2MSFTNGXA01.phx.gbl...
> Your orchestration is subscribed to a particular XML schema message and as
> a result it's not receiving binary messages. This error message is raised
> when BizTalk does not find a subscription for the received message so it
> does not know what to do with the message. Your scenario is very simple,
> you don't even need an orchestration for this. You can use CBR (content
> based routing) with just a receive port and send port that processes
> messages received from that receive port. In order to configure the send
> port to process the message you need to define a filter ("filter" is
> misleading, it's more like a subscription) on the send port . See Filter
> tab for that. All WSS adapter properties begin with WSS.In*.   Look at the
> documentation to see which properties are promoted, since only promoted
> properties can be used for CBR.
>
> If you want to change your orchestration to receive binary messages, you
> will have to change the message type (I think it needs to be XmlDocument
> .. yeah ...  ... strange) ... and make sure you don't touch the message in
> any way that would require BizTalk to load the document in DOM (you can
> access context properties but don't access message promoted properties,
> don't use the actual message for anything else except message assignment -
> don't forget it's a binary message). I think there are improvement in
BT'06
> in the way it handles binary messages, the approach I described works with
> BT'04 as well.
>
> Take a look at this sample as well.
> http://objectsharp.com/blogs/matt/a...02/03/3801.aspx
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Adrian Hamza [MSFT]
> http://blogs.msdn.com/ahamza/
> My blog on BizTalk 2006
> Windows SharePoint Services adapter
>
> -------------------- 
move[vbcol=seagreen] 
> to 
the[vbcol=seagreen] 
if[vbcol=seagreen] 
have[vbcol=seagreen] 
> 
> -- 
> "ReceiveSourceTxt" 
or[vbcol=seagreen] 
necessary[vbcol=seagreen] 
the[vbcol=seagreen] 
files[vbcol=seagreen]
> to 
me[vbcol=seagreen] 
?[vbcol=seagreen] 
>

[ Post a follow-up to this message ]