Wrox Programmer Forums
Go Back   Wrox Programmer Forums > .NET > Other .NET > Biztalk
|
Biztalk General discussion about Biztalk server.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Biztalk section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old September 19th, 2006, 09:50 PM
Registered User
 
Join Date: Aug 2006
Posts: 4
Thanks: 0
Thanked 0 Times in 0 Posts
Default Multiple receive ports in an orchestration

I am having an issue with an orchestration that I am creating that has the following parameters.

I receive a message (XML) on a Request/Response port. The message is then sent to a send port that passes the message to the MSMQT. The MSMQT passes the message to an application. After the app does its processing, it passes a Response XML file back to a different MSMQ queue (part of the architecture unfortunately). A receive port listening in on the second MSMQT takes the message, passes the message to the Response part of the port operation.

I set the first receive message initializes the BTS.MessageID as the correlation set property. The remaining messages use that correlation set. The issue is that when I build the solution, I get the following error:

"in a sequential convoy the ports must be identical."

I researched this issue and found that this issue occurs when you do not share a receive port.

I was wondering if anyone has encountered this problem and found a way around it. I have to stay with the 2 receive port system. Would separating the orchestration into two work? I should be able to use the BTS.MEssageID property in that second orchestration.

Any help would be greatly appreciated on this issue.

 
Old November 17th, 2006, 05:22 PM
Registered User
 
Join Date: Nov 2006
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I have encountered a similar problem. Have you found any resolution?

 
Old April 15th, 2007, 08:16 PM
Registered User
 
Join Date: Apr 2007
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

It's just happening because you are initializing and following a correlation both in a receive shape. Try to initialize the correlation in a send shape and then follow the correlation using a receive shape.

I Hope it helps !

Bruno Spinelli.
 
Old October 25th, 2008, 04:16 AM
Registered User
 
Join Date: May 2008
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Hello Bruno,
I am also having the same issue. The requirement is such, that i have to use one receive port scheduled message in order to activate the orchestration & two another receive port for same message type.

As you said, try to initialize the correlation in a send shape and then follow the correlation using a receive shape.
My question is:which send shape & which receive shape you are talking about?

Please reply... thanks alot in advance
Regards,
harry

Happy Programming,
harry
 
Old August 14th, 2013, 06:56 AM
Registered User
 
Join Date: May 2013
Posts: 9
Thanks: 0
Thanked 0 Times in 0 Posts
Default Add more orchestration

In BizTalk server try to add one more orchestration that will pick the xml file and transform it to a text file for another position and keep your solution simple and loosely coupled, You can modify any component without splitting or ending the whole message flow.

http://www.athenainfotech.co.uk/free...k-health-check





Similar Threads
Thread Thread Starter Forum Replies Last Post
Need information on ports acelives Other Programming Languages 1 May 29th, 2011 09:00 AM
Connecting to multiple com ports using threads gaurisharya Beginning VB 6 0 April 8th, 2008 12:01 AM
Working With Ports JosephLouis .NET Web Services 1 November 27th, 2005 02:13 PM
IDENTIFYING THE PORTS abdul_owiusa C# 3 August 7th, 2004 04:11 AM
ports abdul_owiusa C# 1 August 6th, 2004 06:09 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.