April 2005 - Posts

Hierarchical naming convention for messaging artifacts
28 April 05 11:04 AM | dhtoran | 0 Comments   

Abstract : the use of a hierarchical naming convention allow to group messaging artifacts in a tree-like structure. note on conventions I’ve seen many different naming conventions for BizTalk, and I must admit that I haven’t found any suitable for me, Read More...

Integration with messaging: Command messages and Document messages
21 April 05 04:46 AM | dhtoran | 5 Comments   

Abstract : although the concept of document message and command message is quite simple, it’s usual to see document messages used for everything. At the highest level, integration is about communicating different applications. This communication can be Read More...

Team development with BizTalk: new white paper
21 April 05 04:41 AM | dhtoran | 0 Comments   

a must read for everyone working with BizTalk. It includes team development, best practices, approaches for versioning, etc. read at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/bts_2004wp/html/ffda72df-5aec-4a1b-b97a-ac98635e81dc.as Read More...

Schema design: do include support for Errors and Warnings
15 April 05 05:38 AM | dhtoran | 3 Comments   

Abstract : Schema designs usually contain some boolean Error-or-Success code to handle the result of the process. In an EAI scenario, schemas should contain at least support for a new result type: Warning . EAI communicates different applications. In Read More...

Programming inside orchestrations: Where should I put the code?
13 April 05 04:02 AM | dhtoran | 1 Comments   

Abstract : A common question from my customers: ‘how much code should be in the orchestration, and how much code should be leveraged into .NET components?’ In the BPEL standard, a business workflow is used only to coordinate the execution of components Read More...

Orchestrations as Business Processes, not Technical Processes (Part 2, Development)
08 April 05 01:34 PM | dhtoran | 2 Comments   

Abstract : Once I read a book that said: “A complex system that works is invariably found to have evolved from a simple system that works”. That’s right for orchestrations, especially because they mix business and technical elements. Let’s see an approach Read More...

Orchestrations as Business Processes, not Technical Processes (Part 1, Design)
07 April 05 04:11 AM | dhtoran | 8 Comments   

Abstract : In a Business Process Management oriented project, orchestrations are business processes, not technical processes. A common mistake (mistake from the BPM point of view) is to use orchestration designer as 'visual coding'. If you take the orchestration Read More...

Introducing the blog (and myself)
06 April 05 07:10 AM | dhtoran | 1 Comments   

Welcome to my brand new blog! this is my first post, so I'll try to set the expectations and introduce myself first. What you can expect from here: I'll post about BizTalk and integration stuff, such ideas related to BPM, EAI, SOA, etc., and probably Read More...