BizTalk Server Installation Scenario
This article explains how to install and configure Microsoft BizTalk Server 2013 on a single computer (development standalone machine) running Windows Server 2012. This information will help you plan the installation and configuration of BizTalk Server 2013, applications and components on which it depends.
We will assume that the machine already have installed the operating system: Windows Server 2012 and latest critical Windows updates from Microsoft.
In this scenario I will perform a full installation of Microsoft BizTalk Server, with the exception of the deprecated SharePoint Adapter (SharePoint Services Service Side Object Model (SSOM)). The following components will be installed:
- Enterprise Single Sign-On (SSO).
- BizTalk Group.
- BizTalk Runtime.
- Business Rule Engine.
- BAM Tools and Alerts.
- BAM Portal.
- BizTalk EDI/AS2 Runtime
- Microsoft BizTalk Adapters
Important considerations before set up the server
There are some important considerations or suggestions, since some of these operations are not mandatory, that we can set before starting the installation and configuration of the server.
One of the downsides of dealing with a new version of Windows Server is figuring out where things have moved in the new release.
Join the Local Administrators Group
To be able to install and configure BizTalk Server 2013, you have to log on the server using an administrator account on the local computer.
To add a member to a local group using the Windows interface
- Press the “Windows key” to switch to Metro UI.
- Type “Computer Management” and click in “Computer Management” option on Apps menu.
- Right-click the group to which you want to add a member, click “Add to Group”, and then click “Add”.
- In the “Select Users, Computers, or Groups” dialog box, do the following:
- To add a user account or group account to this group, under “Enter the object names to select” , type the name of the user account or group account that you want to add to the group, and then click “OK”.
- To add a computer account to this group, click Object Types, select the Computers check box, and then click “OK”. Under “Enter the object names to select”, type the name of the computer account that you want to add to the group, and then click “OK”.
Change the Machine Name
An important consideration that you take into consideration is: if your computer name is longer than 15 characters, BizTalk Server Configuration will not work.
- Start by running the Server Manager from either the Start Screen or the Desktop.
- In the Server Manager Dashboard, click on “Local Server” on the left side.
- In the Server Properties for the Local Server, click in the “Computer name” property to be able to change it
- Click on the “Change” button to edit computer name and domain information, which will pop up this dialog:
Now you can finally change the name of the computer. You’ll have to reboot after you make this change.
Disable IPv6
IPv6 is the latest address protocol that will eventually replace IPv4. Windows Server 2012 kept this protocol enabled by default, but it is also a fact that IPv6 is not yet common and many software, routers, modems, and other network equipment do not support it yet. So it may be a wise approach to disable it for now. Also by turning off it will facilitate the process of detecting which port certain application are listening.
IPv6 can be disabled either through the DisabledComponents registry value or through the check box for the Internet Protocol Version 6 (TCP/IPv6) component in the list of items on the Networking tab for the properties of connections in the Network Connections folder. The following figure shows an example:
Turn off Internet Explorer Enhanced Security Configuration
Internet Explorer Enhanced Security Configuration established a configuration for your server and for Microsoft Internet Explorer that decreases the exposure of your server to potential attacks that can occur through Web content and application scripts. As a result, some Web sites may not display or perform as expected.
By default, Internet Explorer Enhanced Security Configuration is enabled on Windows Server 2012 and can be configured through Server Manager.
To disable Internet Explorer Enhanced Security Configuration (IE ESC) in Windows Server 2012
- Start by running the Server Manager from either the Start Screen or the Desktop.
- In the Server Manager Dashboard, click on Local Server on the left side.
- In the Server Properties for the Local Server, you’ll see the option for IE Enhanced Security Configuration. Click “On” to change the option.
- A dialog box appears, letting Internet Explorer Enhanced Security Configuration be enabled/disable separately for normal users and administrators, turn off both. After disable both options, click “OK”.
- Click the Refresh button at the top of the Server Manager and the IE Enhanced Security Configuration should now show as “Off”
Disable User Account Control (UAC)
User Account Control (UAC) is a security component that allows an administrator to enter credentials during a non-administrator’s user session to perform occasional administrative tasks.
Whenever you need to configure a Windows Server 2012 setting, even if you are logged on as the administrator – you need elevated privileges. This is by design, and part of the fierce security initiative in Windows Server 2012. Before you can complete any administrative task, the User Account Control manager pops-up with a ‘Continue’ message.
To Disable User Account Control (UAC):
- Press the “Windows key” to switch to Metro UI.
- Type “Change User Account Control Settings” or “UAC” and click in “Change User Account Control Settings” option on Settings menu.
- Select “Never notify me when…” to disable UAC.
Turn Windows Firewall Off
I always advise you to turn Windows Firewall on BizTalk Server.
To turn Windows Firewall off:
- Press the “Windows key” to switch to Metro UI.
- Type “Windows Firewall” and click in “Windows Firewall” option on Settings menu.
- Select “Turn Windows Firewall on or off” option
- And select the option “Turn off Windows Firewall (not recommended)” in both settings
Configure the Application Event Log
BizTalk Server setup keeps a record of events in the Application Event Log. Depending on the BizTalk Server features installed, the amount of space required in the log may exceed its limit. If the application event log runs out of space during BizTalk Server setup, the installation will fail. To prevent this from happening, you can change the settings in the Application Event Log.
To change settings in the Application Event Log:
- Press the “Windows key” to switch to Metro UI.
- Type “Event Viewer” and click in “Event Viewer” option on Apps menu.
- In the Event Viewer, expand Windows Logs.
- Right-click Application, and then click Properties. This opens the Log Properties dialog box.
- To see how much available space your log has, compare the Log Size field with the Maximum log size field.
- To provide more space in the event log, enter a higher number in the Maximum log size field.
- To enable overwriting of old events when the log becomes full, select Overwrite events as needed.
- To clear the log events, click Clear log.
- Click OK, to close the Event Viewer.
Install Critical Windows Updates
Before installing BizTalk Server or its prerequisites, make sure you have installed the latest critical Windows updates from Microsoft.
To install Windows updates:
- Press the “Windows key” to switch to Metro UI.
- Type “Windows Update” and click in “Install optional updates” option on Settings menu.
- Click “Check for updates” and if exist new updates available, install them
- If prompted, restart your computer
Related links
- BizTalk 2013 Installation and Configuration – Enable Internet Information Services (Part 2)
- BizTalk 2013 Installation and Configuration – Install Windows Identity Foundation (Part 3)
- BizTalk 2013 Installation and Configuration (Part 4) – Coming soon
- BizTalk 2013 Installation and Configuration (Part 5)
- BizTalk 2013 Installation and Configuration (Part 6)
- BizTalk 2013 Installation and Configuration (Part 7)
- BizTalk 2013 Installation and Configuration (Part 8)
