February 2007 Entries

BizTalk: Internals: Enlisted/Unenlisted; Started/Stopped; Enabled/Disabled. Errors and Suspended messages generated by Subscribers

Why some BizTalk artifacts can be Enlisted and Started and others can only be Enabled? What kind of errors depends on these actions (Enlisted, Started, Enabled)? One of the main rule of the BizTalk message system is: Only messages with subscription can come to the message system. System cannot "consume" messages without subscription, otherwise they would overfill it (messages without subscription would come into the message system but could not go out, noone want them.) There are two places where ......

BizTalk: Architectural Tips: Monitoring orchestration

Note: this orchestration is used for learning purpose. To monitoring in the real life we'd rather use the BAM and BAS. I can see this orchestration in the real environment only as a "lightweight" tool when using an additional technology (BAM/BAS) is not worth the time. Description: This is a singleton orchestration for monitoring other BizTalk applications. It can start/stop by the special "start/stop" message or whatever you want. It can work infinitely or on per day basis, or whatever you want. ......

BizTalk: Architectural Tips: "Shallow-copy schema"

Shallow-copy schema is compounded from namespace+root + <any> at most nodes + copies of the significant nodes . I use the Shallow-copy schema for reference to the complicated Schema, when I don't want the changes in this original schema would influence to the referencing project. Case 1: Project A has the complicated schemas. The project B has a reference to these schemas (to the first project). We expect these schemas could be changed. We won't change the project B. We expect the changes in ......