'BizTalk Server: 8 Tips And Tricks For Better BizTalk Programming

i have came across this really interesting tips about biztalk programming, it really summarizes most of the pitfalls that most developers fall into, and as we always say, it's all about design, you can do lots of things with Biztalk, and you can do them in many different ways, the most important thing is how to do things the right way... :)


Enjoy Biztalking :)

'BizTalk Server: 8 Tips And Tricks For Better BizTalk Programming,'bloggerForm','scrollbars=no,width=475,height=300,top=175,left=75,status=yes,resizable=yes

Any Element in Biztalk Schema

we had a working orchestration today that needs to send notification for the failed messages, one problem came around, the schema of the failed message doesn't match anything to given to the orchestration !!! ,

the solution was so simple, we created a new generic schema, that contained the same root node and under it the Magical "any" element node type.!!!

so now the notification orchestration will only check the root node , and it will accept the message no matter what elements come under the root... and that was IT :)

Cheers :)

Ahmed

(Cutting-Edge ) Get To Know Biztalk Session

I have uploaded the material for the demo i made in the cutting-Edge club biztalk session ...

click here


please feel free to contact me if you have an questions.


Cheers

Ahmed

Handling Different Flat Files in the Same Pipeline

I have been asked a while ago about what to do if you have different Flat file schemes arriving at the same location each with a different schemas.

converting flat file into XML files is done by the flat file schema wizard which requires that you create a custom pipeline to put the disassembling schema in it, so the first thing that pops up in your mind is , what if I receive different schemas on the same port ?? I can't make a custom pipeline for each type of schemas; So what I should do,, ??

actually, some prefer to take this "trick" to the orchestrations by passing the file as "passthrough" and the orchestration will decide which transformation map to use, but I'm personally against this option because this enforces tight coupling between the message types and the deployed orchestrations, also it will raise several issues in the deployment and versioning of the whole solution.


I have seen a solution Gilles' Web log where it extends the Flat file disassembler to create a new one that detects the schema type and applied the right transformation ..
here is a link

we have tried this solution and it worked nicely, it's not a simple solution though but it preserve the service orientation of the biztalk solution .

keep biztalking

Anti Patterns -- ( The worst you can do !!! )

I came across this really interesting article about the Worst you can do with Biztalk, it really sheds the light about the real working problems that I have seen in Biztalk Project, everybody asks about the business logic and where to place it correctly in Biztalk, I believe this article shows the best way to place your business logic

Click here


Keep up the patterns and Enjoy Biztalking :)

Old Lady Pwnz Mercedes Guy

Really Funny

Calling .NET Assembly from Biztalk Server 2006 Orchestration

I have working for a while on multiple Biztalk Server project and I have also recently delivered a workshop on this great product,,

I have decided to share the samples I have made during the workshop for those who are interested in learning this product.

one of the these samples shows how to call .NET assembly from an orchestration, all you have to do is simple, declare a variable and choose it's type to be from the class you created, initialize this file and then call it's method,,, !!! Very simple, isn't it.. ?

the class has to be a "serializable" class since all the objects in Biztalk are XML objects,

to download the complete application with source code Click here

have a nice time Biztalking :)

Cheers,
Ahmed