A voir, BizTalk rencontre passablement de probl??mes pour g??rer les fichiers dont le volume est important. Pourtant, malgr?? les efforts entrepris pour r?? architecturer l’application, il est parfois impossible de s’affranchir de ses OutOfMemoryException. Dans le cas du projet actuel, le probl??me ne se passe que lorsque BizTalk doit traiter plus d’un fichier en m??me temps. J’ai donc d??cid??, provisoirement, de ne soumettre ?? BizTalk qu’un seul fichier ?? la fois, et attendre qu’il en ait termin?? le traitement avant d’en soumettre le suivant. Or, il me semble qu’il n’est pas possible d’??tre averti lorsqu’une orchestration se termine, dans le framework .NET.<\/FONT><\/SPAN><\/P> La m??thode que j’ai trouv??e passe par WMI. Ainsi, pour conna??tre quand une orchestration se termine :<\/FONT><\/SPAN><\/P> private<\/SPAN> void<\/SPAN> MountBTSOrchestrationMonitoring() <\/FONT><\/SPAN>Ainsi, lorsqu’une orchestration se terminera, l’??v??nement bts_OrchestrationDeleted sera appel??. Le seul petit probl??me, c’est qu’il n’est pas possible de conna??tre quelle orchestration s’est termin??e. Il faut alors interroger BizTalk, via WMI, ?? nouveau, pour savoir si une instance de l’orchestration observ??e est encore active :<\/FONT><\/SPAN><\/P> private<\/SPAN> int<\/SPAN> OrchestrationInstanceCount(string<\/SPAN> strOrchestrationName) <\/FONT><\/SPAN>Si la m??thode retourne 0, aucune orchestration avec le nom donn?? en param??tre n’est active.<\/FONT><\/SPAN><\/P> Attention toute fois ! BizTalk met un certain temps avant de mettre en route une orchestration, faisant que m??me si un fichier est d??pos?? dans un r??pertoire d’accueil de BizTalk, la m??thode risque de renvoyer la valeur 0, car l’orchestration n’aura pas encore d??marr??. Il serait alors judicieux de voir si des fichiers sont encore pr??sent dans le r??pertoire d’accueil avant d’en poster de nouveaux.<\/FONT><\/SPAN><\/P> <\/FONT><\/SPAN><\/P> <\/FONT><\/SPAN><\/P> <\/FONT><\/SPAN><\/P> <\/FONT><\/SPAN><\/P> <\/FONT><\/SPAN><\/P> According to a lot of blogs, BizTalk has some issues with large files. However, despite of the efforts for rearchitecturing the application, it is sometimes not possible to avoid the OutOfMemoryException.<\/EM><\/FONT><\/P> In the case of the actual project, that happens only when BizTalk has to process more than one file at a time. So, I temporary decided to pass to BizTalk only one file at a time and to wait the orchestration stops before copying the next file to the receive location. But, it seems that it is not possible to be warned when an orchestration stops with .NET.<\/EM><\/FONT><\/P> The way I found is using WMI. To know when an orchestration stops, I install an event handler :<\/EM><\/FONT><\/P> <\/FONT><\/P> private<\/SPAN> void<\/SPAN> MountBTSOrchestrationMonitoring() <\/FONT>When an orchestration will stop, the bts_OrchestrationDeleted event will be called. There is only one little issue. It is impossible to know which orchestration stopped. We have to get the answer from BizTalk itself, through WMI again, and getting the number of active instance with a given name :<\/EM><\/FONT><\/P> <\/FONT> <\/P> private<\/SPAN> int<\/SPAN> OrchestrationInstanceCount(string<\/SPAN> strOrchestrationName) If the method returns 0, no orchestration with the given name is still running.<\/EM><\/FONT><\/P> But, warning ! BizTalk needs a bit of time before starting an orchestration and event a file is dropped in a BizTalk receive location, the method will certainly return 0, because the orchestration is not yet started. It would be a good idea to test is there are files in the receive location before dropping new files.<\/EM><\/FONT><\/P><\/p>\n","protected":false},"excerpt":{"rendered":" Il n’est pas possible d’??tre notifi?? quand une orchestration BizTalk se termine. Ce post montre un moyen d’y arriver tout de m??me, mais en utilisant WMI. It is not possible to be notified when a BizTalk orchestration ends. This post shows how we can do that, using WMI.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-1823","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/posts\/1823","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/comments?post=1823"}],"version-history":[{"count":0,"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/posts\/1823\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/media?parent=1823"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/categories?post=1823"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.peneveyre.com\/en\/wp-json\/wp\/v2\/tags?post=1823"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n
\n
{
\/\/ Only one watch to mount, because we can only monitor orchestration deletion<\/SPAN>
WqlEventQuery q =<\/SPAN> new<\/SPAN> WqlEventQuery(__InstanceDeletionEvent,
new<\/SPAN> TimeSpan(0,0,0,10),
“TargetInstance isa \\”MSBTS_ServiceInstance\\””<\/SPAN>);
m_btsWatcher =<\/SPAN> new<\/SPAN> ManagementEventWatcher(new<\/SPAN> ManagementScope(root\/MicrosoftBizTalkServe),
q);
m_btsWatcher.EventArrived += new<\/SPAN> EventArrivedEventHandler(bts_OrchestrationDeleted);
m_btsWatcher.Start();
}
private<\/SPAN> void<\/SPAN> bts_OrchestrationDeleted(object<\/SPAN> sender, EventArrivedEventArgs e)
{
\/\/ Do something<\/SPAN>
}
<\/FONT><\/SPAN><\/P>
\n
\n
{
System.Text.StringBuilder sb =<\/SPAN> new<\/SPAN> System.Text.StringBuilder(“SELECT * FROM MSBTS_ServiceInstance WHERE ServiceName=\\””<\/SPAN>);
sb.Append(strOrchestrationName);
sb.Append(“\\””<\/SPAN>);
WqlObjectQuery w =<\/SPAN> new<\/SPAN> WqlObjectQuery(sb.ToString());
ManagementObjectSearcher objSearcher =<\/SPAN> new<\/SPAN> ManagementObjectSearcher(new<\/SPAN> ManagementScope(kstrWMIBTSNamespace),
w);
return<\/SPAN> objSearcher.Get().Count;
}
<\/FONT><\/SPAN><\/P>
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
{
\/\/ Only one watch to mount, because we can only monitor orchestration deletion<\/SPAN>
WqlEventQuery q =<\/SPAN> new<\/SPAN> WqlEventQuery(__InstanceDeletionEvent,
new<\/SPAN> TimeSpan(0,0,0,10),
“TargetInstance isa \\”MSBTS_ServiceInstance\\””<\/SPAN>);
m_btsWatcher =<\/SPAN> new<\/SPAN> ManagementEventWatcher(new<\/SPAN> ManagementScope(root\/MicrosoftBizTalkServe),
q);
m_btsWatcher.EventArrived += new<\/SPAN> EventArrivedEventHandler(bts_OrchestrationDeleted);
m_btsWatcher.Start();
}
private<\/SPAN> void<\/SPAN> bts_OrchestrationDeleted(object<\/SPAN> sender, EventArrivedEventArgs e)
{
\/\/ Do something<\/SPAN>
}
<\/FONT><\/SPAN><\/P>
\n
\n
\n
{
System.Text.StringBuilder sb =<\/SPAN> new<\/SPAN> System.Text.StringBuilder(“SELECT * FROM MSBTS_ServiceInstance WHERE ServiceName=\\””<\/SPAN>);
sb.Append(strOrchestrationName);
sb.Append(“\\””<\/SPAN>);
WqlObjectQuery w =<\/SPAN> new<\/SPAN> WqlObjectQuery(sb.ToString());
ManagementObjectSearcher objSearcher =<\/SPAN> new<\/SPAN> ManagementObjectSearcher(new<\/SPAN> ManagementScope(kstrWMIBTSNamespace),
w);
return<\/SPAN> objSearcher.Get().Count;
}
<\/SPAN><\/P>
\n
\n