RE: Routing problem
- From: Martin Bring (Sogeti Sverige AB) <MartinBringSogetiSverigeAB@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 14 Oct 2008 11:23:01 -0700
You say you promote the properties in the send port. If you want to route on
properties you need to promote them in the receiving end.
If you choose "Default Xml Receive"-pipeline (if xml) or a custom pipeline
with a dissassembler (xml or flat file depending) then your properties will
be promoted and BizTalk can use them to route the message.
Regards
Martin Bring
"Jonny Bergdahl" wrote:
I have developed a custom receive port that sends messages into BizTalk. In.
the adapter code, I promote some properties for use in message routing.
However, the messages gets suspended with a 0c0c01680 Routing Failure:
"The published message could not be routed because no subscribers were
found. This error occurs if the subscribing orchestration or send port has
not been enlisted, or if some of the message properties necessary for
subscription evaluation have not been promoted. Please use the Biztalk
Administration console to troubleshoot this failure."
If I doublecklick the suspended message and looks at the context, my
properties are promoted and contains values matching the filter on the send
port it is supposed to go to.
However, if I double click the "Routing Failure Report" that belongs to the
same message and checks the properties, they are not promoted. As the Error
Information tab states that "The context of the message associated with this
instance contains all the promoted properties at the time of the routing
failure", I am utterly confused.
Since I promote the values in the send adapter, how can they not be
promoted? And why does the routing fail, even though the message itself
shows the properties as promoted?
Please advice.
Regards;
/jb
- Follow-Ups:
- Re: Routing problem
- From: Jonny Bergdahl
- Re: Routing problem
- References:
- Routing problem
- From: Jonny Bergdahl
- Routing problem
- Prev by Date: Routing problem
- Next by Date: Re: The map has empty source and destination schemas
- Previous by thread: Routing problem
- Next by thread: Re: Routing problem
- Index(es):
Relevant Pages
|
Loading