Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria Wednesday, September 24, 2014 3:37 PM

Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria Wednesday, September 24, 2014 3:37 PM
• Proposed as answer by Rachit Sikroria 19 hours 34 minutes ago

Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria Wednesday, September 24, 2014 3:37 PM
• Proposed as answer by Rachit Sikroria Friday, September 26, 2014 2:53 PM

Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria Wednesday, September 24, 2014 3:37 PM
• Proposed as answer by Rachit Sikroria Friday, September 26, 2014 2:53 PM

Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria Wednesday, September 24, 2014 3:37 PM
• Proposed as answer by Rachit Sikroria Friday, September 26, 2014 2:53 PM

You can use a Resource Dispenser Pattern to limit the number of concurrent connections beyond simple Ordered Delivery.

Wiki Article: http://social.technet.microsoft.com/wiki/contents/articles/23924.biztalk-resource-dispenser-send-port-edition.aspx

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 2 hours 8 minutes ago

You can use a Resource Dispenser Pattern to limit the number of concurrent connections beyond simple Ordered Delivery.

Wiki Article: http://social.technet.microsoft.com/wiki/contents/articles/23924.biztalk-resource-dispenser-send-port-edition.aspx

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, September 29, 2014 8:18 AM

You can use a Resource Dispenser Pattern to limit the number of concurrent connections beyond simple Ordered Delivery.

Wiki Article: http://social.technet.microsoft.com/wiki/contents/articles/23924.biztalk-resource-dispenser-send-port-edition.aspx

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Monday, September 29, 2014 8:18 AM

How can we send only one message to a WCF service at a time? How we can limit the number of concurrent calls to a WCF service without use the Singleton pattern or without do the change in BizTalk Configuration file? Can we do it by Host throttling?

Hi Pawan,

You need to use WCF-Custom adapter and add the ServiceThrottlingBehavior service behavior to a WCF-Custom Locations.

ServiceThrottlingBehavior.MaxConcurrentCalls - Gets or sets a value that specifies the maximum number of messages actively processing across a ServiceHost. The MaxConcurrentCalls property specifies the maximum number of messages actively processing across a ServiceHost object. Each channel can have one pending message that does not count against the value of MaxConcurrentCalls until WCF begins to process it.

Follow MSDN- http://msdn.microsoft.com/en-us/library/ee377035%28BTS.10%29.aspx

http://msdn.microsoft.com/en-us/library/system.servicemodel.description.servicethrottlingbehavior.maxconcurrentcalls.aspx

I hope this helps.

Rachit

If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

We can add ServiceThrottlingBehavior.MaxConcurrentCalls on Receive Location. But my requirement is limit  number of concurrent calls to a WCF service on Send Port.

1) You can use a dedicated send port for your application and set Maximum Engine Threads property accordingly.

2) You can also achieve this by using Ordered delivery at the send port.

Rachit

If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

implement the order delivery means using the Singleton patter which I can't use as per requirement.

I had used Maximum Engine Threads property for send host, but it not worked.

The best possible way to handle this was by making change to your BizTalk Configuration file by adding connectionManagement settings and limiting the number of connections there.

But unfortunately you pointed that as restriction already. I am exhausted with all the options, can't think of anything else.

Looking forward to this post for any other possibles, if it ever exists.

Rachit

Realize, you're stating a problem, then immediately eliminating the two most common solutions.  Understandably, this restriction may be imposed upon you, so...

Why have have Host settings and a singleton been ruled out?  Maybe we can help you address those.

Does this include all singletons?

You can try out custom queuing in the design and process one request at a time for the WCF service call.

You are going to need a throtting pattern implemented.

Create a controller orchestration which in turn will trigger another sequential convoy orchestration by passing a correlation value, further the S convoy will trigger your WCF service calling orchestration via message box in a synchronous way. This design will allow only one service call at a time also by changing the design of main orchestration it can allow you n number of concurrent threads (In event of you service can process more than one request at the same time)

Regards

Practical implementation of Pushpendra's suggestion below:

http://seroter.wordpress.com/2008/05/19/biztalk-orchestration-throttling-pattern/

Rachit

• Edited by Rachit Sikroria 18 hours 49 minutes ago

You can use a Resource Dispenser Pattern to limit the number of concurrent connections beyond simple Ordered Delivery.

Wiki Article: http://social.technet.microsoft.com/wiki/contents/articles/23924.biztalk-resource-dispenser-send-port-edition.aspx