BizTalk MSMQ userid and password in bindings file
I am setting up a batch file driven deployment solution to play - I have a bind file that works, but now I added to my MSMQ adapters - works on my local machine, but I found that I need to add a user id and password to make it work on the server itself - it's on the domain, my VM-dev is just a workgroup
Can I add user ID and password to the file? - seems unlikely since the password will have clear text in this case, but what is the solution - I seem to think something is wrt SSO, but this is an area where I was not close
source to share
You can put your user ID and password in any BizTalk binding that supports authentication, including MSMQ. For security, the password is not exported, you just get the mask.
The userName and password sections of the bind file are not exported unless they have been configured, so the easiest way is to configure the MSMQ send port with username and password manually and export the bindings - this forces items containing the username and masked password to be generated into the bind file ...
What you are looking for in your binding file is & lt; TransportTypeData> element of your MSMQ mail port. This contains all the configuration information for the adapter as encoded data.
Inside this element there is a userName and password section. The password will be masked with asterisks. Put your environment password here and import the binding.
Some of the encoded data with username and password will look something like this:
& amp; l; username & amp; GT; YOURUSERNAME & amp; l; / username & amp; GT; & amp; l; password & amp; GT; ****** & amp; l; / & password amplifier; amp; GT;
source to share
For security reasons, when exporting a binding, BizTalk Server removes the passwords for the bindings from the file. After importing the bindings, you must reconfigure the passwords for send ports and receive addresses before they will function. You configure passwords on the Transport Properties BizTalk Server Administration Console to send a port or get a location. For instructions, see How to Create a Send Port. See also How to create a Location reception.
From http://msdn.microsoft.com/en-us/library/aa558708.aspx
If you open the biding file however and scroll down to the properties line for the MSMQ adapter, you will find empty nodes. All you have to do is fill them in and the correct values, and they will be used the next time you import the binding file.
Of course, you'll have to remember to repeat this every time you export a new binding ...
source to share