Ernesto is currently a Microsoft solutions architect, focusing on developing BizTalk solutions for banking. He has managed to combine the power the BizTalk platform with the power of programming in.NET Farmework towards applications easily scalable and maintainable, high availability environments.
Currently resides in Barcelona, Spain
It's been the time of my last Post, but not so this is a topic I have left behind.
Remember my previous Posts, in which we were using the PowerShell Provider to BizTalk
Based on the possibilities offered by the cmdlets included in PowerShell provider to BizTalk, we have developed a set of scripts. Each one of them performs specific functions, so it can be executed separately in the environment providing the necessary parameters.
This set of scripts performs the tasks of installation and upgrade that we need in our environment, as well as other necessary tasks in our distributions such as the creation of folders from Backup of the Assembly you are updating, to preserve the possibility of backtracking( if necessary) and the import of bindings.
All of us that somehow we are involved in the deployment and configuration of Microsoft BizTalk solutions know or have read about the existence of software packages, either owner or open source with aim of this cumbersome task. The reality is that there is not a unique solution to these issues, and in many cases we decided to implement our own strategies, based on the environment that we manage.
For this reason I would like to contribute to the community of BizTalk administrators/developers with this set of scripts developed in PowerShell and Visual Basic for Applications (VBA), which enable deployments on a large scale in a few minutes and maintaining guidelines imposed by the developments that we do.
In this series of articles I will explain the different steps that I have made to achieve a comfortable platform for deployment of BizTalk applications. It is neither more advanced nor more convenient method. It is simply another method.