BizTalk Deployment Framework (BTDF) 5.1 beta with BizTalk 2013 - Trying to deploy an application with SSO Settings


Recently i tried to get a BizTalk 2013 up and running. As i normally do, i use the BTDF to deploy the whole bunch of projects, so i downloaded the betaversion 5.1 from codeplex, and started the deployment. Unfortenately i ran into a problem when trying to deploy to the SSO store. I thought, let’s go crazy and enable SSO, unfortenately, this wasn’t a cakewalk, it wasn’t my birthday, but was certainly treated on some stuff i didn’t request, the pop-up;
clip_image002
And of course, the error that helps you out in tough times;
C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1684,5): error MSB3073: The command ""C:\Program Files (x86)\Deployment Framework for BizTalk\5.1\Framework\DeployTools\SSOSettingsFileImport.exe" "<…>" /settingsFile:"<…> " /userGroupName:"BizTalk Application Users" /adminGroupName:"BizTalk Server Administrators"" exited with code -532459699.
Build FAILED.   Problem My analysis is, that the BTDF is built against an older version of the SSO Interop Client. With the release of a new version of BizTalk 2013, the SSO Interop Client is also updated. This means that the reference to the BTDF project needs to be updated. Solution (workaround) Build a new version of the SSO executable / dll, using the steps mentioned below; 1) Extract the source The installation of the BTDF comes with the the source, which is located in a zip file. You should extract the source. clip_image003 And remove the readonly flag; clip_image007 2) Convert the SSOSettingsFileImport project to a VS2012 solution clip_image004 3) Analyse each project to determine if the reference is invalid a) Look at the reference clip_image005 b) Determine if the dll could be located clip_image006 c) Update the reference to the Interop SSO client for all projects that refer to this dll clip_image009 clip_image011 clip_image012 4) Update the target .Net framework version (due to references in the interop client) clip_image014 a) Update deprecated methods (Reflection LoadWithPartialName is not supported anymore) clip_image016 b) Replace with ‘Assembly.Load’ clip_image018 c) Rebuild clip_image020 5) Update the dll’s in the ‘DeployTools’ folder clip_image022 6) Deploy your BizTalk 2013 project! clip_image024   HTH,   Sander


UPDATE: Solved in beta2 (http://snefs.blogspot.nl/2013/05/biztalk-deployment-framework-btdf-51.html)



































Popular posts from this blog

Azure implementation guidelines

In My post ‘ Service Bus Management ’ I pointed out a way of implementing a DTAP strategy for managing the Service Bus environment. There’s now a great post available from Microsoft which goes into more detail about other aspects of managing the Azure subscriptions and other artefacts which is quite useful when setting up your Azure environments. Follow this link to the ‘Azure Implementation Guidelines’ HTH, Sander
Read more

Focus and innovation - recap of the last 2 years

It's been a long time since my last post. Hereby a partial explanation for that, with the note that this blog will remain active for the purpose of being a resource for historical references. My IT career started with programming, and adventures within holland, as well as overseas. When I realised programming is something you can specify, I figured that providing added value is crucial for a long term career and decided to focus on process centric roles. I started with webservice integration and eventually from that to process integration using BizTalk. The great feeling when discussing high level processes and implementing solutions within days, even highly scalable and interfacing with LOB systems is great. After several years of implementing solutions like these, I started questioning if all of this work was justified by the business case, if the solution was actually contributing, if the choices had been valid. In other words, I needed to understand the choices made. When...
Read more

Centralized SSO Application Configuration Data Store

Image
Reading application configuration data from a Single Sign-On database is a well-known concept within the BizTalk community. There are other means of retrieving application configuration data for BizTalk, yet retrieving them from SSO is the most powerful one. Microsoft has built an SSO Application Configuration Snap-In that provides a good user experience maintaining custom configuration data. With the Snap-In you will also get code for a .NET Helper Class to support retrieval of application configuration data in BizTalk. This approach has some major benefits. Your application configuration data is cached, has a built in refresh mechanism (ESSO Service) and is secure. What if you have a requirement that to remotely (from a non-BizTalk machine) retrieve application configuration data, because you like to benefit from SSO Config Store? Consider the following diagram In this scenario a mapping is implemented using a Functoid based on a shared helper class that reads the co...
Read more