Part of the issue is that each call to the web service involves 1)
publishing your request to the message box, 2) the send adapter getting this
message and actually making the SOAP call, then 3) placing the response back
in the message box, where it can be 4) picked up by the orchestration. Take
a look at this peformance characteristics whitepaper for information on how
you can tune your server for different adapters:
>> In fact in a first time I was debatching in the pipeline, but that doesn't
>> allow me to delivery the messages in the order, that's why I need to
>> in the orchestration and loop for all the messages (in the order).
>> But by doing that, the web service calls are not done in the same time, so
>> lose precious seconds for each message ...
>> That's why I would like to use the same instance of the web service for
>> whole messages in the orchestration .... (I managed to do this, but by
>> a C# class calling the web service that I use by a var in my
>> I'm really searching why this web services are so slow ... (in fact the
>> instanciation ...), is it a BizTalk problem ....? Or am I missing
>> Tanks a lot for your help
>>> Debatching large messages in the orchestration is sometimes slow, one
>>> could be to debtch in the puipeline, and create one orchestration
>>> per debatched message (if this is possible in your scenario).
>>> There'a a good blog post on this here:
>>> Another option to speed things up may be to use the parallel acions shape
>>> when calling several web services.