|
Home > Archive > BizTalk Server Framework > November 2004 > Getting BT 2004 to send a BT Framework Receipt to BT 2002
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 |
Getting BT 2004 to send a BT Framework Receipt to BT 2002
|
|
|
| We are having problems getting BizTalk 2004 to send a Biztalk
Framework Receipt to BizTalk 2002
We have tried many options but have no examples or documentation on
how this should be done.
This is out latest attempt:
1. We have created a Receive Pipeline called RECV-BTF2-POR.
It has in it a BizTalk Framework disassembler with all default
parameters (ie no extra schemas or envelopes added)
2. We have a receive location that picks up from a file and uses
pipeline RECV-BTF2-POR
3. We have an orchestration that is waiting to receive a message
with a particular schema type (called POR). It is bound to the file
receiver in the previous step
4. We drop a file into the revieve location. It contains a SOAP
message
in BTF2 format that contains document of schema POR in its body. This
message comes from a BizTalk 2002 server and we know it is valid
5. We kind of hoped that the pipeline would read the messsage,
send the required receipt and then forward the message in the body to
the
orchestration. Instead it does not send the receipt and raises the
error:
The Messaging engine failed to process a message submitted by
adapter:FILE Source URL:\\ydevsql02\c$\BizTalkFiles\PORXCBL-*.xml.
Details:Could not find a matching subscription for the message. .
This error occurs if the subscribed orchestration schedule or
send port has not been started, or if some of the message propertie
s necessary for subscription evaluation have not been promoted.
Please refer to Health and Activity Tracking tool for more detailed
information on this failure
The HAT displays the 'Message Flow' for the Pipeline as:
'Unparsed Interchange' ..... 4919 bytes
followed by
<a document in the Schema that matches POR> ..... 3657 bytes
followed by
'BTF2DeliveryReceipt' ..... 1373 bytes
6. If we remove the pipeline from the receive location and drop the
same message
the SOAP headers are automatically stripped off, the correct message
is forwarded
to the orchestration all works (except that no receipt is sent)
How should this be configured?
or does any one have an example??
Thanks
Lee
| |
| Christof 2004-06-26, 10:52 am |
| I'm not an BTF expert but...
if you drop a file into a directory, where do you expect the receipt to go
to please?
Isn't this typically done in an HTTP environment?
Best regards,
Christof
"Lee" <lee.connor@trustmarquesolutions.com> wrote in message
news:6ca2bfc1.0406180606.7d31d835@posting.google.com...
> We are having problems getting BizTalk 2004 to send a Biztalk
> Framework Receipt to BizTalk 2002
> We have tried many options but have no examples or documentation on
> how this should be done.
> This is out latest attempt:
>
> 1. We have created a Receive Pipeline called RECV-BTF2-POR.
> It has in it a BizTalk Framework disassembler with all default
> parameters (ie no extra schemas or envelopes added)
>
> 2. We have a receive location that picks up from a file and uses
> pipeline RECV-BTF2-POR
>
> 3. We have an orchestration that is waiting to receive a message
> with a particular schema type (called POR). It is bound to the file
> receiver in the previous step
>
> 4. We drop a file into the revieve location. It contains a SOAP
> message
> in BTF2 format that contains document of schema POR in its body. This
> message comes from a BizTalk 2002 server and we know it is valid
>
> 5. We kind of hoped that the pipeline would read the messsage,
> send the required receipt and then forward the message in the body to
> the
> orchestration. Instead it does not send the receipt and raises the
> error:
>
> The Messaging engine failed to process a message submitted by
> adapter:FILE Source URL:\\ydevsql02\c$\BizTalkFiles\PORXCBL-*.xml.
> Details:Could not find a matching subscription for the message. .
> This error occurs if the subscribed orchestration schedule or
> send port has not been started, or if some of the message propertie
> s necessary for subscription evaluation have not been promoted.
> Please refer to Health and Activity Tracking tool for more detailed
> information on this failure
>
> The HAT displays the 'Message Flow' for the Pipeline as:
>
> 'Unparsed Interchange' ..... 4919 bytes
>
> followed by
>
> <a document in the Schema that matches POR> ..... 3657 bytes
>
> followed by
>
> 'BTF2DeliveryReceipt' ..... 1373 bytes
>
> 6. If we remove the pipeline from the receive location and drop the
> same message
> the SOAP headers are automatically stripped off, the correct message
> is forwarded
> to the orchestration all works (except that no receipt is sent)
>
> How should this be configured?
> or does any one have an example??
>
> Thanks
> Lee
| |
| Jan Eliasen 2004-06-26, 10:52 am |
| Hi
As I hav eunderstood it, the address the receipt should go to is
written in the SOAP-envelope around the document.
Jan Eliasen
On Tue, 22 Jun 2004 19:59:06 +0200, "Christof"
<bts2004communityfeedback (at) hotmail (dot) com> wrote:
>I'm not an BTF expert but...
>if you drop a file into a directory, where do you expect the receipt to go
>to please?
>Isn't this typically done in an HTTP environment?
>
>Best regards,
>Christof
>
>"Lee" <lee.connor@trustmarquesolutions.com> wrote in message
>news:6ca2bfc1.0406180606.7d31d835@posting.google.com...
>
--
Jan Eliasen, representing himself and not the company he works for.
| |
|
| Chrisof
The reason I am picking the reply form a DIR is that I have an ASP
page on a separate web server which spools the responses to a
directory. That way we ensure that the BT server is secure and not
exposed and we get a very easy way to track and archive responses.
The original message is sent via a HTTP send and the response is
collected via a folder drop. I would expect the SOAP header to be
extracted via the pipeline and BT to respond to the sending server via
HTTP.
Lee
"Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in message news:<#MfAeKIWEHA.2840@TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> I'm not an BTF expert but...
> if you drop a file into a directory, where do you expect the receipt to go
> to please?
> Isn't this typically done in an HTTP environment?
>
> Best regards,
> Christof
>
> "Lee" <lee.connor@trustmarquesolutions.com> wrote in message
> news:6ca2bfc1.0406180606.7d31d835@posting.google.com...
| |
|
| I have now solved this issue after speaking to Microsoft.
follow the steps as below...
1) Create a receive port and receive location for the in inbound BTF
document using a pipeline that has a BTF disassembler (lets say our
PORT is call RECV_Doc_BTF2 and the location is called
RECV_Doc_BTF2_File)
2) Create a dynamic send port (lets call it Send_BTF2_Receipts)
3) Add a filter to the dynamic send port using the BTS.ReceivePortName
property and set it to the ReceiveportName created in Step 1 (i.e.
RECV_Doc_BTF2)
This seems to work... it seems locigal as the BTF2 receipt was being
produced but did not have a way to be sent out of the BT2004 server.
Its all a little strange and not very automated!
A little advice is to use the HAT to check the return Receipt and the
URL address the receipt is going to!! I just spent over an hour
wondering why the other server was not getting the receipts, turned
out the response address in the SOAP header was incorrect!
Thanks for your responses...
Lee
lee.connor@trustmarquesolutions.com (Lee) wrote in message news:<6ca2bfc1.0406230049.48acc403@posting.google.com>...[vbcol=seagreen]
> Chrisof
>
> The reason I am picking the reply form a DIR is that I have an ASP
> page on a separate web server which spools the responses to a
> directory. That way we ensure that the BT server is secure and not
> exposed and we get a very easy way to track and archive responses.
>
> The original message is sent via a HTTP send and the response is
> collected via a folder drop. I would expect the SOAP header to be
> extracted via the pipeline and BT to respond to the sending server via
> HTTP.
>
> Lee
>
>
> "Christof" <bts2004communityfeedback (at) hotmail (dot) com> wrote in message news:<#MfAeKIWEHA.2840@TK2MSFTNGP11.phx.gbl>...
| |
|
| What pipeline did should be used for the dynamic send port? Should it be
XMLTrasmit or PassThru?
"Lee" wrote:
> I have now solved this issue after speaking to Microsoft.
>
> follow the steps as below...
>
> 1) Create a receive port and receive location for the in inbound BTF
> document using a pipeline that has a BTF disassembler (lets say our
> PORT is call RECV_Doc_BTF2 and the location is called
> RECV_Doc_BTF2_File)
>
> 2) Create a dynamic send port (lets call it Send_BTF2_Receipts)
>
> 3) Add a filter to the dynamic send port using the BTS.ReceivePortName
> property and set it to the ReceiveportName created in Step 1 (i.e.
> RECV_Doc_BTF2)
>
> This seems to work... it seems locigal as the BTF2 receipt was being
> produced but did not have a way to be sent out of the BT2004 server.
>
> Its all a little strange and not very automated!
>
> A little advice is to use the HAT to check the return Receipt and the
> URL address the receipt is going to!! I just spent over an hour
> wondering why the other server was not getting the receipts, turned
> out the response address in the SOAP header was incorrect!
>
> Thanks for your responses...
>
> Lee
>
>
> lee.connor@trustmarquesolutions.com (Lee) wrote in message news:<6ca2bfc1.0406230049.48acc403@posting.google.com>...
>
|
|
|
|
|