Modifying the Environment Settings file after deployment

Topics: Bindings File, Settings Management and SSO
Apr 15, 2013 at 8:55 PM

We have started using BTDF for our Biztalk deployments (Thanks for the great tool).

I am wondering how to deal with env settings excel changes. I can change the bindings on the admin console, however, that will make the env settings file on the server out of date and if I have to undeploy/redeploy the application, my changes are lost. So, if there is a need for binding changes, does it require me to build the installer and undeploy/redeploy? or can I modify the excel sheet on the server, for future deployments?

Please let me know what is the best way to do this (How to modify the env settings after the application is deployed)

Apr 16, 2013 at 1:22 AM
Hi Harini,

After deployment, settings for the particular enviornment defined inSettingsFileGenerator.xml(excel sheet) gets deployed to SSO. And you can edit those values from the tool.

Start->All Programs-><ApplicationName>->Deployment Tools->Edit SSO Settings

Now, if you want to permanently make changes, makes changes on excel sheet of course so that they can be deployed next time round.

Apr 29, 2013 at 5:16 AM
Hi Harini,

If you are not making code changes that require redeploying the whole application -- maybe you are electing to just re-GAC a pipeline components DLL or something similar -- and you want to change the Excel settings spreadsheet on the server to drive a bindings file token replacement, you can certainly do so. The file is in a nasty XML format, so you'd really want to use Excel to make the changes. If you change SettingsFileGenerator.xml in the installed location (\Program Files\MyApp\1.0\etc.), then it will be used with your changes for any undeploy/redeploy/deploy operation until you uninstall the MSI. The side effect is that uninstalling the MSI may not delete SettingsFileGenerator.xml because it is not identical to what the MSI originally installed.