I need some assistance in my approach to setting up an orchestration
project.
Here's what I want to do:

1 - Pick up a non-XML document from a directory
2 - "Archive" that file by copying it to another directory in it's
raw/original form
3 - Submit this non-XML document to a web service (which then connects to
databases and does all of the needed processing to add/update records)

The problem is, from what I understand:
- You can only submit documents to web services via orchestrations
- Yet, orchestrations can only process XML files (using passthru pipeline is
not allowed in an orchestration)

I'm not new to BizTalk....just BizTalk 2004.
In BizTalk 2002, I used to accomplish the archiving via a COM+ preprocess
AIC and the submission to a web service via a process AIC (written in .NET,
pretending to be COM+ so BizTalk 2002 could pass off to it, yet .NET so it
can submit to the web service).

I've had no problem setting up receive ports/locations and send ports to
take care of the "archiving" process.
But, getting the non-XML file through an orchestration is where I'm stuck.
As soon as I have a port within my orchestration point to the same directory
as my receive port/location, that bombs out because it's duplicative.
As soon as I drop the receive port/location approach and try to bring the
archiving process into the orchestration, I run into the non-XML inside
orchestration issue.

I could have two seperate processes, one for the archiving and one for the
web service submission, but that seems silly.

Anyone have a better suggestion?

Thanks in advance.

Dan Tharp

[ Post a follow-up to this message ]

Dan - you can pass non-xml to an orchestration. The main thing is to set the
message type correctly.  In your situation you probably want your port_type
message types to be XmlDocument (even thought you are not passing XML - its
really ok as long as you don't actually try to read in the Xml).

I have another approach with a sample here
http://www.masteringbiztalk.com/wik.../>
amples.html
(under samples - passing binary messages with BizTalk).

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
news:%23SKbDBwVFHA.2256@TK2MSFTNGP14.phx.gbl...
>I need some assistance in my approach to setting up an orchestration
>project.
> Here's what I want to do:
>
> 1 - Pick up a non-XML document from a directory
> 2 - "Archive" that file by copying it to another directory in it's
> raw/original form
> 3 - Submit this non-XML document to a web service (which then connects to
> databases and does all of the needed processing to add/update records)
>
> The problem is, from what I understand:
> - You can only submit documents to web services via orchestrations
> - Yet, orchestrations can only process XML files (using passthru pipeline
> is not allowed in an orchestration)
>
> I'm not new to BizTalk....just BizTalk 2004.
> In BizTalk 2002, I used to accomplish the archiving via a COM+ preprocess
> AIC and the submission to a web service via a process AIC (written in
> .NET, pretending to be COM+ so BizTalk 2002 could pass off to it, yet .NET
> so it can submit to the web service).
>
> I've had no problem setting up receive ports/locations and send ports to
> take care of the "archiving" process.
> But, getting the non-XML file through an orchestration is where I'm stuck.
> As soon as I have a port within my orchestration point to the same
> directory as my receive port/location, that bombs out because it's
> duplicative.
> As soon as I drop the receive port/location approach and try to bring the
> archiving process into the orchestration, I run into the non-XML inside
> orchestration issue.
>
> I could have two seperate processes, one for the archiving and one for the
> web service submission, but that seems silly.
>
> Anyone have a better suggestion?
>
> Thanks in advance.
>
> Dan Tharp
>
>

[ Post a follow-up to this message ]

Jon,
THANKS!

I changed both inbound and outbound message types from system.string to
system.xml.xmldocument and then tried it again, but got the following event
log messages when documents were picked up from the receive location:

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5719
Date:  5/12/2005
Time:  10:41:46 AM
User:  N/A
Computer: ECOMMERCE1
Description:
There was a failure executing the receive pipeline:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
Receive Location: " \\ecommerce1\ecommerce\!DanTest\Inbound\
*.*" Reason:
Finding document specification by message type "root" failed. Verify that
the schema is deployed properly.

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5755
Date:  5/12/2005
Time:  10:41:46 AM
User:  N/A
Computer: ECOMMERCE1
Description:
The Messaging Engine encountered an error publishing a batch of "1" messages
to the Message Box database for the transport adapter "FILE". Please refer
to Health and Activity Tracking tool for more detailed information on this
failure and check the endpoint bindings are correctly configured.

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5753
Date:  5/12/2005
Time:  10:41:46 AM
User:  N/A
Computer: ECOMMERCE1
Description:
The "FILE" adapter is suspending a message coming from Source
URL:" \\ecommerce1\ecommerce\!DanTest\Inbound\
*.*". Details:"Error in
accessing the part data or one of its fragments. The part or fragment may
not exist in the database. ".

Event Type: Error
Event Source: BizTalk Server 2004
Event Category: BizTalk Server 2004
Event ID: 5752
Date:  5/12/2005
Time:  10:41:46 AM
User:  N/A
Computer: ECOMMERCE1
Description:
The Messaging Engine has suspended "1" message(s) from adapter "FILE" due to
failures in message processing. Please refer to Health and Activity Tracking
tool for more detailed information on this failure.


So, then I went back into the orchestration and reconfigured the ports:
Inbound - From: Microsoft.BizTalk.DefaultPipelines.XMLReceive To:
Microsoft.BizTalk.DefaultPipelines.PassThruReceive
Outbound - From: Microsoft.BizTalk.DefaultPipelines.XMLTransmit To:
Microsoft.BizTalk.DefaultPipelines.PassThruTransmit

...and, shwing.....everything worked!
I was able to pick up text files, binary files, ANY files I wanted to and
was able to push them out to a send port directory "as-is" (which gets  me
the "archive" functionality).
Now, I'll work on the web service part, which I think I can get.

THANKS for your help!
Dan

"Jon Flanders[MVP]" <jon.flanders@gmail.com> wrote in message
news:elvLpQwVFHA.1508@tk2msftngp13.phx.gbl...
> Dan - you can pass non-xml to an orchestration. The main thing is to set
> the message type correctly.  In your situation you probably want your
> port_type message types to be XmlDocument (even thought you are not
> passing XML - its really ok as long as you don't actually try to read in
> the Xml).
>
> I have another approach with a sample here
> http://www.masteringbiztalk.com/wik...
0Samples.html
> (under samples - passing binary messages with BizTalk).
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
> news:%23SKbDBwVFHA.2256@TK2MSFTNGP14.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Glad to help - I was about to tell you to switch to the PassThroughReceive -
and then I read that part of your message. LOL.  Good luck

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Dan Tharp" <dtharp@NOSPAMPLEASEgdtr.com> wrote in message
news:evYbZuwVFHA.3176@TK2MSFTNGP12.phx.gbl...
> Jon,
> THANKS!
>
> I changed both inbound and outbound message types from system.string to
> system.xml.xmldocument and then tried it again, but got the following
> event log messages when documents were picked up from the receive
> location:
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5719
> Date:  5/12/2005
> Time:  10:41:46 AM
> User:  N/A
> Computer: ECOMMERCE1
> Description:
> There was a failure executing the receive pipeline:
> "Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source: "XML disassembler"
> Receive Location: " \\ecommerce1\ecommerce\!DanTest\Inbound\
*.*" Reason:
> Finding document specification by message type "root" failed. Verify that
> the schema is deployed properly.
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5755
> Date:  5/12/2005
> Time:  10:41:46 AM
> User:  N/A
> Computer: ECOMMERCE1
> Description:
> The Messaging Engine encountered an error publishing a batch of "1"
> messages to the Message Box database for the transport adapter "FILE".
> Please refer to Health and Activity Tracking tool for more detailed
> information on this failure and check the endpoint bindings are correctly
> configured.
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5753
> Date:  5/12/2005
> Time:  10:41:46 AM
> User:  N/A
> Computer: ECOMMERCE1
> Description:
> The "FILE" adapter is suspending a message coming from Source
> URL:" \\ecommerce1\ecommerce\!DanTest\Inbound\
*.*". Details:"Error in
> accessing the part data or one of its fragments. The part or fragment may
> not exist in the database. ".
>
> Event Type: Error
> Event Source: BizTalk Server 2004
> Event Category: BizTalk Server 2004
> Event ID: 5752
> Date:  5/12/2005
> Time:  10:41:46 AM
> User:  N/A
> Computer: ECOMMERCE1
> Description:
> The Messaging Engine has suspended "1" message(s) from adapter "FILE" due
> to failures in message processing. Please refer to Health and Activity
> Tracking tool for more detailed information on this failure.
>
>
> So, then I went back into the orchestration and reconfigured the ports:
> Inbound - From: Microsoft.BizTalk.DefaultPipelines.XMLReceive To:
> Microsoft.BizTalk.DefaultPipelines.PassThruReceive
> Outbound - From: Microsoft.BizTalk.DefaultPipelines.XMLTransmit To:
> Microsoft.BizTalk.DefaultPipelines.PassThruTransmit
>
> ...and, shwing.....everything worked!
> I was able to pick up text files, binary files, ANY files I wanted to and
> was able to push them out to a send port directory "as-is" (which gets  me
> the "archive" functionality).
> Now, I'll work on the web service part, which I think I can get.
>
> THANKS for your help!
> Dan
>
> "Jon Flanders[MVP]" <jon.flanders@gmail.com> wrote in message
> news:elvLpQwVFHA.1508@tk2msftngp13.phx.gbl... 
>
>

[ Post a follow-up to this message ]

Hi,

I'm having a problem on sending non-xml files inside an orchestration...

I'm using xmldocument for message type, passthru pipeline on both send and
receive ports, but I can't get the message to get across the send port:
"Could not find a matching subscription for the message...".

I can't figure out how to do this? I've tried correlation (maybe not the
right way)...

I thought I had this working, but it wasn't being managed by the
orchestration itself, it was being routed due to the property
bts.receivedpipeline on the send port!!
Of course this isn't what I wanted...

Can anyone understand what am I doing wrong? ... or what am I *not doing*...


Thanks,

Joao.

[ Post a follow-up to this message ]

When you are doing non-xml messaging - the subscription for the
orchestration is going to be based on the binding to the receive port only.
Do you have it bound correctly (you can use subscriptionviewer from the sdk
to view this)

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Joao" <Joao@discussions.microsoft.com> wrote in message
news:3BB89795-4371-4E65-B975-FFDCD48D89C3@microsoft.com...
>
> Hi,
>
> I'm having a problem on sending non-xml files inside an orchestration...
>
> I'm using xmldocument for message type, passthru pipeline on both send and
> receive ports, but I can't get the message to get across the send port:
> "Could not find a matching subscription for the message...".
>
> I can't figure out how to do this? I've tried correlation (maybe not the
> right way)...
>
> I thought I had this working, but it wasn't being managed by the
> orchestration itself, it was being routed due to the property
> bts.receivedpipeline on the send port!!
> Of course this isn't what I wanted...
>
> Can anyone understand what am I doing wrong? ... or what am I *not
> doing*...
>
>
> Thanks,
>
> Joao.

[ Post a follow-up to this message ]

That was what I had previously... But if I make the send port receive
messages that come from receive port, I can't use file's information inside
the orchestration, right?!

So you can't use non-xml messages to start an orchestration? Is that it?
Amoung other things, I wanted to send an email with an alert about the
received file. Isn't there any other way?



Thanks,

Joao.

"Jon Flanders[MVP]" wrote:

> When you are doing non-xml messaging - the subscription for the
> orchestration is going to be based on the binding to the receive port only
.
> Do you have it bound correctly (you can use subscriptionviewer from the sd
k
> to view this)
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "Joao" <Joao@discussions.microsoft.com> wrote in message
> news:3BB89795-4371-4E65-B975-FFDCD48D89C3@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

Yes - you can use non-xml messages to start an orchestration.  You don't
want a send port filter - you want the receive port bound to the
orchestration.

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Joao" <Joao@discussions.microsoft.com> wrote in message
news:3C048BCD-A193-451A-905A-C371891F4CD7@microsoft.com...[vbcol=seagreen]
> That was what I had previously... But if I make the send port receive
> messages that come from receive port, I can't use file's information
> inside
> the orchestration, right?!
>
> So you can't use non-xml messages to start an orchestration? Is that it?
> Amoung other things, I wanted to send an email with an alert about the
> received file. Isn't there any other way?
>
>
>
> Thanks,
>
> Joao.
>
> "Jon Flanders[MVP]" wrote:
> 

[ Post a follow-up to this message ]

I'm not sure I'm understanding then... :\

I know I don't want the send port filter.
The receive port is at the orchestration, connected to msg1 (wich is xmldoc
type and has activate=true).

In the SubscriptionViewer I have three entries:
1- [without name]
2- [SendPort] Service= EPM
3- [Activate: Orchestration] Service= XLANG

Is this how it was supposed?


[thanks for your patience :\]

Joao.


"Jon Flanders[MVP]" wrote:

> Yes - you can use non-xml messages to start an orchestration.  You don't
> want a send port filter - you want the receive port bound to the
> orchestration.
>
> --
> Jon Flanders
> http://www.masteringbiztalk.com/blogs/jon/
>
> "Joao" <Joao@discussions.microsoft.com> wrote in message
> news:3C048BCD-A193-451A-905A-C371891F4CD7@microsoft.com... 
>
>
>

[ Post a follow-up to this message ]

That looks good - now that does teh subscription under #3 look like?

--
Jon Flanders
http://www.masteringbiztalk.com/blogs/jon/

"Joao" <Joao@discussions.microsoft.com> wrote in message
news:B548D2CC-BCCE-45BA-82A5-F1CEA47F2ACD@microsoft.com...[vbcol=seagreen]
> I'm not sure I'm understanding then... :\
>
> I know I don't want the send port filter.
> The receive port is at the orchestration, connected to msg1 (wich is
> xmldoc
> type and has activate=true).
>
> In the SubscriptionViewer I have three entries:
> 1- [without name]
> 2- [SendPort] Service= EPM
> 3- [Activate: Orchestration] Service= XLANG
>
> Is this how it was supposed?
>
>
> [thanks for your patience :\]
>
> Joao.
>
>
> "Jon Flanders[MVP]" wrote:
> 

[ Post a follow-up to this message ]