web services Vs. vanilla biztalk

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › web services Vs. vanilla biztalk

Viewing 1 reply thread
  • Author
    Posts
    • December 30, 2005 at 4:14 AM #12592
      community-content

        Hi,
        We have two teams where one team believes in doing all the integration
        within the BizTalk Server and the other team believes in using web services
        and integrating with the BizTalk server. I personally like using multiple web
        services to integrate my orchestration. BizTalk and web services together
        works very well as we all know. We can handle better exceptional handling in
        the web services and we can control lot of things through the code. We
        believe BizTalk Server is a enterprise hub and not a programming environment,
        hence we do manipulations inside the web service.

        My question is what are the pros and cons doing everything within the
        vanilla BizTalk vs using web services to integrate with the BizTalk Server.

        Also when we post the document to partner, we post the document to the local
        web service and local web service in turn posts the document to the partner.
        We feel we can control the communication part much better in the web service.

        The other team believes in directly posting through BizTalk Server. We feel
        that if the partner is down or for some other reasons, the orchestration may
        hang which leaves in a suspended or dehydrated state.

        Any opinions here as what is the best way?

        Thanks,
        Anand

      • January 5, 2006 at 5:44 AM #12593
        community-content

          First Point: BizTalk give you a consistent approach to solving your integration problems. You are able to leverage the graphical development environment, BAM, and all the pre built adapters. Plus, if someone builds an Orchestration it is usually easier to component, read, and understand then a generic web service.

          Second Point: If you let Biztalk call the partner web service directly you can build into your Orchestration a retry and recovery process. You can let Biztalk do some of the harder work for you like managing the retrys and resubmits. If you use Delivery Notification, then your Orchestration will wait until your call timeout – otherwise your Orchestration will terminate and your messages will error or succeed in the Send Pipeline.

          Hope this helps.

      • Author
        Posts
      Viewing 1 reply thread
      • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.