BizTalk Server Orchestration - Correlation and Publishing Orchestration Issue

Author

Correlation and Publishing Orchestration Issue

Gary

2004-06-11, 5:44 pm

We have an Orch with two Receives in Parallel that initialize a correlation set.
The schemas for the two receives both have their elementFormDefault set to "qualified".

We've tested the Orch using the File adapter succesfully, however when we publish one of the Receive Ports as a Web Service, we have the following error:

"The Messaging engine failed to process a message submitted by adapter:SOAP Source ...."

After looking at the Message Details in HAT we notice that the properties have not been promoted.
We also traced the message received by the Web Service and it seems correct.

Thanks in advance.

Christof

2004-06-20, 11:09 pm

Hi Gary,

can you please elaborate? Are you initialising a different corrset in both
receives please?
Do both receives work on same message schema?

Kind regards,
Christof

"Gary" <anonymous@discussions.microsoft.com> wrote in message
news:759EC0DE-03E9-496D-B807-E0C729659B06@microsoft.com...
> We have an Orch with two Receives in Parallel that initialize a
correlation set.
> The schemas for the two receives both have their elementFormDefault set to
"qualified".
>
> We've tested the Orch using the File adapter succesfully, however when we
publish one of the Receive Ports as a Web Service, we have the following
error:
>
> "The Messaging engine failed to process a message submitted by
adapter:SOAP Source ...."
>
> After looking at the Message Details in HAT we notice that the properties
have not been promoted.
> We also traced the message received by the Web Service and it seems
correct.
>
> Thanks in advance.
>
>
>

Gary

2004-06-20, 11:09 pm

Hi Chrstof,

We are initializing the same corrset in both Receives and are using a different message schema on each Receive.

Best Regards
Gary

"Gary" wrote:

> We have an Orch with two Receives in Parallel that initialize a correlation set.
> The schemas for the two receives both have their elementFormDefault set to "qualified".
>
> We've tested the Orch using the File adapter succesfully, however when we publish one of the Receive Ports as a Web Service, we have the following error:
>
> "The Messaging engine failed to process a message submitted by adapter:SOAP Source ...."
>
> After looking at the Message Details in HAT we notice that the properties have not been promoted.
> We also traced the message received by the Web Service and it seems correct.
>
> Thanks in advance.
>
>
>
>

Christof

2004-06-20, 11:09 pm

Ok,

a parallel convoy you mean :-)

Although I'm not sure about this at all, I believe that parallel convoys are
only supported if they use the same port, which in your case is a possible
requirement that was not met. I took a look at the docs, which don't seem
to mention any restrictions of that kind. (Look at "Concurrent Correlated
Receives")

MS, can anyone confirm this please?

Regards,
Christof

"Gary" <Gary@discussions.microsoft.com> wrote in message
news:CB85883F-FF9C-4778-ACFA-CC6BE6E19C9B@microsoft.com...
> Hi Chrstof,
>
> We are initializing the same corrset in both Receives and are using a
different message schema on each Receive.[vbcol=seagreen]
>
> Best Regards
> Gary
>
> "Gary" wrote:
>
correlation set.[vbcol=seagreen]
to "qualified".[vbcol=seagreen]
we publish one of the Receive Ports as a Web Service, we have the following
error:[vbcol=seagreen]
adapter:SOAP Source ...."[vbcol=seagreen]
properties have not been promoted.[vbcol=seagreen]
correct.[vbcol=seagreen]

Narasimhan Padmanabhan

2004-06-20, 11:09 pm

Lee Graber [MSFT]

2004-06-20, 11:09 pm

Sorry for showing some non-unity, but while it is true that *sequential*
convoys can only be associated with one port, a parallel activation convoy
can be connected to two different ports (we just tested just for kicks). As
to your error, while you truncated it, it sounds like you are getting a
routing failure. You should look at the routing failure report and check
the properties of the message suspended with that report (all found in
HAT). If this is what you did when you say that the properties were not
promoted, you next need to look and see if MsgType was promoted. If msgtype
is not promoted (or even in the context), then there is no way we could
have promoted the properties associated with the message. The most common
cause of this is that your receive pipeline is the passthru pipeline which
will not look for msgtype of promoted properties. Please check to make sure
you are using the XML pipeline.

THanks
Lee

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team
--------------------[vbcol=seagreen]
<CB85883F-FF9C-4778-ACFA-CC6BE6E19C9B@microsoft.com>
<OdBVuEZUEHA.760@TK2MSFTNGP12.phx.gbl>[vbcol=seagreen]
rights.[vbcol=seagreen]
12[vbcol=seagreen]
a[vbcol=seagreen]
elementFormDefault[vbcol=seagreen]
seems[vbcol=seagreen]

Gary

2004-06-20, 11:09 pm

Thank-you Lee,

That was the problem!
The Publishing Wizard creates a Receive Port that uses a Pass-Through Receive Pipeline, which needed to be changed to the XMLReceive.

Thanks
Gary

"Lee Graber [MSFT]" wrote:

> Sorry for showing some non-unity, but while it is true that *sequential*
> convoys can only be associated with one port, a parallel activation convoy
> can be connected to two different ports (we just tested just for kicks). As
> to your error, while you truncated it, it sounds like you are getting a
> routing failure. You should look at the routing failure report and check
> the properties of the message suspended with that report (all found in
> HAT). If this is what you did when you say that the properties were not
> promoted, you next need to look and see if MsgType was promoted. If msgtype
> is not promoted (or even in the context), then there is no way we could
> have promoted the properties associated with the message. The most common
> cause of this is that your receive pipeline is the passthru pipeline which
> will not look for msgtype of promoted properties. Please check to make sure
> you are using the XML pipeline.
>
> THanks
> Lee
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> EBusiness Server Team
> --------------------
> <CB85883F-FF9C-4778-ACFA-CC6BE6E19C9B@microsoft.com>
> <OdBVuEZUEHA.760@TK2MSFTNGP12.phx.gbl>
> rights.
> 12
> a
> elementFormDefault
> seems
>
>