| Author |
SOAP Envelope Receipt Not Sending Out
|
|
| fheinema 2005-10-28, 5:03 pm |
| We are migrating a partner from our 2002 server to 2004. They send xml with
a Soap envelope so that we will send back a receipt so they know we have
received the document. On 2002 BizTalk automatically processed the file and
sent out receipts. We did not have to set anything. On 2004 BizTalk is
successfully processing the files, but our partner is not getting receipts.
The files are coming into a directory on our side and we have to use a file
adapter receive port to pick up and process the files. This is the same
process we used on the 2002 server. The mapping is completed in in the send
port corresponding the receive port.
I have not been able to figure out if I am missing some sort of setting to
send the receipts back or not. I assumed based on 2002 that this was
automatic. I have pasted a header from one of the SOAP envelopes below. Can
someone tell me if this is an issue with a setting I am missing or possibly
something wrong with the SAOP envelope? I am not very familiar with the use
of the SOAP envelope and receipts.
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><SOAP-ENV:Header><eps:endpoints
SOAP-ENV:mustUnderstand="1"
xmlns:eps="http://schemas.biztalk.org/btf-2-0/endpoints"
xmlns:biz="http://schemas.biztalk.org/btf-2-0/address/types"><eps:to><eps:address
xsi:type="biz:OrganizationName">IBM</eps:address></eps:to><eps:from><eps:address
xsi:type="biz:OrganizationName">IBM</eps:address></eps:from></eps:endpoints><prop:properties
SOAP-ENV:mustUnderstand="1"
xmlns:prop="http://schemas.biztalk.org/btf-2-0/properties"><prop:identity>uuid:DA117563-CB0A-4121-810D-F67A791DFD72</prop:identity><prop:sentAt>2005-10-27T00:39:24+00:00</prop:sentAt><prop:expiresAt>2005-10-27T01:19:24+00:00</prop:expiresAt><prop:topic>ro
ot:Catalog</prop:topic></prop:properties><services
xmlns="http://schemas.biztalk.org/btf-2-0/services"><deliveryReceiptRequest><sendTo><address
xsi:type="biz:httpsURL">https://ibmemax.pc-daiwabo.co.jp/bi...eMsgReceipt.asp</address></sendTo><sendBy>2005-10-27T01:19:24+00:00</sendBy></deliveryReceiptRequest></services></SOAP-ENV:Header><SOAP-ENV:Body>
Thanks,
Fred
--
Fred Heinemann
| |
| Jon Flanders 2005-10-28, 5:03 pm |
| Hello fheinema, are you using a custom receive pipeline with the BizTalk
Framework Disassembler in it? I believe that is what you have to do to make
this work
Jon Flanders [MVP]
http://www.masteringbiztalk.com
> We are migrating a partner from our 2002 server to 2004. They send
> xml with a Soap envelope so that we will send back a receipt so they
> know we have received the document. On 2002 BizTalk automatically
> processed the file and sent out receipts. We did not have to set
> anything. On 2004 BizTalk is successfully processing the files, but
> our partner is not getting receipts.
>
> The files are coming into a directory on our side and we have to use a
> file adapter receive port to pick up and process the files. This is
> the same process we used on the 2002 server. The mapping is completed
> in in the send port corresponding the receive port.
>
> I have not been able to figure out if I am missing some sort of
> setting to send the receipts back or not. I assumed based on 2002
> that this was automatic. I have pasted a header from one of the SOAP
> envelopes below. Can someone tell me if this is an issue with a
> setting I am missing or possibly something wrong with the SAOP
> envelope? I am not very familiar with the use of the SOAP envelope
> and receipts.
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"><SOAP-ENV:Header
> xmlns:eps="http://schemas.biztalk.org/btf-2-0/endpoints"
> xmlns:biz="http://schemas.biztalk.org/btf-2-0/address/types"><eps:to><
> eps:address
> xsi:type="biz:OrganizationName">IBM</eps:address></eps:to><eps:from><e
> ps:address
> xsi:type="biz:OrganizationName">IBM</eps:address></eps:from></eps:endp
> oints><prop:properties SOAP-ENV:mustUnderstand="1"
> xmlns:prop="http://schemas.biztalk.org/btf-2-0/properties"><prop:ident
> ity>uuid:DA117563-CB0A-4121-810D-F67A791DFD72</prop:identity><prop:sen
> tAt>2005-10-27T00:39:24+00:00</prop:sentAt><prop:expiresAt>2005-10-27T
> 01:19:24+00:00</prop:expiresAt><prop:topic>root:Catalog</prop:topic></
> prop:properties><services
> xmlns="http://schemas.biztalk.org/btf-2-0/services"><deliveryReceiptRe
> quest><sendTo><address
> xsi:type="biz:httpsURL">https://ibmemax.pc-daiwabo.co.jp/biztalk/Relia
> bleMsgReceipt.asp</address></sendTo><sendBy>2005-10-27T01:19:24+00:00<
> /sendBy></deliveryReceiptRequest></services></SOAP-ENV:Header><SOAP-EN
> V:Body>
>
> Thanks,
> Fred
| |
| fheinema 2005-10-28, 5:03 pm |
| I am using the default Pipeline and not a custom one. I will give that a try
and let you know if it works. Thanks for the advice!
--
Fred Heinemann
"Jon Flanders" wrote:
> Hello fheinema, are you using a custom receive pipeline with the BizTalk
> Framework Disassembler in it? I believe that is what you have to do to make
> this work
>
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
>
>
>
>
| |
| fheinema 2005-10-28, 5:03 pm |
| It looks like it is reading the envelope now. I am getting an error though
about the Index being out of the bounds of the array. I built a custom
pipeline with an XML disassembler and put in the collection of schemas. I
have used all of the BizTalk envelopes that are provided in the enveolpe
collection and none of them seem to resolve this error. I beleive the one
that should work is the BTF2Schemas.btf2_endpoints_header. Here is the
spcific error I am seeing:
There was a failure executing the receive pipeline: "DISIn.DISInRecv"
Source: "Microsoft.BizTalk.Pipeline.Components" Receive Location:
" W:\PartnerDirectories\DIS\In\DIS_832_846
*.xml" Reason: Index was outside the
bounds of the array.
Any ideas about this one?
--
Fred Heinemann
"Jon Flanders" wrote:
> Hello fheinema, are you using a custom receive pipeline with the BizTalk
> Framework Disassembler in it? I believe that is what you have to do to make
> this work
>
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
>
>
>
>
|
|
|
|