|
Home > Archive > BizTalk Server Orchestration > January 2005 > Reliable Receipt processing problem
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 |
Reliable Receipt processing problem
|
|
|
| I’m trying to setup a simple document transfer using HTTP and Reliable
Receipts between two BizTalk 2004 servers (Server1 and Server2). Server1 is
receiving the reliable receipt but it seems that it is not matching the
receipt to the original message and thus the status of the original message
eventually becomes "Suspended". The message seems to be delivered fine to
Server2, and Server2 seems to be sending the Reliable Receipt without any
problem to Server1. In HAT on Server1, under "Messages received in past day"
I can see the "Unparsed Interchange" for the reliable receipt.
Would anyone have any idea why the receipt is not being processed correctly?
Here is what I’ve created:
* Server1 *
Orchestration1:
ReceivePort -> Receive_1 -> ConstructMessage (uses a simple map) -> Send_1
-> SendPort
ReceivePort properties:
One-Way Receive Port
Transport: FILE
URI: C:\FileToSend\*.xml
Receive Pipeline: ...DefaultPipelines.XMLReceive
SendPort properties:
One-Way Send Port
Transport: HTTP
URI: http://Server1/HTTPReceive/BTSHTTPReceive.dll
Send Pipeline: SendPipeline1
SendPipeline1:
BizTalk Framework assembler:
Add processing instructions text: [blank]
Add XML declaration: True
Delivery receipt address: http://Server1/HTTPReceive/BTSHTTPReceive.dll
Delivery receipt address type: biz:httpURL
Delivery receipt send by time: 30
Destination address: Partner1
Destination address type: biz:OrganizationName
Document schemas: [blank]
Document topic: http://www.mycompany.com/topic/file.xml
Envelope schemas: BTF2Schemas.btf2_envelope
Generate delivery receipt request: True
Message time to live (in minutes): 30
Processing instructions: Append
Source address: My Company
Source address type: biz:OrganizationName
Target charset: (None)
HTTP_ReceivePort:
No map applied
HTTP_ReceiveLocation:
Transport Type: HTTP
URI: /HTTPReceive/BTSHTTPReceive.dll
Receive Handler: BizTalkServerIsolatedHost
Receive Pipeline: ...DefaultPipelines.XMLReceive
* Server2 *
Orchestration1:
ReceivePort -> Receive_1 -> Send_1 -> SendPort
ReceivePort properties:
One-Way Receive Port
Transport: HTTP
URI: /HTTPReceive/BTSHTTPReceive.dll
Receive Pipeline: ReceivePipeline1
SendPort properties:
One-Way Send Port
Transport: FILE
URI: C:\ReceivedFile\%MessageID%.xml
Send Pipeline: ...DefaultPipeline.XMLTransmit
ReceivePipeline1:
BizTalk Framework disassembler:
Allow unrecognized message: False
Document schemas: MySchemas.MySchema1
Envelope schemas: BTF2Schemas.btf2_envelope
Validate document structure: False
Dynamic_SendPort:
Dynamic One-Way Send Port
Send Pipeline: ...DefaultPipelines.PassThruTransmit
Filter: "BTS.ReceivePortName" == (the full name of the deployed
Orchastration1 receive port)
No map applied
Regards,
Ron
| |
| Todd_Uhl 2004-11-28, 8:46 pm |
| Ron,
Are there any errors in the Application Event log? Usually you will get a
more descriptive error in there. Perhaps I read over your post incorrectly,
but it appears that you are just sending an envelope back as a receipt, and
not a document as well?
Todd Uhl
http://www.geekswithblogs.net/toddu
"Ron" wrote:
> I’m trying to setup a simple document transfer using HTTP and Reliable
> Receipts between two BizTalk 2004 servers (Server1 and Server2). Server1 is
> receiving the reliable receipt but it seems that it is not matching the
> receipt to the original message and thus the status of the original message
> eventually becomes "Suspended". The message seems to be delivered fine to
> Server2, and Server2 seems to be sending the Reliable Receipt without any
> problem to Server1. In HAT on Server1, under "Messages received in past day"
> I can see the "Unparsed Interchange" for the reliable receipt.
>
> Would anyone have any idea why the receipt is not being processed correctly?
>
> Here is what I’ve created:
>
> * Server1 *
>
> Orchestration1:
> ReceivePort -> Receive_1 -> ConstructMessage (uses a simple map) -> Send_1
> -> SendPort
>
> ReceivePort properties:
> One-Way Receive Port
> Transport: FILE
> URI: C:\FileToSend\*.xml
> Receive Pipeline: ...DefaultPipelines.XMLReceive
>
> SendPort properties:
> One-Way Send Port
> Transport: HTTP
> URI: http://Server1/HTTPReceive/BTSHTTPReceive.dll
> Send Pipeline: SendPipeline1
>
> SendPipeline1:
> BizTalk Framework assembler:
> Add processing instructions text: [blank]
> Add XML declaration: True
> Delivery receipt address: http://Server1/HTTPReceive/BTSHTTPReceive.dll
> Delivery receipt address type: biz:httpURL
> Delivery receipt send by time: 30
> Destination address: Partner1
> Destination address type: biz:OrganizationName
> Document schemas: [blank]
> Document topic: http://www.mycompany.com/topic/file.xml
> Envelope schemas: BTF2Schemas.btf2_envelope
> Generate delivery receipt request: True
> Message time to live (in minutes): 30
> Processing instructions: Append
> Source address: My Company
> Source address type: biz:OrganizationName
> Target charset: (None)
>
> HTTP_ReceivePort:
> No map applied
> HTTP_ReceiveLocation:
> Transport Type: HTTP
> URI: /HTTPReceive/BTSHTTPReceive.dll
> Receive Handler: BizTalkServerIsolatedHost
> Receive Pipeline: ...DefaultPipelines.XMLReceive
>
> * Server2 *
>
> Orchestration1:
> ReceivePort -> Receive_1 -> Send_1 -> SendPort
>
> ReceivePort properties:
> One-Way Receive Port
> Transport: HTTP
> URI: /HTTPReceive/BTSHTTPReceive.dll
> Receive Pipeline: ReceivePipeline1
>
> SendPort properties:
> One-Way Send Port
> Transport: FILE
> URI: C:\ReceivedFile\%MessageID%.xml
> Send Pipeline: ...DefaultPipeline.XMLTransmit
>
> ReceivePipeline1:
> BizTalk Framework disassembler:
> Allow unrecognized message: False
> Document schemas: MySchemas.MySchema1
> Envelope schemas: BTF2Schemas.btf2_envelope
> Validate document structure: False
>
> Dynamic_SendPort:
> Dynamic One-Way Send Port
> Send Pipeline: ...DefaultPipelines.PassThruTransmit
> Filter: "BTS.ReceivePortName" == (the full name of the deployed
> Orchastration1 receive port)
> No map applied
>
> Regards,
> Ron
| |
|
| No, nothing in the App event log, or any other event log, hence me scratching
my head!
My understanding of BTF2 is that the reliable receipt is automatically
generated by the BTF disassembler. I don't think there is an option of
sending back the document along with the envelope, it just sends a special
receipt envelope. Or is my understanding wrong?
I must say that documentation for all of this is very hard to come by. Only
information pertaining directly to the (dis)assembler properties can be
found, but no general overview of _all_ the required components and how they
interact can be found. Even the recently released BizTalk 2004 Unleased book
has only one short paragraph for the BTF assembler, all they mention is that
this component requires an orchestration to support it. Any other insight
would be greatly appreciated.
Regards,
Ron
"Todd_Uhl" wrote:
[vbcol=seagreen]
> Ron,
> Are there any errors in the Application Event log? Usually you will get a
> more descriptive error in there. Perhaps I read over your post incorrectly,
> but it appears that you are just sending an envelope back as a receipt, and
> not a document as well?
>
> Todd Uhl
> http://www.geekswithblogs.net/toddu
>
> "Ron" wrote:
>
| |
|
| Everybody please repeat after me: "Rollup Package 1, Rollup Package 1, Rollup
Package 1".
If you didn't quite understand that, let me just say that once I installed
the BizTalk Server 2004 Rollup Package 1 on both servers, everything began to
work!
Regards,
Ron
"Ron" wrote:
[vbcol=seagreen]
> No, nothing in the App event log, or any other event log, hence me scratching
> my head!
>
> My understanding of BTF2 is that the reliable receipt is automatically
> generated by the BTF disassembler. I don't think there is an option of
> sending back the document along with the envelope, it just sends a special
> receipt envelope. Or is my understanding wrong?
>
> I must say that documentation for all of this is very hard to come by. Only
> information pertaining directly to the (dis)assembler properties can be
> found, but no general overview of _all_ the required components and how they
> interact can be found. Even the recently released BizTalk 2004 Unleased book
> has only one short paragraph for the BTF assembler, all they mention is that
> this component requires an orchestration to support it. Any other insight
> would be greatly appreciated.
>
> Regards,
> Ron
>
>
> "Todd_Uhl" wrote:
>
| |
|
| Well, I was wrong. The Rollup package did not solve me problem. Upon closer
investigation, the reliable receipt is still not being matched to the
original document.
Would anyone else have any ideas of what might be missing here?
Regards,
Ron
"Ron" wrote:
[vbcol=seagreen]
> Everybody please repeat after me: "Rollup Package 1, Rollup Package 1, Rollup
> Package 1".
>
> If you didn't quite understand that, let me just say that once I installed
> the BizTalk Server 2004 Rollup Package 1 on both servers, everything began to
> work!
>
> Regards,
> Ron
>
> "Ron" wrote:
>
| |
| Sam Vanhoutte 2005-01-28, 5:49 pm |
| As I need to start reliable messaging between two Biztalk servers overseas,
I am diving into BTF2 too and don't find the information.
Did you in the meantime succeed in running your scenario as wanted?
Best regards...
"Ron" <Ron@discussions.microsoft.com> wrote in message
news:8173010D-85B6-426A-ABB0-5F1C1A5A23DD@microsoft.com...
> Well, I was wrong. The Rollup package did not solve me problem. Upon
closer[vbcol=seagreen]
> investigation, the reliable receipt is still not being matched to the
> original document.
>
> Would anyone else have any ideas of what might be missing here?
>
> Regards,
> Ron
>
>
> "Ron" wrote:
>
Rollup[vbcol=seagreen]
installed[vbcol=seagreen]
began to[vbcol=seagreen]
scratching[vbcol=seagreen]
of[vbcol=seagreen]
special[vbcol=seagreen]
Only[vbcol=seagreen]
be[vbcol=seagreen]
how they[vbcol=seagreen]
Unleased book[vbcol=seagreen]
is that[vbcol=seagreen]
insight[vbcol=seagreen]
get a[vbcol=seagreen]
incorrectly,[vbcol=seagreen]
receipt, and[vbcol=seagreen]
Reliable[vbcol=seagreen]
Server1 is[vbcol=seagreen]
matching the[vbcol=seagreen]
original message[vbcol=seagreen]
fine to[vbcol=seagreen]
without any[vbcol=seagreen]
in past day"[vbcol=seagreen]
correctly?[vbcol=seagreen]
map) -> Send_1[vbcol=seagreen]
http://Server1/HTTPReceive/BTSHTTPReceive.dll[vbcol=seagreen]
deployed[vbcol=seagreen]
|
|
|
|
|