This also can work for multiple outputs to BizTalk Map also.

A recent post was asked how to take multipe messages and merge them into an output message structure. This actually puzzed me while I was learning the way BizTalk worked. Here is a simple example of how it works, and how to implement it…

1. The first thing this orchestration does is start off by consuming a trigger message.
2. It then constructs the calls to the two stored procedures
   
3. Then it calls the stored procedures and gets the responses from the stored procedures.
4. It then takes the two responses and invokes the map. Here is the picture of the input arguments to the map:
   
5. This is what the map looks like after you create the map with the multiple inputs:
   
6. It then creates the file an sends the resulting file out.
7. Here is the complete view of the orchestration:
   

Setup Instructions:

1. Extract this file
2. In the Properties of the project point to a strong named key file and set the BizTalkMgmtDB to your server
3. Run the included sql script against the Northwind database to create the stored procedures
4. Deploy the project
5. create 4 ports
• One input using Default XML pipeline and pointing to ..\MultipleInput\Input directory
• Two Static Solicit/Response ports pointing to the Nortwind database and setting the Document Target Namespace to be http://storedprocx/ (X being the number of the stored proc), setting default xml as both the Send and Receive pipelines
• One send port, setting the default xml pipline and pointing to the ..\MultipleInput\Output directory
6. Bind the logical ports to the physical ports created in step 5
7. Start the orchestration, drop the trigger in the Input directory, and you are good to go 

I am tired of constantly having to look up what the macros are for BizTalk

It seems that every client that I assist in implementing HL7, we get to testing the process and we send in an ADT, ORM, ORU, or some other message and we wait for the automated acknowledment, but it never comes.

I then remember that unless I have MLLP version 1.0.308.0, and 1.0.309.0 (current) of Microsoft.solutions.btahl7.mllp.dll I better camp out for a while, while I know it states that it can take up to 10 seconds to get the ack, I have gone to lunch and come back with no response. I even heard that there is a 24 hr delay. So make sure that you have the following patches from Microsoft for the HL7 adapter.

• KB893369: HL7 Interrogative transactions may take 10 or more seconds to complete when MLLP synchronizes communications end-to-end
• KB893404: The BizTalk Accelerator for HL7 sends an acknowledgement message to the source system after a long delay

Don’t forget to follow the post installation instruction on getting the send adapter to be a solicit/response as documented here.  

A recent post was written about attempting to query the DTADB database to capture data and send it to a particular customer. I suggested that this is a purpose in Business Activity Monitoring. I have created a sample application that demonstrates some of the powers of BAM.

In this example orders are processed by Biztalk, and key data elements are extracted and sent to the BAMPrimaryImport database.

Another orchestration takes the information in the database and creates a report and sends it out to the customer.

Setup Instructions:

1. Download this file.
2. Run the following command from a dos prompt to create the necessary BAM objects: \Tracking\BM.exe deploy ..\BAMReporting\ActivityInfo.xml
3. Run the extractBAM.sql against the BAMPrimaryImportDb
4. Deploy the solution
5. Modify the binding.xml file to represent your enviornment
6. Bind the ports using the Deployment wizard.
7. Enlist the orchestrations
8. Drop Order 1.xml, Order 2.xml, and Order 3.xml into the Input folder
9. Wait and then drop the Confirmation 1.xml, Confirmation 2.xml, and Confirmation 3.xml into the Input folder
10. Drop the Trigger.xml file into the input file and in the output folder there should be an email xml file that shows various BAM data.

This actually goes against my better concience on at least 2 fronts:

• BizTalk has the ability to do a lot of things, but sometimes it shouldn’t. I know of some people think that it is better than sliced bread, but a more elegant solution would be to use SQLReporting services that would go against the BAMPrimaryImportDB
• It uses a trigger file to kick off the report, there could be a better way, with a proper stored proc to do some marking of the data so no duplicate reports get run

In the BizTalk HL7 accelerator, you set up the port definition and assign the delimiters in HEX, but then if you are going to test it using the MLLP Send test tool, you have to use the Decimal equivalent. I am surprised that they did not include the following table as part of the documentation.

Also, one of the things not clearly explained is the promoted property DoorbellFinalMessage(BTAHL7Schemas.MSH1) = 124; this is the decimal version of |

Inside of the Hl7 Configuration Explorer, the tab for Acknowledgments, most of the fields in there were foreign when I first started dealing with HL7, so below is a list of the values and what they mean.

Acknowedgment Type:

I had forgot about this little document while at a client site, so here it is for reference:

If you have already developed BizTalk Server artifacts that use the native MLLP adapter you must delete and recreate them with the updated MLLP adapter.
To update the existing MLLP adapter
1.               Using Windows Explorer create the C:\MLLPTemp\ folder.
2.               Click Start, point to Programs, point to Microsoft Visual Studio .NET 2003, and then click Microsoft Visual Studio .NET 2003.
3.               In Microsoft Visual Studio .NET 2003, click View on the toolbar, and then click BizTalk Explorer.
4.               In BizTalk Explorer, expand erver name>.BizTalkMgmtDb.dbo, expand TwoWayAckReceivePort, expand Receive Locations, and then right-click TwoWayAckReceiveLocation, and the click Edit.
5.               In the Receive Location Properties - Configuration - General dialog box, in the Transport Type drop-down box select File.
6.               In the Receive Location Properties - Configuration - General dialog box, in the Address (URI) box click the ellipsis (…) button.
7.               In the File Transport Properties dialog box, in the Receive folder box, type C:\MLLPTemp\.
8.               Click OK.
9.               In the Receive Location Properties - Configuration - General dialog box, in the Receive Handler drop-down box select BizTalkServerApplication.
10.           Click OK.
Note  If you have any BizTalk Server artifacts configured using MLLP adapter, you must repeat steps 3-9 for each artifact before proceeding. Be sure to save the configuration information so that you can update the artifacts using the updated MLLP adapter. You must also save Receive and Send Handlers configuration information if you have customized the MLLP adapter.
11.           Click Start, point to Programs, point to Microsoft BizTalk 2004, and then click BizTalk Server Administration.
12.           In the BizTalk Administration Console, expand Microsoft BizTalk Server 2004 (Local), expand Adapters, right-click the MLLP from the list, and then click Delete.
13.           In the BizTalk Server Administration dialog box click Yes.
14.           In the BizTalk Administration Console, right-click Adapters, point to New, and then click Adapter.
15.           In the Add Adapter dialog box, in the Name box type MLLP, in the Adapter drop-down select MLLP, and then click OK.
16.           Close the BizTalk Administration Console.
17.           In Microsoft Visual Studio .NET 2003, in the BizTalk Explorer, click Refresh on the toolbar.
18.           In the BizTalk Explorer, right-click TwoWayAckReceiveLocation, and the click Edit.
19.           In the Receive Location Properties - Configuration - General dialog box, in the Transport Type drop-down box select MLLP.
20.           In the Receive Location Properties - Configuration - General dialog box, in the Address (URI) box click the ellipsis (…) button.
21.           In the MLLP Transport Properties dialog box, do the following:

22.           Click OK.
23.           In the Receive Location Properties - Configuration - General dialog box, click OK.