locked
Correlation and long-running question RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have an orchestration that does some processing but needs to wait for a file to be ready in a shared location before it can proceed further. I can use a delay and keep polling until the file is ready and then move on. But the problem is that it is going to be a problem while updating the BizTalk application during deployments.

    If I use correlation, is my case still going to be a long running instance?

    Thursday, February 9, 2012 11:15 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi ,

    you would need to implement sequential convoy pattern here, And also you would be only waiting for a particular amout of time? It is going to be a log running orchestration and before deploying any new release you need to make sure current ones has completed the processing.

    Please see following two articles on sequential convoys using correlation

    Sequential Convoy-By Abdul

    MSDN Sample 

    Thanks, Naushad (MCC/MCTS) http://alamnaushad.wordpress.com |@naushadalam

    If this is helpful or answers your question - please mark accordingly.

    Thursday, February 9, 2012 11:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    See this blog post get the idea how you can use the side-by-side deployment with convoy, though this post is for BizTalk 2004 but the idea should work for you. And the issue reported in this blog has been fixed in KB911617 for BizTalk 2004 so you should not face this problem.

    Please mark the post answered your question as answer, and mark other helpful posts as helpful, it'll help other users who are visiting your thread for the similar problem, Regards -Rohit Sharma (http://rohitbiztalk.blogspot.com)

    Friday, February 10, 2012 4:53 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes it is still be the LR transaction. It is nothing to do with correlation for your case.

    The problem with updationg of the LR orchestrations are independent problem. You can fight it by broken LR orch to several orchs with state stored in database

    OR

    implementing wise versioning strategy in a way new artifacts can work side by side with old one.

    Leonid Ganeline [BizTalk MVP] BizTalkien: Advanced Questions: have fun - test your knowledge

    Thursday, February 16, 2012 11:09 PM
    Moderator