Considerations Before Installing BizTalk Server 2013 and 2013 R2
[Unless specifically noted, the content in this topic applies to BizTalk Server 2013 and 2013 R2.]
Before installing, consider the following:
- Account names – Use the default account names whenever possible. The BizTalk Server setup automatically enters the default accounts. If there are multiple BizTalk Server groups within the Domain, change the account names to avoid conflicts. If you change the names, BizTalk Server supports only <NetBIOS domain name>\<user> for service accounts and Windows groups.
- Account names with BAM Management Web Service – BizTalk Server does not support built-in accounts or accounts without passwords for the BAM Management Web Service User. The web service accesses the BizTalk Server database and these accounts may suggest a security threat.
Note Configuring BizTalk Server with these typs of accounts may succeed, but the BAM Management Web Service fails. Built-in accounts or accounts without passwords can be used for the BAM Application pool.
- BizTalk Assembly Viewer – Not supported on a 64-bit platform.
- Install and Uninstall – Uninstalling BizTalk Server requires manually deleting the BizTalk Server databases. If you are installing BizTalk Server as a developer or evaluator, use a virtual machine. If you need to reinstall, you can easily roll back the virtual machine without having to uninstall and delete the databases.
- 32-bit and 64-bit computers – There are few differences when installing BizTalk Server on 32-bit or 64-bit computer. The installation and configuration covers 32-bit and 64-bit computers. Any differences are noted.
- Workgroups - Installing and configuring BizTalk Server in the workgroup environment on a single computer is supported. SQL Server and BizTalk Server features and components are installed and configured on the same computer.
- Terminal Server – Installing BizTalk Server using Terminal Server running in application mode is not supported. See KB 832027.
- BAM Portal - If the BAM portal is configured on a website used by applications that are running .NET Framework 2.0, then create a new website for the BAM portal:
Create an IIS 7 web site
Create an IIS 8 web site
After creating the new website:
Open BizTalk Server Configuration.
Configure the BAM portal and select the new website from the BAM Portal Web Site list.
- Open BizTalk Server Configuration.
Read Proactivity in BizTalk Server. The whitepaper provides some great advice.
© 2014 Microsoft Corporation. All rights reserved.