Thursday, March 03, 2011 4:03 PM
Hi, We are setting up a clustered 2 node BizTalk env. and want to Install ESB Toolkit 2.1.
I understand installing the toolkit should not be an issue on a cluster but I have no idea how we can install ESB Management portal on Production env. as we do NOT have Visual Studio install. The Installs scripts under source folder does require Visual Studio which we can NOT install in production env.
Please let us know the step by step guide on how we can install the Management portal without VS.
Thanks for your help. Looking forward to prompt reply.
Monday, March 07, 2011 12:10 AM
have you looked at this:
MCT, MCSD.NET, MVP
- Marked As Answer by Andrew_ZhuModerator Thursday, March 10, 2011 7:00 AM
Friday, July 27, 2012 12:50 PM
This is a NON-answer. Of course, you can JUST install the SDK on a production server.
No one thought this through. This appears to have been created by developers for developers. What about FOR Production? Does anyone have this answer or will those of us looking for the answer have to eventually create one for everyone else?
Friday, November 09, 2012 9:25 PM
i had the similar problem installing in a environment with WS 2008 R2, BT 2010 and no VS,so i followed the below steps to resolve it, by the way i only installed the core and management portal solution:
followed the guide that comes with ESB 2.1 download :Installing BizTalk 2010 ESB Toolkit 2.1.htm
install .net framework 4.0
Copy “C:\Program Files\MSBuild\Microsoft\VisualStudio\v10.0″ from the development machine to the target environment.
install the SDK win 7.1
Next run the Windows SDK 7.1 Command Prompt (Start => All Programs => Microsoft Windows SDK 7.1) and run:
C:\Program Files\Microsoft SDKs\Windows\v7.1> Setup\WindowsSdkVer.exe -version:v7.1
still all the projects related to management solution wont be installed when "management_install.cmd" is run, ESB.AlertService & ESB.UDDI.PublishingService will fail in the build.
you have to build these projects in the dev machine assigning the "key" to the projects, and use the msi/setup files to install in the target environement
rest just follow the steps in the guideline, finally you will be able to install the portal successfully.
Sunday, November 11, 2012 10:29 PM
I have not formally documented it yet, but typically I take the projects directory from my dev machine and copy it to my non-dev environments, in the install script comment out the build from the powershell script and run it, it I am doing multiple non-dev environments in the same group, I then also comment out the powershell script database create on all machines except the 1<sup>st</sup> one.
Bill Chesnut | BizTalk Server MVP | Mexia Consulting | Melbourne Australia
Please indicate "Mark as Answer" if this post has answered the question.