biztalk

I have a little experience with BizTalk and am trying to understand BizTalk 2009 ESB Toolkit 2 without using it. Firstly, I am wondering whether anyone can clear up a couple of concepts for me: What is the difference between an "on-ramp" and a "receive port"? Why do you need itineraries, can you not simply create the same using ports and orchestrations? I am obviously missing something here. A couple of more general questions: Do all messages still have to go through the Message Box? Thanks in advance for any insight. On-ramps The on-ramps are web service based receive port but they are a bit

I'm trying to install CU6 for BTS2013r2 I run the exe, it unpacks then starts the wizard. It progresses or a while then presents the following message: I have the BizTalk ISO already downloaded from MSDN and mounted to the local server. So I browse to the correct path. Notice how the "File name:" text box of the select dialog has the filename miss-spelled as "aptersSetup.msi": I ignore this miss-spelling and select the "AdaptersSetup.msi" from the ISO image. I then get the following error: The wizard then backs-out the install of the AdapterPack and I run through the same problems for the

We all know that BizTalk is an commercial product from Microsoft for ESB (Enterprise Service Bus). What are other ready-made features which BizTalk supports over the AppFabric Service bus. Or in other words what does AppFabric Service Bus doesn't provide to the features of ESB ...? Is the term "Service Bus" misleading as far as the AppFabric Service Bus is concerned with respect to Enterprise Service Bus...? The BizTalk and AppFabric Service Bus teams at Microsoft are actually tightly collaborating and we (I work there) are integrating BizTalk's capabilities with AppFabric and Service Bus over

I am curious if it even makes consider BizTalk for the implementation of a pub/sub messaging architecture (basically what you can do with NServiceBus or MassTransit is all I really need). My manager tends to want to stick with frameworks provided directly from Microsoft and so as part of my due diligence as to which one to use I need to give a good set of pro/cons for both sides. Any guidance would be greatly appreciated! One of the major cons of a Broker is that it is very difficult to version and upgrade. You would have to stop the flow of messages to upgrade a particular endpoint(s). A

I've read it's good practice to split a BizTalk solution into multiple projects, and have seen some debate as to the exact nature of the split, e.g. ... - could be split by artifact, i.e. Schemas, Orchestrations, Maps, etc. - could be split by function But what's the benefits / con's ?? BizTalk solutions typically include schemas, maps, and orchestrations. Solutions can also include supporting components, Business Rules, definitions of port-based routing and transformations, trading partners, and several other types of artifacts. Effectively managing all of these artifacts has many benefits –

The company I work for recently started a project delving into the world of HL7 messaging and data trading. We are using BizTalk Server 2010 with the BTAHL7 accelerator for 2010 with success so far for HL7 v2 but now we have a need to accept HL7 v3 (CDA R2) documents. These are CCD's we will be accepting from an external vendor. I have the full suite of .xsd schemas from HL7 for CDA R2 (all 1541 of them) but am struggling with how to figure out which schemas relate to the messages we will be receiving. All I have to work with are test CCD messages from our trading partner and no other