Michael Stephenson

keeping your feet on premise while your heads in the cloud
posts - 356 , comments - 418 , trackbacks - 11

My Links

News

View Michael Stephenson's profile on BizTalk Blog Doc View Michael Stephenson's profile on LinkedIn

Twitter












Archives

Post Categories

Image Galleries

BizTalk

Mates

BizTalk Import MSI Binding problems

Problem

The probem we had was when trying to import an msi to biztalk on our system test environment we got errors because the password for our send port using the oracle db adapter was not being bound properly. The process we were using was as follows:

  1. Our build would build the solution and deploy biztalk components to the application
  2. We would add resources to the application (such as binding files for each environment)
  3. We would apply the bindings to the application
  4. We would start the application then run a number of BizUnit tests against it
  5. We would export the application to a binding file.

Upon investigation i found that although during the import we were specifying to use the binding file for system test (which had the correct password in it) it didnt seem to be applying these bindings it was mentioning a file called BindingInfo.xml.  It seems that when you export the application it takes the existing bindings as kind of defaults and try to apply these on import before adding the ones for your target environment.

Solution

The solution was to ensure that no bindings in the application when you export have the requirement for passwords, or even better have no bindings setup at all when you export and apply them all from the environment specific binding file during the import.  To manage this better we changed our build process to do the following:

  1. Our build would build the solution and deploy biztalk components to the application
  2. We would add resources to the application (such as binding files for each environment)
  3. We exported the application
  4. We would apply the bindings to the application
  5. We would start the application then run a number of BizUnit tests against it

This then worked fine when we import the msi, the default places the application there with absolutely no bindings.  Or if during import you specify an environment it will apply those bindings.

Note: With the system test and dev bindings, we had set those up manually in biztalk administrator and then exported them to an xml file.  We then manually placed the password in the bit where BizTalk placed a bunch of *** characters.  We then added the files as solution items and added the files as resources to the BizTalk application.  For other environments where the settings need to be more secure we would import the application with the default environment (apply no bindings) and then an operator with the appropriate priveledges would apply manually or from the command line the secure production bindings.

Applies To

This applies to any bindings where you have an adapter which requires credentials. 

Suggestion

I would suggest you use the changes we did to our build process even if you dont have bindings with passwords as you would just get hit by this if you added that at a future date. 

I would like to hear any thoughts or experiences others have had with this

Print | posted on Wednesday, October 11, 2006 9:55 PM | Filed Under [ BizTalk ]

Feedback

No comments posted yet.
Post A Comment
Title:
Name:
Email:
Comment:
Verification:
 
 

Powered by: