We heavily use the BizTalk Deployment Framework to aid in the deployment of simple to complex BizTalk solutions. One of the greatest benefits is the ability to run custom deployment tasks and scripts. In previous blogs we have shown how to run a custom post deployment scripts in BTDF, today, we will show how custom scripts can be used to conditionally import a binding file during BTDF deployment.
BizTalk is great in its ability to store messages within the MessageBox even after processing failure, however its not always so easy to get those messages back out! I recently had a need to retrieve all messages that were currently suspended due to validation failures while attempting to generate X12 EDI messages using the Microsoft.Practices.ESB.
Typed Polling with WCF Adapters
It is very common to have a requirement in middleware design where we have to query SQL tables and retrieve some data when certein conditions are met.
The WCF-based adapters available with the BizTalk Adapter Pack enable the adapter clients to receive data-change messages from the SQL Server database(s). The adapter(s) support receiving “polling-based” messages wherein the adapter executes a specified SQL statement (SELECT statement or stored procedure), retrieves or updates the data, and provides the result to the adapter client at regular intervals of time. The adapters supports three types of polling:
Weakly-typed Polling (also called Polling),
Strongly-typed Polling (also called TypedPolling)
Xml-Polling polling using statements or procedures that include a FOR XML clause
For more information about the different types of polling, see Polling SQL Server by Using the SQL Adapter with BizTalk Server (http://go.microsoft.com/fwlink/?LinkId=221195).
Assumptions and prerequisites
This document is…
Last week month (sorry about that!), I wrote a post about using MABS to access a LoB system (in the example, SQL Server) behind several layers of firewalls (here).
We looked at the following tasks
Creating the BizTalk services
Setting up BizTalk Adapter Services in a local (or IaaS) environment to run a stored procedure in SQL Server
Creating a sample table and stored procedure
Creating a ServiceBus namespace with ACS
Create the Relay to the LOB system
Creating an EAI bridge to access the LoB system
This week, we’ll look at these tasks:
Testing and debugging the bridge with a Visual Studio add on
Writing a custom component to call the LoB adapter in a EAI Bridge Stage and parse the response
Having the component send an email notification using an Office 365 server
While building BizTalk projects within Visual Studio, it is possible to receiving the following error when trying to compile a project with multiple orchestrations:
“The namespace ‘[namespace]’ already contains a definition for ‘_MODULE_PROXY_’”
While the error seems obvious, in my case, the namespaces were indeed unique, such that the above error did not make much sense. The underlying issue was in fact that the type names of two of the orchestrations within the project were identical. It turns out that an orchestration was at one point duplicated, and only the namespace was changed. After making the type names unique, the project successfully compiled and deployed.
Having used Team Foundation Systems (TFS) for many years I grew accustom to having an automated build process and the ability to have the Revision number in my binary file versions. Recently I began work for a client that used SubVersion as their source control system. This removed much of the niceties I was used to having in other TFS based projects. I set out on a search of the internet and found a couple methods to provide similar functionality of tying a deployed package of code back to a revision in my source control.
Both of these methods require that you use the Tortoise SVN tool and have it installed on your local system. Since both of these methods do not require you to actually log into SVN to get the revision number, it is important to note that the…
Microsoft provides a useful tutorial (located here) for running a TFS Continuous Delivery configuration, and automatically publishing to Azure. This tutorial, while instructive, is somewhat out of date, and it may be useful to have a more personalized experience of building such a continuous deployment, while running through the instructions on the tutorial.
As may be the case for others, the TFS server used for running automated builds was already setup and configured, and the project to be built already linked to this server, so I won’t go into that here. The build server is running TFS 2013, and the ASP.NET MVC5 application being built and deployed is running on Visual Studio 2013.
After verifying the functionality of the build server, I created a package build in TFS Team Build. These configuration settings are for the most part self-explanatory, but the exact configuration in the…
There are a few common deployment errors in Microsoft Visual Studio when redeploying a previously deployed BizTalk project.
“Failed to add resource(s). Change requests failed for some resource. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Cannot update receive port “”. Transform “” not found”
Recently when deploying an application out to IIS we had the need to deploy a sub application within the same domain. Essentially, what we were trying to do was make the sub application an extension of the parent application, but live in separate app pools and the code base would be kept separate as well.
(ie: www.awesomeApp.com is the parent application and www.awesomeApp.com/subAwesomeApp is the separate sub application living in the same awesomeApp domain)
This is simple to set up in IIS, however, when we tried to deploy the second sub application we got this reoccurring error when we tried to hit www.awesomeApp.com/subAwesomeApp.
Server Error in ‘/subAwesomeApp Application.
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load type…
Lately I have come across this annoying little bug (feature?) of Visual Studio while working with BizTalk orchestrations. If an orchestration is opened in XML view and then closed, it will forever more insist on opening up in TEXT view.
As you can see, this is not very useful. Right clicking on the orchestration in Solution Explorer, then selecting Designer, then selecting “Set as Default” does not actually set it as default either. This might be an issue with not running Visual Studio as administrator. Though in some environments, running as an administrator may not be possible. Another different solution is to open up the .btproj file containing the offending orchestration.