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.
In my last post (http://www.biztalkadminsblogging.com/index.php/item/79-powershell-script-that-gets-biztalk-server-group-settings) I told you that I use library files with PowerShell code that I reuse. In this post I will describe how I import all library files into my script and how the library files actually work.
In my PowerShell scripts I often use the same functionality as in other PowerShell scripts. To prevent me from writing the same code over and over again I created a library with generic code that I can reuse. For example I often need the Management Db Server Name and the Management Db Name.
The script below has a function GetBizTalkGroupSettinginfo that BizTalk Server group settings. It fills variables that you can then use in your script. The script writes the output to screen to give you an idea of the information that is collected.
It’s always good to know what software is installed in our environment. Sometimes we need to know what version of BizTalk is installed or what version of the Adapter Pack, x86 or x64?
And preferably be able to get this list in an easy and automated way.
In an earlier post I posted a PowerShell script that automatically deploys BizTalk applications:
This version of the script stops when a older version of a BizTalk application that you are installing is detected. I had some discussions with other BizTalk admins and most of them wanted a ‘overwrite’ feature. I added this to a newer version of the script.