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

UK Connected Systems User Group – BizTalk Services questions

This Wednesday I’m attending the CSUG – The Hybrid Organisation (sold out!). During my evaluation of several Integration products (BizTalk / BizTalk Services / Neuron ESB / MuleESB) I had some concerns/questions on BizTalk Services. My goal is to get answers on the following scenario a) I receive a HTTP Post with an Xml Body payload b) This contains a signature which i need to validate c) Transform the Xml body payload to another Xml message d) Perform a HTTP Post with the new Xml message to an external HTTP url and sign the message e) Route the response back, similar to the aforementioned steps, where an error needs to be mapped to a dedicated error response Challenges I'm wondering how to cope with some of the following challenges in this scenario, and would like to know resource information available which addresses some of these challenges; Validating / Signing of messages A requirement is to validate the incoming message by inspecting an signature in the message
Read more

Setting up a build server with the BizTalk Deployment Framework

Image
This chapter describes the steps to a TFS Build Server to set up BizTalk deployment with the following functionality: • Build solution • Perform unit testing Using BizUnit • Create Deployment Packages Using BDTF • Deploy to Server Using R packages created in previous step • Create documentation BizTalkDocumenter For this the following steps are required: • Installation Components (30 min) • Configuring a build account (30 min) • Setting up the build service (30 min) • Scrum template installation (30 min) • Share for the build output directory (10 min) • Adjustments Build Template for use BTDF (30 min) • Design of build definitions (60 min) • Setting BTDF (60 min) • Use BTDF • Build execution / scheduling UPDATE (21-06-2013) - When using sharedassemblies, the following URL is a big help http://mohamedradwan.wordpress.com/2013/01/31/set-custom-assemblies-path-for-host-build-service-on-the-cloud/ - For viewing the basic instructions a video is available on the following blog http:
Read more