Blog Home  Sign In RSS 2.0 Atom 1.0 CDF  

  def Softwaremaker() :
         return "William Tay", "<Challenging Conventions />"

  knownType_Serialize, about = Softwaremaker()

 Saturday, January 30, 2010

Via here: BizTalk Server 2006 R2 SP1 is now available !!!

These 2 factors are great improvements, or rather - fixes:

Better reliability, performance, and scale for the following key features

  • Throttling and dehydration of orchestrations.
  • Archiving and purging operations.
  • BAM alerts and archiving.
  • HIPAA.
  • Reduced memory consumption in scenarios using scripting functoids.
  • Improvement in the bts_FindSubscription stored proc, resulting in faster execution and lower CPU utilization.

Better management and deployment experiences

  • Performance and user experience improvements of key scenarios.
  • WCF configuration management.
  • Significant improvement in deployment time for send ports using a map.

While still some time away, I am very looking forward to BizTalk v.Next where there will be some very interesting innovations to push the low latency envelope (every bit of pun intended).

Saturday, January 30, 2010 12:18:59 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Tuesday, November 03, 2009

    Q: Does BizTalk Server WCF Custom Adapters support Identity Federation ?

    A: Yes, it does. The WCF adapter supports the ws2007FederationHttpBinding. BizTalk MVP Yossi Dahan blogs about it extensively here.

    Tuesday, November 03, 2009 10:10:17 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Sunday, February 17, 2008

    If you make your living installing, deploying, managing and operating Microsoft BizTalk Server 2006. I guarantee that you will be excited and be thankful for the availability of the BizTalk Server Operations Guide. So, what's in it ?

    openquotes.png Guidance based on real-world experience. The idea for the guide originated with Microsoft field representatives, partner organizations, and customers who plan, deploy, and maintain BizTalk Server installations. This group of IT professionals has accumulated extensive hands-on experience with a diverse range of BizTalk solutions. As they gained experience they created checklists, best practices, and presentations to guide future BizTalk Server operations. We collected and organized this information to create the guide.
    Key portions of this guide are new; however, a considerable portion consists of documentation taken from BizTalk Server 2006 R2 Help, white papers, Knowledge Base articles, and other sources. It has been carefully reviewed and vetted by experts from the community of BizTalk Server IT professionals and members of the product development team, whom we gratefully acknowledge at the end of this topic. We believe that the information presented here will help BizTalk Server users solve, and above all, avoid many of the common problems that can occur while deploying and maintaining a BizTalk Server installation.


    The BizTalk Server Operations guide is now available for download in DOCX, CHM, and PDF file formats.

    Saturday, February 16, 2008 10:25:50 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Friday, February 15, 2008

    Problem: If you are in the configuration screen of Microsoft BizTalk Server 2006 and you are configuring Business Activity Monitoring (BAM) Portal, you checked 'Enable BAM Portal" and you noticed that the Account and Windows Group options are still grayed out.

    Cause: I suspect that if you have configured BAM Portal once from any server in the BizTalk Server group, the user account fields are disabled on the rest of the servers even though Enable BAM Portal option is still available.

    Resolution: Reset BAMVRoot in the BAM config file: BAMConfig.xml and then run BM update-config

    Used bm.exe to get the BAM configuration XML:

    1. Open a command window
    2. Go to C:\Program Files\Microsoft BizTalk Server 2006\Tracking
    3. Type: bm.exe get-config -FileName:BAMConfig.xml

    It specifies BAMVRoot so it appears someone configured BAMPortal before. Deleted this line:

    1. <GlobalProperty Name="BAMVRoot">http://FOOBAR:80/BAM</GlobalProperty>

    Saved the file and updated the BAM configuration:

    1. Open a command window
    2. Go to C:\Program Files\Microsoft BizTalk Server 2006\Tracking
    3. Type: bm.exe update-config -FileName:NewBAMConfig.xml

    The options will no longer grayed out. You will probably get an error that the "BAMAppPool already exists". That is fine. Delete it, restarted IIS and it will be configured successfully.

    As far as I can tell - this is not documentated very widely and this has helped me so I hope it helps someone out there as well.

    Thursday, February 14, 2008 11:07:47 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Thursday, November 15, 2007

    With the impending release of the Microsoft BizTalk Server Adapter Pack (Beta 2 available here), there are some confusions as to the differences between the BizTalk Adapter Pack, Microsoft's WCF Line of Business (LOB) Adapter SDK, and of course, the (older) BizTalk Adapter Framework.

    In a nutshell, the BizTalk Adapter Pack is written and developed on top of the WCF LOB Adapter SDK (which is free and freely downloadable). The value-add is that the LOBs that it can integrate with ootb are SAP (mySAP Business Suite), ORACLE (Oracle Database) and SIEBEL (Siebel eBusiness Applications). Of course, a lot of grunt work is taken away from you, as explained here.

    One of the confusing part is the play of the words "BizTalk" in the product name. As I have explained above, built on the WCF LOB Adapter SDK, these adapters are host agnostic i.e. they are not tied to a specific product like BizTalk. You can use it with BizTalk 2006 R2 specifically (The WCF LOB adapters cannot be used in BizTalk Server versions prior to BizTalk Server 2006 R2) but you can use it outside of BizTalk as well (some configuration work required, such as the Add Adapter Reference plug-in, etc) but this also means you do not have to buy BizTalk for it, if you dont have to.

    This SDK is based on Windows Communication Foundation (WCF, previously - Indigo), and it surfaces an adapter to an LOB system as a WCF binding. For an adapter consumer, the adapter can be accessed like a typical WCF service; the consumer does not have to learn a new programming model. The same adapter developed can be reused in multiple .NET applications including custom .NET applications, Microsoft® BizTalk® Server 2006 R2, Microsoft Office SharePoint® Server 2007 SP1, and Microsoft SQL Server™ Integration Services (SSIS) through adapter development provided. In addition, the adapter provides metadata browse, search, and retrieval functionality for the adapter consumer to selectively generate WCF contracts that reflect live type modeling of the LOB system.

    Confusions from customers and partners alike usually stem from the the primary differences between WCF LOB Adapter SDK and the BizTalk Adapter Framework. I will hereby summarized it in the following table:

    Feature WCF LOB Adapter SDK BizTalk Server Adapter Framework


    .NET 3.0 Assembly, provides help classes for metadata processing, connection management, and messaging

    COM, provides basic support for adapter operations.

    Adapter exposure

    • Exposed as WCF binding; available to any application that can consume a WCF binding including BizTalk Server 2006 R2 (using the WCF adapter)

    • Exposed only to BizTalk Server; not reusable by other applications.


    Adapter Code Generation Wizard, metadata browser for Visual Studio 2005



    Yes (as WCF channel extension)


    If you are knee-deep into writing, shipping and selling adapters for BizTalk, I strongly urge you to visit the Adapters' Team Blog here.

    Thursday, November 15, 2007 2:04:07 PM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Thursday, February 15, 2007

    These are just some of the tabs that can be found if you expose a Microsoft BizTalk Server 2006 R2 process via a Windows Communication Foundation (WCF, previously - Indigo) Service.


    The interesting part of the Messaging Tab of BizTalk 2006 R2 is that you are able to dictate the source of the inbound message body that you would like BizTalk to handle.

    You can specify it to be the entire <soap:Envelope> or just the <soap:Body>, which essentially strips out the <soap:Header> element from the entire envelope. The flexibility comes in when you can dictate and customize the message content via an XPath expression that you would like BizTalk to process such as: /bookstore/book[0] ...

    Thursday, February 15, 2007 7:34:21 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions

  •  Wednesday, February 16, 2005

    I know this BizTalk tip will come in handy one day.

    Wednesday, February 16, 2005 12:01:52 AM (Malay Peninsula Standard Time, UTC+08:00)  #    Disclaimer 
  • Blog reactions