My scripts has two parts. One with different functions that I wrote and one part that encapsulates the functions and executes them in the correct order. As input I create an XML file that specifies which .msi packages that are to be deployed, which applications to remove/update/add, settings for the IIS virtual directories and so on. Since it is quite common during complicated deployments that something will err, I added functions to test run the scripts in advance. The test run simply checks for dependencies in the BizTalk configuration, making sure that applications can be modified as configured. It also checks that all files needed are provided in the setup package.
When creating the scripts, I briefly looked at using the BizTalk Deployment Framework and other extensions to PowerShell, but opted on developing it all in my own scripts. This due to several reasons, each quite strong in my case:
- I would learn more about PowerShell as well as the API:s and tools found in BizTalk
- I would know exactly where things could go wrong and what to do about it.
- It allowed me a greater flexibility since nothing was hidden in dll files or needed installation. As long as PowerShell was installed on the servers, the scripts would work. Nothing else is needed. This is also something that administrators liked. Some of them are a bit weary about installing "some stuff I found on the net".
Are you able to add some links to the blogs about your actual deployment scripts please?
ReplyDeleteI have not been able to post as much scripts as I've wanted to due to time constraint. There are a few bits up so far, but I'll try to get some more examples up asap!
DeleteHi Marcus,
DeleteCan we start up a conversation via email? I have added my email address on my linked-in profile page. I was hoping you can help to de-mystify the whole Biztalk Deployment.
Check your inbox!
Delete