|
Home > Archive > BizTalk Server Framework > August 2004 > BizTalk 2004 - Reliable Messaging
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 |
BizTalk 2004 - Reliable Messaging
|
|
|
| We are using BizTalk 2004 to communicate with a BizTalk 2002 server
using reliable messaging.
We believe that the 2002 server is configured correctly.
The two servers communicate fine when just using HTTP.
In BizTalk 2004 to configure the reliable messaging we have:
1. Create a send pipeline called SEND-BTF2.btp
2. Added a BizTalk Framework assembler to it and set all the
properties it requires
3. Added a reference to the SEND-BTF2 pipline is the send port (that
sends to BizTalk 2002)
4. Created a receive pipeline called RECV-BTF2.btp
5. Added a BizTalk Framework dis-assembler to it
6. We already have a receive location that receives from the BizTalk
2002 server, so we have added
an extra receive location to it that uses the RECV-BTF2 pipeline we
created
To test we get the system to send a message to the BizTalk 2002
server.
We can see the message go out.
We can see that BizTalk 2002 sends a SOAP reliable receipt back to us
and the receipt is read by BizTalk 2004
However after about 5 minutes we get the error as follows
"There was a failure executing the send pipeline: "MSLI.SEND_BTF2"
Source: "BizTalk Framework assembler"
Send Port: "http://Ydev01/BizTalkHTTPReceive.dll?PODR" Reason: The
reliable BTF message exhausted
all retry attempts without receiving acknowledgement.
Has anyone managed to get reliable messageing to work between BizTalk
2004 and BizTalk 2002,
or have an example we could follow
or know what we have done wrong
Any help much appreciated
Lee
| |
|
| We are having a similar problem when processing a reliable message between two BizTalk 2004 servers.
Did you manage to solve the problem ?
What value did you use for the "Delivery receipt address" and "Delivery receipt address type" properties of the BizTalk Framework Assembler on the send Pipeline ?
Regards,
Dylan
| |
| Allen Zhang 2004-05-24, 11:35 pm |
| This error indicates that no response has been received. Because of format
change, to interop with BizTalk 2004, you must upgrade to BizTalk 2002 SP1.
Could you verify that?
For same error between two 2004 servers, the routing must not have been set
up correctly. For Delivery receipt address type, you can put anything. The
Delivery receipt address is used to dynamically send port. It should in the
format of Protocol://URL. (For example: file://c:\output\Response.xml or
file://receivehost\public\ack.xml or
http://host1.domain.com/receive/btshttpreceive.dll.)
You configure a dynamic port and link to the receive port with BTF
disassembler, then the address will automatically be used for outbound
messages.
Thanks.
- Allen Zhang (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
We are having a similar problem when processing a reliable message between
two BizTalk 2004 servers.
Did you manage to solve the problem ?
What value did you use for the "Delivery receipt address" and "Delivery
receipt address type" properties of the BizTalk Framework Assembler on the
send Pipeline ?
Regards,
Dylan
| |
| Lee Connor 2004-08-06, 7:49 am |
| Yeah Allen thats what we found, once we put SP1 onto the 2002 server it
worked...
or if you do not have control over the 2002 server you can use a hotfix
number... 813845 which solves problems with the SOAP reciept having a
namespace in the delivery identity.
Lee
"Allen Zhang (MSFT)" wrote:
> This error indicates that no response has been received. Because of format
> change, to interop with BizTalk 2004, you must upgrade to BizTalk 2002 SP1.
> Could you verify that?
>
> For same error between two 2004 servers, the routing must not have been set
> up correctly. For Delivery receipt address type, you can put anything. The
> Delivery receipt address is used to dynamically send port. It should in the
> format of Protocol://URL. (For example: file://c:\output\Response.xml or
> file://receivehost\public\ack.xml or
> http://host1.domain.com/receive/btshttpreceive.dll.)
>
> You configure a dynamic port and link to the receive port with BTF
> disassembler, then the address will automatically be used for outbound
> messages.
>
> Thanks.
>
> - Allen Zhang (MSFT)
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> --------------------
>
> We are having a similar problem when processing a reliable message between
> two BizTalk 2004 servers.
>
> Did you manage to solve the problem ?
>
> What value did you use for the "Delivery receipt address" and "Delivery
> receipt address type" properties of the BizTalk Framework Assembler on the
> send Pipeline ?
>
> Regards,
> Dylan
>
|
|
|
|
|