|Products Released||Lifecycle Start Date||Mainstream Support End Date||Extended Support End Date||Service Pack Support End Date|
|Microsoft BizTalk Accelerator for Financial Services 1.0 Enterprise Edition||3-12-2003||4-8-2008||4-9-2013|
|Microsoft BizTalk Accelerator for Financial Services 1.0 Standard Edition||3-12-2003||4-8-2008||4-9-2013|
|Microsoft BizTalk Accelerator for HIPAA 1.0 Enterprise Edition||12/30/2001||1-9-2007||1-10-2012||4/25/2003|
|Microsoft BizTalk Accelerator for HIPAA 1.0 Service Pack 1||4/25/2002||Not Applicable||Not Applicable||4/25/2004|
|Microsoft BizTalk Accelerator for HIPAA 1.0 Standard Edition||12/30/2001||1-9-2007||1-10-2012||4/25/2003|
|Microsoft BizTalk Accelerator for HIPAA 2.0 Enterprise Edition||2/15/2003||4-8-2008||4-9-2013|
|Microsoft BizTalk Accelerator for HIPAA 2.0 Standard Edition||2/15/2003||4-8-2008||4-9-2013|
|Microsoft BizTalk Accelerator for HIPAA 3.0 Enterprise Edition||12/28/2004||1-12-2010||1/13/2015|
|Microsoft BizTalk Accelerator for HIPAA 3.0 Standard Edition||12/28/2004||1-12-2010||1/13/2015|
|Microsoft BizTalk Accelerator for RosettaNet 1.0 Enterprise Edition||12/30/2001||1-9-2007||1-10-2012|
|Microsoft BizTalk Accelerator for RosettaNet 1.0 Standard Edition||12/30/2001||1-9-2007||1-10-2012|
|Microsoft BizTalk Accelerator for RosettaNet 2.0 Enterprise Edition||8/31/2002||10-9-2007||10-9-2012|
|Microsoft BizTalk Accelerator for RosettaNet 2.0 Standard Edition||8/31/2002||10-9-2007||10-9-2012|
|Microsoft BizTalk Accelerator for RosettaNet 3.0 Enterprise Edition||2/22/2005||4/13/2010||4/14/2015|
|Microsoft BizTalk Accelerator for RosettaNet 3.0 Standard Edition||2/22/2005||4/13/2010||4/14/2015|
|Microsoft BizTalk Accelerator for Suppliers 1.0 Service Pack 1||12-12-2001||Not Applicable||Not Applicable||12-12-2003|
|Microsoft BizTalk Accelerator for SWIFT 2.0 Enterprise Edition||9/25/2004||10/13/2009||10/14/2014|
|Microsoft BizTalk Accelerator For SWIFT 2.1 Enterprise Edition||7/21/2005||10-12-2010||10/13/2015||10/14/2008|
|Microsoft BizTalk Accelerator for SWIFT 2.1 Service Pack 1||9/25/2006||Review Note||Review Note|
|Microsoft BizTalk Accelerator For SWIFT 2.1 Standard Edition||7/21/2005||10-12-2010||10/13/2015||10/14/2008|
|Microsoft BizTalk Accelerator for SWIFT 2.3 Service Pack 1||9/25/2006||Review Note||Review Note|
|Microsoft BizTalk Adapter 1.0 for SAP||1/30/2002||4-10-2007||4-10-2012|
|Microsoft BizTalk Adapter 2.0 for mySAP Business Suite||10/20/2004||1-12-2010||1/13/2015|
|Microsoft BizTalk Adapter 2.0 for SAP||11-2-2004||1-12-2010||1/13/2015|
|Microsoft BizTalk Adapter for MQSeries 1.0||1/30/2002||4-10-2007||4-10-2012|
|Microsoft BizTalk Adapter for MQSeries 2000||12/30/2001||1-9-2007||1-10-2012|
|Microsoft BizTalk Adapter for MQSeries, v2.0||1/30/2002||4-10-2007||4-10-2012|
|Microsoft BizTalk Adapter for MSMQ 2.0||12-10-2004||1-12-2010||1/13/2015|
|Microsoft BizTalk Adapters for Host Systems||1/27/2007||4-10-2012||4-11-2017|
|Microsoft BizTalk Adapters for Host Systems 2.0||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk Adapters for Host Systems 2.0 Developer Edition||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk FileAct and InterAct Adapters for SWIFT||4-10-2007||4-10-2012||4-11-2017|
|Microsoft BizTalk Server 2000 Enterprise Edition||5-2-2001||7-11-2006||7-12-2011|
|Microsoft BizTalk Server 2000 Service Pack 1||5-2-2001||Not Applicable||Not Applicable||6/30/2002|
|Microsoft BizTalk Server 2000 Service Pack 1a||6/15/2001||Not Applicable||Not Applicable||3/30/2003|
|Microsoft BizTalk Server 2000 Service Pack 2||3/29/2002||Not Applicable||Not Applicable||3/29/2004|
|Microsoft BizTalk Server 2000 Standard Edition||5-2-2001||7-11-2006||7-12-2011|
|Microsoft BizTalk Server 2002 Enterprise Edition||4-1-2002||7-10-2007||7-10-2012||7-7-2004|
|Microsoft BizTalk Server 2002 Service Pack 1||7-7-2003||Review Note||Review Note|
|Microsoft BizTalk Server 2002 Standard Edition||4-1-2002||7-10-2007||7-10-2012||7-7-2004|
|Microsoft BizTalk Server 2004 Developer Edition||5/20/2004||7/14/2009||7-8-2014||4-11-2006|
|Microsoft BizTalk Server 2004 Enterprise Edition||5/20/2004||7/14/2009||7-8-2014||4-11-2006|
|Microsoft BizTalk Server 2004 Partner Edition||5/20/2004||7/14/2009||7-8-2014||4-11-2006|
|Microsoft BizTalk Server 2004 Service Pack 1||1/18/2005||Not Applicable||Not Applicable||1-8-2008|
|Microsoft BizTalk Server 2004 Service Pack 2||10/25/2006||Review Note||Review Note|
|Microsoft BizTalk Server 2004 Standard Edition||5/20/2004||7/14/2009||7-8-2014||4-11-2006|
|Microsoft BizTalk Server 2006 Developer Edition||6/23/2006||7-12-2011||7-12-2016|
|Microsoft BizTalk Server 2006 Enterprise Edition||6/23/2006||7-12-2011||7-12-2016|
|Microsoft BizTalk Server 2006 R2 Branch Edition||6/23/2006||7-12-2011||7-12-2016||4-12-2011|
|Microsoft BizTalk Server 2006 R2 Developer Edition||6/23/2006||7-12-2011||7-12-2016||4-12-2011|
|Microsoft BizTalk Server 2006 R2 Enterprise Edition||6/23/2006||7-12-2011||7-12-2016||4-12-2011|
|Microsoft BizTalk Server 2006 R2 Service Pack 1||4/27/2010||Review Note||Review Note|
|Microsoft BizTalk Server 2006 R2 Standard Edition||6/23/2006||7-12-2011||7-12-2016||4-12-2011|
|Microsoft BizTalk Server 2006 Standard Edition||6/23/2006||7-12-2011||7-12-2016|
|Microsoft BizTalk Server 2009 Branch||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk Server 2009 Developer||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk Server 2009 Enterprise||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk Server 2009 Standard||6/21/2009||7-8-2014||7-9-2019|
|Microsoft BizTalk Server 2013 Branch||6-12-2013||7-10-2018||7-11-2023|
|Microsoft BizTalk Server 2013 Developer||1-12-2014||4-9-2019||4-9-2024|
|Microsoft BizTalk Server 2013 Enterprise||6-12-2013||7-10-2018||7-11-2023|
|Microsoft BizTalk Server 2013 R2 Branch||7/31/2014||7-10-2018||7-11-2023|
|Microsoft BizTalk Server 2013 R2 Developer||7/31/2014||4-9-2019||4-9-2024|
|Microsoft BizTalk Server 2013 R2 Enterprise||7/31/2014||7-10-2018||7-11-2023|
|Microsoft BizTalk Server 2013 R2 Standard||7/31/2014||7-10-2018||7-11-2023|
|Microsoft BizTalk Server 2013 Standard||6-12-2013||7-10-2018||7-11-2023|
|Microsoft BizTalk Server Branch 2010||11/14/2010||1-12-2016||1-12-2021|
|Microsoft BizTalk Server Developer 2010||11/14/2010||1-12-2016||1-12-2021|
|Microsoft BizTalk Server Enterprise 2010||11/14/2010||1-12-2016||1-12-2021|
|Microsoft BizTalk Server Standard 2010||11/14/2010||1-12-2016||1-12-2021|
This post presents some useful suggestions for the Visual Studio Solution structure to use in BizTalk development. It is based on a copy from http://www.novaenterprisesystems.com. But this site is no longer available.
Generally I like to break my solutions up into the seven projects show below. I find that this meets the needs of most solutions, but it is not a hard fast rule. Some solutions will have more, others less, but each project is explained below.
External Schemas (.xsd files)
This project contains all of the schemas that are sent or received by the BizTalk solution. Port level mapping ensures no dependencies are leaked into or out of the BizTalk implementation. This would include schemas generated by adapter wizards, SOAP references, etc. It is vital that these be treated as what they really are: external artifacts (i.e. external dependencies).
Schemas (.xsd files)
The Schemas project contains all the schemas used internally by a BizTalk solution. These are schemas that are never exposed to any other systems and would be used to define entities within the actual solution. Every external schema should have a corresponding internal schema or translate to part of a composite schema.
Maps (.btm files)
The Maps project contains all maps within the solution. It references the Schemas and External Schemas projects and nothing else (with the exception of custom functoid assemblies). This is the guardian that prevents external dependencies from permeating a BizTalk solution.
Pipelines (.btp files)
All pipeline components (assemblers and disassemblers) are grouped in this project to make testing and maintenance easier. This project should reference the External Schemas project and /or the Schemas project if needed. Alternatively if you want to provide slightly more robust isolation you could create internal and external pipeline projects, but I really only recommend this if you need to call a Pipeline from within an Orchestration to avoid leaking a dependency into your Orchestrations layer.
Orchestrations (.odx files)
This project contains all Orchestrations used in the solution. It references the Schemas project and possibly the Pipelines project (if you’re using pipelines from within an Orchestration). Workflows can also exist in this assembly in BizTalk 2009.
Library (C#, resources, etc)
Any artifacts that are used by your solution should also be broken into their own projects. It is important to not let these bleed dependencies into your solution. If you have some custom components to do processing in an orchestration and some for custom functiods or pipeline components these should be broken into their own distinct projects.
Testing (.xml, .dtd, .cs files)
This project hosts all Unit and Functional tests and their supporting data. The only direct references should be to the utilities assembly and to the testing frameworks (e.g. NUnit and BizUnit). This also ensures a clean separation of tests and artifacts from the other parts of a solution.
Non Project Artifacts
There are also several Solution level folders I like to use to organize my solutions. These generally are:
- 3rdParty Assemblies – for storing any external assemblies and components the solution may need to utilize.
- Bindings – to store deployment bindings used in each of the environments you will have in your solution. I generally have Local Development, Integration, UAT, and Production.
- Build – used to hold build scripts.
Relative Path Locations
Always use relative path locations for all artifacts including:
- Keys used to sign assemblies
- References to other assemblies (i.e. project references not absolute references)
- Paths of test files
This will make it easier to build the solution on multiple machines and also make it easier to use a CI server to perform automated building of the solution.
Remember not all solutions will have these seven; some will have less others more, but keep in mind the separation of concerns brought up in the discussion about layers in a BizTalk solution. Later on I’ll cover some specific examples of when to combine which parts of this guidance.
It is natural and healthy to ask why go through all this trouble (ignore that creating projects in a solution is very simple; even more so with a template). Earlier I mentioned the need to control dependencies and this is a certain way to do that, but there are other reasons as well. You may find yourself needing to update in-flight Orchestrations or Maps in a solution with such Orchestrations. Perhaps it’s a simple fix and you haven’t quite worked out you versioning strategy. With separate assemblies you are free to deploy just the changes necessary rather than all assemblies and artifacts at once.
Perhaps more importantly you are also free to create packages that are specific to the type of server you are deploying them to. If you are working in a large BizTalk environment you may have a dozen or more servers partitioned by their functional role. You may want to create deployment packages for each role. This goes back to the previous discussion about Layers vs. Tiers. Building solutions in a separable manner is a good practice that allows administrators and operators more control over the solution once it is out of development. This is critical to the success of any enterprise software system and even more so to BizTalk solutions.
|Product||Lifecycle Start Date||Mainstream Support End Date||Extended Support End Date||Service Pack Support End Date|
|BizTalk Server 2013 R2||07/31/2014||07/10/2018||07/11/2023|
|BizTalk Server 2013||06/12/2013||07/10/2018||07/11/2023|
|BizTalk Server 2010||11/14/2010||01/12/2016||01/12/2021|
|BizTalk Server 2009||06/21/2009||07/08/2014||07/09/2019|
|BizTalk Server 2006 R2 SP1||04/27/2010||See notes||See notes||See notes|
|BizTalk Server 2006 R2||06/23/2006||07/12/2011||07/12/2016||04/12/2011|
|BizTalk Server 2006||06/23/2006||07/12/2011||07/12/2016|
|BizTalk Server 2004 SP2||10/25/2006||See notes||See notes||See notes|
|BizTalk Server 2004||05/20/2004||07/14/2009||07/08/2014||04/11/2006|
I was getting this error at a customer with a BizTalk WCF receive location (isolated): The address of the location was correct and running. When actually removing, or in my case renaming the uri address in the receive location, I still got an error but slightly different:
The second error is the expected error when the address is incorrect. After re-deploying, recompiling, everything the problem still persisted. Then the other ports in the same application pool started to complain with: “The Messaging Engine failed to register an adapter “WCF-BasicHttp”. Details:
“Registering multiple adapter types within the same process is not a supported configuration. For e.g. HTTP and SOAP receive adapters cannot co-exist in the same process”.
This error was not part of my problem. But it leads to Sandro’s blog page:
And then to Saravana:
Multiple Isolated Host (Host Instances) – Multiple Virtual directories – different adapters, what are the rules?
But the solution was much more simpler. Somehow my svc file got changed. Open it in notepad and change “BasicHttpHostFactory” or “CustomWebServiceHostFactory” to “CustomWebServiceHostFactory“. THAT’S IT!
I don’t know why the svc changed. some tfs, regenerating webservice issue?
Microsoft today released Microsoft SQL Server 2014, the foundation of our cloud-first data platform. SQL Server 2014 delivers breakthrough performance with new and enhanced in-memory technologies to help customers accelerate their business and enable new, transformational scenarios. In addition, SQL Server 2014 enables new hybrid cloud solutions to take advantage of the benefits of cloud computing with scenarios such as cloud backup and cloud disaster recovery for on-premises SQL Server installations. SQL Server 2014 continues to offer industry-leading business intelligence capabilities through integration with familiar tools like Excel and Power BI for Office 365 for faster insights.
We will also soon make generally available the SQL Server Backup to Microsoft Azure Tool, a free tool that allows customers to backup older versions of SQL Server to Azure storage.
Try SQL Server 2014 release today
Download and try the generally available release of SQL Server 2014 today on premises, or get up and running in minutes in the cloud. And, please be sure to save the date for the live stream of our April 15 Accelerate Your Insights event to hear more about our data platform strategy from CEO Satya Nadella, COO Kevin Turner and CVP of Data Platform Quentin Clark.
After configurating the BAM portal I was still getting this error:
“The server encountered a critical failure while trying to access the list of Views. The Business Management Web Service requires Administrator’s attention.
Use the navigation bar on the left to access Business Activity Monitoring views.
If the problem persists, contact your System Administrator.”
Normally this would be resolved by editing the config files of the 2 webservices:
<identity impersonate=”true” password=”<strong>registry:HKLM\SOFTWARE\Microsoft\BizTalk Server\3.0\BAM\WebServices\identity\ASPNET_SETREG,password</strong>” userName=”<strong>registry:HKLM\SOFTWARE\Microsoft\BizTalk Server\3.0\BAM\WebServices\identity\ASPNET_SETREG,userName</strong>” />
(see here for more details)
The error in the event viewer was:
(BAMPortal.navbar_ascx) Void OnPreRender(System.EventArgs): System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:8888 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object parameters) at Microsoft.BizTalk.Bam.WebServices.ManagementService.BamManagementService.GetViewSummaryForCurrentUser() at Microsoft.BizTalk.Bam.Portal.DataAccess.BamDefinition.BuildViewsCollection() at Microsoft.BizTalk.Bam.Portal.DataAccess.BamDefinition.EnsureViewsCollection() at Microsoft.BizTalk.Bam.Portal.DataAccess.BamDefinition.get_Views() at BAMPortal.navbar_ascx.OnPreRender(EventArgs e)
Connecting at port 8888???? Fiddler? So iis default uses the machines proxy settings of IE. Starting fiddler and the BAM was running! (or changing the proxy settings)
I’ve found a problem with message tracking in BizTalk 2009. Somehow tracking didn’t show op in the tracking database. The setting in the admin console however, was correct. And data went through BizTalk. The admin console:
SELECT * FROM BizTalkMgmtDb.dbo.StaticTrackingInfo WHERE strServiceName in( 'Microsoft.BizTalk.DefaultPipelines.XMLTransmit', 'Microsoft.BizTalk.DefaultPipelines.XMLReceive', 'Microsoft.BizTalk.DefaultPipelines.PassThruTransmit', 'Microsoft.BizTalk.DefaultPipelines.PassThruReceive')
update BizTalkMgmtDb.dbo.StaticTrackingInfo set imgData= 0×13000000 where strServiceName in( ‘Microsoft.BizTalk.DefaultPipelines.XMLTransmit’, ‘Microsoft.BizTalk.DefaultPipelines.XMLReceive’, ‘Microsoft.BizTalk.DefaultPipelines.PassThruTransmit’, ‘Microsoft.BizTalk.DefaultPipelines.PassThruReceive’)
The value of 0x00000000 somehow shows tracking on in the admin console, but actually does not track any info! The reason can be deployment script setting these values.
Now tracking also the messagebodies.