Mohammed Atef’s Technical blog

Covert Complex SQL In clause to a business rule

Suppose you have Complex SQL Stored procedure and you would like to do this Complex SQL operation into BizTalk Business Rule Engine, what can you do??

Let see Example for This…
we need to transform the below SQL script to BRE
Update a Set a.policy=150
from a
Inner join b
Where a.xx=100 and a.yy in (3,10) and b.zz=1
To solve this issue follow this steps
1- create view contain SQL join.
2- Use IF statement in Business Rule
by adding in the if condition a.xx=100 and a.yy in (3,10) and b.zz=1
and put the set action into if condition action
I Hope this Help.


July 29, 2009 Posted by | Biztalk | , , | Leave a comment

Configure DB2 adapter in BizTalk 2009

Problem definition

I was trying to build new BizTalk application to retrieve data from DB2 and insert it into SQL DB or
Oracle DB by applying some Business Rules.

First i have installed Db2 client into BizTalk 2009 server Machine then i have installed
BizTalk Server 2009 Adapters for Host Systems 2.0 Developer Edition
but after installing this tools i can’t found my db2 adapter :(!!!!!!!.
i have search for this issue in many places but i didn’t found solution.

finally i went to my lovely forum MicroSoft BizTalk Forum and submit new question.
after few hours i get a lot of answers one of the effective answer was from Eliasen.

you can find his answer here
after that i download this tool BizTalk Server 2009 Adapters for Host Systems 2.0 Enterprise Edition and installed it.
Finally i found the DB2 adapter in BizTalk 2009 server administration Adapters list.

Thank you Eliasen.

I hope this help

July 7, 2009 Posted by | Biztalk | , , , , , | Leave a comment

BizTalk 2009 Orchestration Dehydration and Persistence Points

I am going to describe the Orchestration Dehydration and Persistence Points.this post for understanding why and how BizTalk use these.So let’s go quickly.

We know that BizTalk some times depending on other external application, so it is possible to ask BizTalk for waiting the other external application responses this my consume a lot of resources and memories, Instead of just waiting, the orchestration will dehydrate, and the state of the instance is taken out of memory and stored in SQL Server. BizTalk does this to free up valuable resources
for other processes and special subscription will be created for the dehydrated instance of the orchestration.This subscription will monitor the BizTalk message box for context properties
that match your unique correlation ID. When the subscription comes across that message, the
orchestration will “wake up,” and the state of the instance will be taken out of the database
and reconstituted in memory. The point at which the orchestration will, essentially, come alive
is known as a persistence point.
Persistence Points
The orchestration engine persists the entire state of a running orchestration instance at various points, so that the instance can later be completely restored in memory.
The state includes
1. The internal state of the engine, including its current progress.
2. The state of any .NET components that maintain state information and are being used by the orchestration.
3. Message and variable values.
if a message is received but there is an unexpected shutdown before state can be saved, the engine will not record that it has received the message, and will receive it again upon restarting. The engine will save the state in the following circumstances:

1. The end of a transactional scope is reached.
The engine saves state at the end of a transactional scope so that the point at which the orchestration should resume is defined unambiguously, and so that compensation can be carried out correctly if necessary.
The orchestration will continue to run from the end of the scope if persistence was successful; otherwise, the appropriate exception handler will be invoked. If the scope is transactional and atomic, the engine will save state within that scope.If the scope is transactional and long-running, the engine will generate a new transaction and persist the complete state of the runtime.
2.Debugging breakpoint is reached.
3. message is sent.The only exception to this is when a message is sent from within an atomic transaction scope.
4. The orchestration starts another orchestration asynchronously, as with the Start Orchestration shape.
5. The orchestration instance is suspended.
6. The system shuts down under controlled conditions. in that case, when the engine next runs, it will resume the orchestration instance from the last persistence point that occurred before the shutdown.
7. The engine determines that the instance should be dehydrated.
8.The orchestration instance is finished.

I hope this help…………

June 20, 2009 Posted by | Biztalk | , , | 1 Comment

BizTalk 2009 Orchestration Debugging

HAT in BizTalk 2006,2009

In BizTalk 2006 we was debugging orchestration using HAT(Health And Activity) BizTalk 2006 Tool or writing BTZHATApp.exe in the Run windows.
Now BizTalk 2009 Move this functionality from HAT tools to BizTalk Application Console(MMC).

Debug Orchestration in BizTalk 2009

To debug any orchestration in BizTalk 2009 you can make query for running instances or in-progress instances which found in the New Query tab of the BizTalk Group.
After that you can filter you Query buy instance status, number of records, specific instances names,..etc.
if you find you orchestration in the result Right click the orchestration name and select Orchestration debugger as shown in the below image
debugorch Now after Orchestration debugger screen has been opened you can set you break point into any Orchestration shapes.
I Hope this help.

June 13, 2009 Posted by | Biztalk | , , | 3 Comments

BizTalk 2009 new features

With BizTalk, organizations are able to communicate with a variety of platforms and applications and Combining different systems into effective business processes is a challenging problem.Microsoft has released new version for BizTalk which is BizTalk 2009.just i will give you simple brief about the BizTalk 2009 new features.
Key new features in BizTalk Server are:

  • Better support for deploying, monitoring, and managing applications
  • Significantly simpler installation
  • Improved capabilities for Business Activity Monitoring (BAM)

kindly find the below new features of BizTalk 2009.

Updated Platform Support

BizTalk Server 2009 supports the latest Microsoft platform technologies, including Windows Server 2008 These platform updates enable greater scalability and reliability, and many advances in the latest developer tools.also the following are the enhancements in Windows Server System support.

  • Windows Server 2003 SP2 or Windows Server 2008
  • Microsoft Visual Studio 2008
  • Microsoft SQL Server 2008
  • .NET Framework 3.5
  • New Hyper-V Virtualization Support

    BizTalk Server 2009 takes advantage of the latest virtualization improvements included as part of Windows Server 2008 Hyper-V, which can lead to reduced costs through lower hardware, energy, and management overhead, plus the creation of a more dynamic IT infrastructure.

    Improved Failover Clustering

    By taking advantage of Windows Server 2008 clustering, BizTalk Server is now able to be deployed in multi-site cluster scenarios, where cluster nodes could reside on separate IP subnets and avoid complicated VLANs.

    Enhanced Business Activity Monitoring

    By expanding the out-of-the-box BAM functionality with SQL Server 2008 Analysis Services, BizTalk Server 2009 provides support for Unified Dimensional Model (UDM) cubes and scalable real-time aggregations, which enhances support for Microsoft Performance Point Server 2007.

    Enhanced Support for AS2

    Transmitting EDI transactions over the Internet is an increasingly popular alternative to sending and receiving EDI using value-added networks (VANs). Using the Internet for data exchange reduces costs, increases efficiency, and has advantages in terms of redundancy and scalability.

    To support this growing trend, BizTalk Server 2006 R2 introduced support for EDIINT AS/2 (Applicability Statement 2). AS/2 is a specification that enables transport of business data over the Internet in a safe and reliable manner. BizTalk Server uses AS/2-defined methods to send, receive, encrypt, decrypt, decompress, sign, and verify signatures between partners using HTTP over the Internet. BizTalk Server helps ensure the security of messages through the use of encryption keys, digital signatures, certificates, and non-repudiation.

    BizTalk Server 2009 introduces the following AS/2 features:

    • Drummond Group certified for multi-file attachment support, file name preservation support and interoperability.
    • Resend messages if an MDN has not been received within a specified time frame.
    • Send and receive multiple file attachments.
    • Preserve attachment file names.
    Enhanced Support for EDI

    Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically. It represents approximately 75 percent of all business-to-business electronic transactions and grows at about 5 to 7 percent per year.
    BizTalk Server 2009 builds on the core architecture of BizTalk Server 2006 and makes strides in all dimensions of application-to-application, business-to-business, and business-process automation.

    BizTalk Server 2009 improves EDI support with the following features:
    Dynamic EDI Envelope Generation:

    • Override EDI envelope settings at runtime by setting context properties.
    • Values configured in party resolution are used unless the specific value is overridden.

    Multiple Batches

    • Multiple batch configurations can be created for each party.
    • Batch lifecycle can be managed individually.


    • HIPAA schemas now support equivalent segments.
    New Application Life-Cycle Management (ALM) Support

    BizTalk Server 2009 provides support for Microsoft Visual Studio Team System 2008 Team Foundation Server, and enables development teams to leverage the integrated source control, bug tracking, support for team development, integration with Microsoft Office Project Server 2007, and support for automating builds by using MSBuild.

    Enhanced Developer Productivity

    BizTalk Server 2009 introduces a number of improvements to the underlying Visual Studio-based BizTalk project system, which enhances debugging support for artifacts such as BizTalk maps (XSLT), pipeline components, and XLANG orchestrations, and enables support for unit testing with Microsoft Visual Studio Team System 2008 Test Edition.

    Other Enhancements

    BizTalk Server 2009 improves recoverable interchange processing of validation failures by providing support for recoverable interchange processing for disassembly (DASM) and a validation stage within the pipeline. The WCF adapter has been enhanced to provide support for configurable transactions and the ability to choose the transaction isolation level in the WCF-Custom send adapter.

    February 25, 2009 Posted by | Biztalk | , , , , | Leave a comment