BizTalk Server: Basics principles of Maps – What are maps and where BizTalk can use them? (Part 2)

BizTalk Server: Basics principles of Maps – What are maps and where BizTalk can use them? (Part 2)

BizTalk maps are graphical representations of XSLT (Extensible Stylesheet Language Transformation) documents that allow us to perform, in a simple and visual manner, transformations between XML messages. We can enumerate the following standards used in the BizTalk Mapper: XML (Extensible Markup Language) – designed to transport and store data of messages; XML Schema (XSD – […]
Blog Post by: Sandro Pereira

BizTalk Server: Basics principles of Maps – Introduction (Part 1)

BizTalk Server: Basics principles of Maps – Introduction (Part 1)

Introduction Maps or transformations are one of the most common components in the integration processes. They act as essential translators in the decoupling between the different systems to connect. In this article, as we explore the BizTalk Mapper Designer, we will explain its main concepts, covering slightly themes such as product architecture, BizTalk Schemas and […]
Blog Post by: Sandro Pereira

Backup BizTalk: Don’t make ordinary Full backups

Backup BizTalk: Don’t make ordinary Full backups

Off course you make backups of your BizTalk databases! You have set the Recovery Model from the databases to Full and every single day your Maintenance Plans or (actually) the SQL Server Agent jobs make Full and Log backups. So in case you need to restore your BizTalk databases, you are safe…
Well, I’ve got some news for you… You’re not so safe…

If you make BizTalk Backups like described above, you could be in deep trouble in case you need to restore. When it comes to making backups from your BizTalk databases, Microsoft supports only one way….

Read this very nice written blog on how to backup Biztalk Databases the right way: Backup BizTalk: Don’t make ordinary Full backups

Lab: Deploy an Azure App. and explore the deployment thru RDP | Exercice: Déployer une App. Azure et explorer son déploiement via RDP

Lab: Deploy an Azure App. and explore the deployment thru RDP | Exercice: Déployer une App. Azure et explorer son déploiement via RDP


In this post, we’ll see how a Windows Azure application can be packaged from within Visual Studio 2010, then, you’ll have a chance to deploy this package to your Windows Azure environment and discover how the application is deployed by connecting to the virtual machines.Dans ce billet, nous allons voir comment une application Windows Azure peut %u00eatre packag%u00e9e depuis Visual Studio 2010, puis vous aurez l’occasion de d%u00e9ployer le package dans votre environnement Windows Azure et de d%u00e9couvrir comment l’application est d%u00e9ploy%u00e9e en vous connectant aux machines virtuelles.
This lab does not require you to install and configure a development environment on your machine. You only need a Web browser that supports Silverlight in order to connect to the Windows Azure management portal.Cet exercice ne requiert pas d’environnement de d%u00e9veloppement local. Vous n’avez besoin que d’un navigateur qui supporte Silverlight de fa%u00e7on %u00e0 vous connecter au portail de gestion Windows Azure.


The first video shows how the package was created from a machine where the development environment was installed (comments are in French).La premi%u00e8re vid%u00e9o montre comment le package a %u00e9t%u00e9 cr%u00e9%u00e9 depuis une machine avec l’environnement de d%u00e9veloppement install%u00e9.
Here are the resulting files that you can download locally so that you can use them in your own Windows Azure environment.Voici les fichiers r%u00e9sultants que vous pouvez t%u00e9l%u00e9charger localement de fa%u00e7on %u00e0 pouvoir les utiliser dans votre environnement Windows Azure.


skydrive folder

The password that protects the certificate isLe mot de passe qui prot%u00e8ge le certificat est



The default password for AdministrateurRD is the following.
NB: The last video shows how to change the credentials once the application is deployed.
Le mot de passe par d%u00e9faut pour AdministrateurRD est le suivant.
NB: La derni%u00e8re vid%u00e9o montre comment changer les cr%u00e9dentit%u00e9s une fois l’application d%u00e9ploy%u00e9e.



In order to get our own Windows Azure environment for free, you can use the trial version.Pour avoir votre propre environnement Windows Azure gratuitement, vous pouvez essayer l’offre de test pendant 90 jours.


The following video shows how to deploy the package, change and explore the application deployment (comments are in French).La vid%u00e9o suivante montre comment d%u00e9ployer le package, changer et explorer le d%u00e9ploiement de l’application.


If you want to change the remote desktop username or password or disable remote desktop, here is how you can do that (comments are in French):Si vous souhaitez changer les cr%u00e9dentit%u00e9s d’acc%u00e8s au bureau %u00e0 distance ou d%u00e9sactiver cet acc%u00e8s au bureau %u00e0 distance, voici comment faire:




Blog Post by: Benjamin GUINEBERTIERE

Changing directions

Changing directions

I generally try to write a blog each month about something I have been doing around BizTalk but lately I have been doing more and more work outside of the BizTalk world and I have not written anything. I have shifted to a new role in the company I work for, where I now give […]
Blog Post by: mbrimble

Microsoft and the open source community

Microsoft and the open source community

For the last decade, I have repeatedly, in my imitable
Microsoft fan boy style, offered an alternative view to commonly held beliefs
about Microsoft’s stance on open source licensing. In earlier times, leading figures in
Microsoft were very vocal in resisting the idea that commercial licensing is
outmoded or morally reprehensible. Many
people interpreted this as all-out corporate opposition to open source
licensing. I never read it that way. It
is true that I’ve met individual employees of Microsoft who are antagonistic
towards FOSS (free and open source software), but I’ve met more who are
supportive or at least neutral on the subject.
In any case, individual attitudes of employees don’t necessarily reflect
a corporate stance. The strongest
opposition I’ve encountered has actually come from outside the company. It’s not a charitable thought, but I
sometimes wonder if there are people in the .NET community who are opposed to
FOSS simply because they believe, erroneously, that Microsoft is opposed.

Here, for what it is worth, are the points I’ve repeated
endlessly over the years and which have often been received with quizzical scepticism.

a) A decade ago,
Microsoft’s big problem was not FOSS per se, or even with copyleft. The thing which really kept them awake at
night was the fear that one day, someone might find, deep in the heart of the
Windows code base, some code that should not be there and which was published
under GPL. The likelihood of this ever
happening has long since faded away, but there was a time when MS was running
scared. I suspect this is why they held
out for a while from making Windows source code open to inspection. Nowadays, as an MVP, I am positively
encouraged to ask to see Windows source.

b) Microsoft has
never opposed the open source community.
They have had problems with specific people and organisations in the
FOSS community. Back in the 1990s, Richard
Stallman gave time and energy to a successful campaign to launch antitrust
proceedings against Microsoft. In more
recent times, the negative attitude of certain people to Microsoft’s submission
of two FOSS licences to the OSI (both of which have long since been accepted),
and the mad scramble to try to find any argument, however tenuous, to block their
submission was not, let us say, edifying.

c) Microsoft has never, to my knowledge, written off the
FOSS model. They certainly don’t agree
that more traditional forms of licensing are inappropriate or immoral, and
they’ve always been prepared to say so.

One reason why it was so hard to convince people that
Microsoft is not rabidly antagonistic towards FOSS licensing is that so many
people think they have no involvement in open source. A decade ago, there was virtually no evidence
of any such involvement. However, that
was a long time ago. Quietly over the
years, Microsoft has got on with the job of working out how to make use of FOSS
licensing and how to support the FOSS community. For example, as well as making increasingly
extensive use of Github, they run an important FOSS forge (CodePlex) on which
they, themselves, host many hundreds of distinct projects. The total count may even be in the thousands
now. I suspect there is a limit of about
500 records on CodePlex searches because, for the past few years, whenever I
search for Microsoft-specific projects on CodePlex, I always get approx. 500
hits. Admittedly, a large volume of the
stuff they publish under FOSS licences amounts to code samples, but many of
those ‘samples’ have grown into useful and fully featured frameworks, libraries
and tools.

All this is leading up to the observation that yesterday’s
announcement by Scott Guthrie marks a significant milestone and should not go
unnoticed. If you missed it, let me
summarise. From the first release of
.NET, Microsoft has offered a web development framework called ASP.NET. The core libraries are included in the .NET
framework which is released free of charge, but which is not open source. However, in recent years, the number of
libraries that constitute ASP.NET have grown considerably. Today, most professional ASP.NET web
development exploits the ASP.NET MVC framework.
This, together with several other important parts of the ASP.NET
technology stack, is released on
under the Apache 2.0 licence. Hence,
today, a huge swathe of web development on the .NET/Azure platform relies
four-square on the use of FOSS frameworks and libraries.

Yesterday, Scott Guthrie announced
the next stage of ASP.NET’s journey towards FOSS nirvana. This involves extending ASP.NET’s FOSS stack
to include Web API and the MVC Razor view engine which is rapidly becoming the
de facto ‘standard’ for building web pages in ASP.NET. However, perhaps the more important
announcement is that the ASP.NET team will now accept and review contributions
from the community. Scott points out
that this model is already in place elsewhere in Microsoft, and specifically draws
attention to development of the Windows Azure SDKs. These SDKs are central to Azure development. The .NET and Java SDKs are published under
Apache 2.0 on
Github and
Microsoft is open to community contributions.
Accepting contributions is a more profound move than simply releasing
code under FOSS licensing. It means that
Microsoft is wholeheartedly moving towards a full-blooded open source approach
for future evolution of some of their central and most widely used .NET and
Azure frameworks and libraries. In
conjunction with Scott’s announcement, Microsoft has also released Git support
for CodePlex (at long last!) and, perhaps more importantly, announced
significant new investment in their own FOSS forge.

Here at SolidSoft we have several reasons to be very
interested in Scott’s announcement. I’ll draw attention to one of them. Earlier this year we wrote the initial
version of a new UK Government web application called CloudStore. CloudStore provides a way for local and
central government to discover and purchase applications and services. We wrote
the web site using ASP.NET MVC which is FOSS.
However, this point has been lost on the ladies and gentlemen of the
press and, I suspect, on some of the decision makers on the government
side. They announced a few weeks ago
that future versions of CloudStore will move to a FOSS framework, clearly
oblivious of the fact that it is already built on a FOSS framework. We are, it is fair to say, mildly irked by
the uniformed and badly out-of-date assumption that “if it is Microsoft, it
can’t be FOSS”. Old prejudices live on.

Start and stop BizTalk EDI batches in large scale

Start and stop BizTalk EDI batches in large scale

If you have been working with BizTalk and EDI Batches you would most likely have run in to problems with starting and stopping EDI Batches as this require you to go into a screen on the party to start and stop the EDI batch:

If you have a lot of EDI parties with batches on them then this is a big job to do if you need to import bindings as EDI batches must not be running when you import bindings with party information. There is an unsupported way around this.

When you press the start or the stop button you are sending a row into the PAM_CONTROL table in the BizTalk management database. And the BizTalk EDI Application have a receive location that looks for data in the table (through a stored procedure). So with a little bit of SQL magic we can stop every EDI batch that is running in the BizTalk Server:

— Stop EDI Batches
INSERT INTO [BizTalkMgmtDb].[dbo].[PAM_Control]
SELECT edi.PartyId as ‘DestinationParty’
      ,’EdiBatchTerminate’ as ‘ActionType’ –EdiBatchActivate
      ,GetDate() as ‘ActionDateTime’
      ,0 as ‘UsedOnce’
      ,p.nvcName as ‘DestinationPartyName’
  FROM EdiPartnerBatchSchedule edi inner join bts_party p
  on edi.PartyId = p.nID
  inner join PAM_Batching_Log pam on edi.PartyId = pam.PartyId and edi.BatchId = pam.BatchId

And if we want to start the batches again we can use this SQL magic (you have to specify which parties that you want enable batches for or some other criteria in the where section):

  — Start EDI Batches
INSERT INTO [BizTalkMgmtDb].[dbo].[PAM_Control]
SELECT edi.PartyId as ‘DestinationParty’
      ,’EdiBatchActivate’ as ‘ActionType’
      ,GetDate() as ‘ActionDateTime’
      ,0 as ‘UsedOnce’
      ,p.nvcName as ‘DestinationPartyName’
  FROM EdiPartnerBatchSchedule edi inner join bts_party p
  on edi.PartyId = p.nID
where edi.PartyId in (4,20)

A lot easier than going through the parties UI. I have only tested this on BizTalk 2009. I will update when I get a chance to test it on other BizTalk versions.