Share via

From Zero to 4,000

  • Article

Now you know why I've been having fun for the last 4 years. Thanks to all our customers the BizTalk Server business is booming.  A little celebration of our anniversay is here.

Meanwhile 1/2 my team is in Asia this week and last week launching our final BizTalk Server 2004 accelerator - RosettaNet.

Erica stopped by today and we recorded an MSDN TV episode on Indigo and BizTalk Server including a demo. It takes a while for the production to complete but look out for that in the next few weeks/months.

Finally a request.  We are evaluating samples for BizTalk Server 2006.  If you had your way what additional samples would you ship with the product?  Add your comments to this thread. We are evaluating resource (ability to get it done) and are currently collecting feedback so send it in!

Comments

  • Anonymous
    February 28, 2005
    The comment has been removed
  • Anonymous
    February 28, 2005
    The comment has been removed
  • Anonymous
    March 01, 2005
    I would like to see atleast one sample that includes orchestration and business process for health insurance industry.
  • Anonymous
    March 01, 2005
    Since you plan to remove HWS (correct me if I am wrong) please provide some alternatives for it or some samples to a replacing technology.<br><br>Keep up the good work,<br>Angelo
  • Anonymous
    March 01, 2005
    I'd love to see samples showing integration with the Patterns and Practice group's Enterprise Library; in particular the Exception handling, logging, and configuration blocks. I'm finding a lot of customers are planning to use this in regular .NET projects and would like to reuse the same techniques with BizTalk.
  • Anonymous
    March 02, 2005
    Scott,<br>I would like to see examples around the extensibility of the BizTalk Tools, such as the editor. For example perhaps the source code of the Flat File Extensions.
  • Anonymous
    March 02, 2005
    Hi Scott,

    Based around Orchestrations.
    (1) Using Config properties in an Orch. e.g. from an equivalent 'Web.Config' file (c.f. for Web Based Apps)

    (2) Throttling - Orchs that process msgs One a time to send onto a legacy system that dies if it has more than one msg fed to it at once.

    (3) An sample App using the BTS API (or WMI) that determines whether your (long running Orch) is still running + possibly how many there are waiting.

    (4) Lastly, Rules Engine rules that get asserted in response to a certain time.
    e.g. Govt. poilicy changes are enforced midnight, discount is now 10%. How can we be certain that the very next request at 12.01 uses the new rule policy??

    Would be coool!
  • Anonymous
    March 02, 2005
    Scott,

    1. Several additional content based routing examples (message broker pattern).

    2. Several additional orchestration patterns including logical message splitter (not just debatching).

    3. A bunch more rules engine examples with better documentation. This is a huge topic that takes alot to get your hands around.

    4. Migration examples & scenarios from BTS2002. You still have alot of customers on BTS2002 that really need to move to BTS2006 (or BTS2004).
  • Anonymous
    March 03, 2005
    Hi,<br>Regarding the EDI Adapter. Small organizations that send EDI to larger trading partners are typically assigned Sender IDs by their larger trading partners. The current Covast EDI Adapter allows for configuring ONE sender address, in the adapter's send handler. This is great for IBM or Microsoft or Medicare, but not for the little guys who can't dictate their own sender IDs. You need a sample showing how to work around this if you want your product to be marketable for smaller organizations using it for EDI purposes. This is especially true of the HIPAA EDI Accelerator 3.0. At least BTS 2002 could handle this scenario by allowing for specific application_sender_code values in the document definition for a particular channel, and multiple 'aliases' for the Home Organization. Thanks.<br>JT
  • Anonymous
    March 07, 2005
    The comment has been removed
  • Anonymous
    March 09, 2005
    The thing I miss the most, apart from some of the things already mentioned, is in error handling. Exception handling and compensation are simple and covered in the documentation, but most examples are way too simple (or omiss) in what concerns error handling. I would like to see the (classic) PO example with some (recomended) error handling in it, and others.