Sign in
David Hurtado's Integration Traces
Yet another blog about BizTalk, Architecture, and some fuzzy acronyms such as EAI, SOA, ESB, EDA, CEP, MSFLA, etc.
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Email Blog Author
RSS for posts
Atom
RSS for comments
OK
Search
Tags
BizTalk Server
Book
Archive
Archives
July 2009
(1)
June 2009
(4)
May 2009
(3)
April 2009
(1)
February 2008
(1)
July 2005
(3)
June 2005
(7)
May 2005
(5)
April 2005
(8)
Posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
David Hurtado's Integration Traces
Hierarchical naming convention for messaging artifacts
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Integration with messaging: Command messages and Document messages
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Team development with BizTalk: new white paper
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Schema design: do include support for Errors and Warnings
Posted
over 8 years ago
by
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....
David Hurtado's Integration Traces
Programming inside orchestrations: Where should I put the code?
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Orchestrations as Business Processes, not Technical Processes (Part 2, Development)
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Orchestrations as Business Processes, not Technical Processes (Part 1, Design)
Posted
over 8 years ago
by
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...
David Hurtado's Integration Traces
Introducing the blog (and myself)
Posted
over 8 years ago
by
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...
Page 1 of 1 (8 items)