BizTalk Server 2006 R2 Application Update

We have a BizTalk Server 2006 R2 application that we will be shipping this year, with several schemas that customers will use to create custom orchestrations. When we ship the next version of the app next year, chances are that these schemas (some of them are WCF service contracts) may change.

In this case, can we ensure minimal impact on user preferences / settings? Basically, the question is what is the strategy for updating BizTalk Server applications, that is, from one version of the application to another (and not BizTalk Server itself, which is also related to updating the question to 2009).

0


a source to share


1 answer


Check out the BizTalk Application Implementation Guide . These are excellent side-by-side partitions and use of MSI for upgrades.



0


a source







All Articles