• Connect to SAP load balancing server

    It turns out SAP is leveraging the same concept as BizTalk load balancing concept, with a message server and buntch of application servers. The connection should be setup to the message server instead of the specific application server behind it. This is something new, took me sometime to figure it out. Steps below, Change the […] Read more

  • HL7 Notes (3)

    The HL7 flat file disassembler use the logic below for body document spec, if party defined, use configured namespace, else use standard HL7 namespace append with #MSH9_1 append with #MSH9_2 append with #MSH12_1 without ‘.’ if MSH12_2 present append it, else append ‘GLO’ if MSH12_3 present append it, else append ‘DEF’ <still not clear> It […] Read more

  • How to trick BizTalk process all trigger events for a domain

    Problem is if you come up with a custom trigger event within a domain, i.e. ADT_ZZZ, the accelerator requires not only update the MSH schema, but also create the custom schema, i.e. ADT_ZZZ_231_GLO_DEF.xsd. It would be nice if to get rid of this behavior and a single schema handles all custom trigger event within a […] Read more

  • What’s inside HL72fDasm Component

    // if set passthrough to true, then this disassembler is a passthrough componentobject obj2 = inMsg.Context.Read(“PassThru”, “http://HL7Schemas.HeaderPropertySchema”);if ((obj2 != null) && ((bool) obj2))                {                    this.mCalledFirstTime = false;                    this.mMessageList[0] = inMsg;                }                Technorati Tags: BizTalk,HL7 // either individual or batch// determined by HL7DataReaderthis.mType=Individual // source partyMSH3_1, MSH_3_2,MSH_3_3 // ProcessIndividualMessage1) process message headerHL7MessageProcessor wrap documenspec i.e. http://microsoft.com/HealthCare/HL7/2X#MSH_25_GLO_DEFpass […] Read more

  • HL7 Notes (3)

    BTAHL7 Flat File Assemble Pipeline Component – single message a) read value from MSH5.1, 5.2 and 5.3, comnbine them together as destination party b) read message send port name, lookup for its destination party. If there is party configured for that port, override step a) c) if EnablePartialNameResolution is checked, search 5.1+5.2 then try 5.1 […] Read more

  • HL7 Notes (2)

    So working with HL7 is not that steep learning curve. Problem is there is lot to remember, by that I mean lots of table enumerations, data types etc. A lesson learnt today when I try to create a custom trigger event is, not only you change the namespaces, create a party definition, update the tables […] Read more