Checklist: Setting up a new BizTalk 2010 Environment

Posted: March 19, 2013  |  Categories: Biztalk Uncategorized
Tags:

One of my tasks is to configure and set up environments for clients. There are a lot of steps to remember and I tend to forget some every now and then, which is not a good thing. Therefor I decided to create a checklist that I use for all clients to verify that I don’t forget anything.

You can download the entire article as a PDF document.
Setting up a new BizTalk 2010 Environment.

I really wanted to share this with you all. I assume this will end up as a white paper at the end as well with a lot more information. As of now there are just steps without any good explanation. I started this paper not too long ago, and I’m sure there are many more steps that could be added. But use this as a guideline as it covers most of the aspects that needs to be done correctly for a good BizTalk installation and configuration.

Setting up a new BizTalk 2010 Environment

This is the case if you have clean machines, the first tasks should be done to all machines within the BizTalk Environment.

General before Installation of BizTalk and SQL machine

  • Install and run the Microsoft Baseline Security Analyzer
  • Install updates for Windows (update.microsoft.com)
  • Verify that all clusters are installed and only needed resources are clustered.
  • Move TEMP and TMP folders
  • Move Pagefile: http://support.microsoft.com/kb/307886
  • Enable IIS
  • Install WCF for IIS
  • Configure IIS to NLB or Cluster
  • Install Network COM+ under application server (roles)
  • BAM Specific: Install SQL Mgmt. Studio (full)
  • BAM Specific: Install SQL Server 2005 Notification Services
  • MQ Specific: Install prerequisites for MQSeries Agent
  • MQSC Specific: Install the MGSC Adapter before you install the WebSphare MQ Client
  • MQSC Specific: Install WebSphere MQ Client version 7.1 http://biztalkadmin.com/installation-of-the-mqsc-adapter-in-biztalk/
  • Install .NET Framework 4 and 3.5 SP1
  • SharePoint Specific: Install SharePoint Services 3.0 SP2
  • SharePoint Specific: Configure the SharePoint Service
  • SharePoint Specific: Extend default web sites as a virtual server
  • Disable shared memory protocol
  • Join local Administrator Group
  • Install and configure MSDTC
    • Verify DTC with DTC Tester
    • Disable real-time scanning on Antivirus (or add exceptions)
    • Disable all unused windows services
    • Add exceptions to firewall (external and internal)
    • Configure Event logs (size, duration of storage etc.).
    • Registry changes:
      • Update the LanManWorkstation parameters in the registry
      • Disable short-filename
      • DontVerifyRandomDrivers
      • NTFSDisableLastAccessUpdate
      • AdditionalDelayedWorkerThreads should be 16
      • AdditionalCriticalWorkerThreads should be 16
      • For Secure Intranets: Disable LDAP client signing requirements for computers
      • NtfsMftZoneReservation
        • 1 if volumes typically store fewer files.
        • 2 or 3 if volumes typically store a moderate number of files.
        • 4 if volumes typically store a large number of files.
  • MaxWorkItems should be 8192
  • Read more here: http://msdn.microsoft.com/en-us/library/ee377058%28v=BTS.10%29.aspx

 SQL Server Installation

  • Install SQL Server 2008 R2
    • Features:
      • Database Engine Service
        • SQL Server Replication
        • Full-Text Search
      • Analysis Service
      • Reporting Services
      • Shared Features
        • Client Tools Connectivity
        • Integration Services
        • Management Tools – Basic
          • Management Tools – Complete
          • Install any updates CUs or SP for SQL Server (MBSA)
          • Configure parallelism = 1
          • Enable TCP/IP and Named Pipes
          • Install Enterprise Single sign On
          • Configure Enterprise Single Sign on and SQL to work with the windows cluster
          • Add Master Secret Server to the SQL Cluster
You can download the entire article as a PDF document.
Setting up a new BizTalk 2010 Environment.

Install BizTalk

  • Install BizTalk Server on all of the BizTalk machines
  • Adapter Pack Specific: Install BizTalk Adapter Pack if requested or required
  • Install ALL CUs and SP for BizTalk
  • Adapter Pack Specific: Install BizTalk Adapter Pack CUs and SP
  • Configure the first server remember to Join SSO
    • Remember to change the names of the default hosts Recommended in-process host is send
  • Other server should just join group

After installation

SQL

  • Split log files and data files for the following databases on separate disk
    • BizTalkDTADb – two separate disks
    • BizTalkMsgBoxDb – Two separate disks
    • BizTalkMgmtDb and SSO – Share two disks
    • TempDb – two spearte disks, this database should be split into 10mb files
    • Turn off auto update and creation of statistics for the following databases
      • BizTalkDTADb
      • BizTalkMsgBoxDb
      • Set predefined size and auto growth for all databases
  • SQL Agent Jobs

BizTalk

  • Configure all hosts according to best practice and naming conventions.

Naming convention: http://social.technet.microsoft.com/wiki/contents/articles/6607.biztalk-naming-convention-en-us.aspx#Hosts

  • Update and fix all adapters (add the ones the client is going to use)
  • Verify that event tracking is set on the pipelines.
  • Verify windows cluster by clustering the hosts that should be clustered
  • Run Message Box Viewer
  • Run BizTalk Best Practice Analyzer
  • Test and verify that the cluster for hosts works
  • Set all hosts to delayed startup (only in stand-alone)
  • SMTP ONLY: Add default SMPT address under adapters
  • Set up Performance logging on all machines and point them to a file share
  • Configure PAL to run these logs once a week (PowerShell and Schedule Task)
  • Verify environment by using BizTalk Benchmark Wizard
  • Check Event Log for any errors
  • Check performance logs with PAL
  • Perform log shipping from SQL database
  • Install Enterprise Single Sign on to the new SQL Server or BizTalk Server
  • Mount BizTalk towards new Enterprise single sign on server
  • Verify solution by running a simple “pass thru” application.
  • Then fail back again.
  • Advice clients to do this once a year.
  • Delete all third-party testing tools
  • Clean message box
  • Clean Tracking database
  • Do a manual backup (right click message box choose backup)
  • Update ForceUpdate to value 1 (messageboxDb -> adm_BackupSettings)
  • Execute BizTalk Backup SQL Agent Job
  • Verify BizTalk Administration Guidelines
    http://social.technet.microsoft.com/wiki/contents/articles/7234.biztalk-administrator-guidelines.aspx
  • Hand over environment

General

  • Set up Performance logging on all machines and point them to a file share
  • Configure PAL to run these logs once a week (PowerShell and Schedule Task)
  • Verify environment by using BizTalk Benchmark Wizard
  • Check Event Log for any errors
  • Check performance logs with PAL
  • Perform log shipping from SQL database
  • Install Enterprise Single Sign on to the new SQL Server or BizTalk Server
  • Mount BizTalk towards new Enterprise single sign on server
  • Verify solution by running a simple “pass thru” application.
  • Then fail back again.
  • Advice clients to do this once a year.
  • Delete all third-party testing tools
  • Clean message box
  • Clean Tracking database
  • Do a manual backup (right click message box choose backup)
  • Update ForceUpdate to value 1 (messageboxDb -> adm_BackupSettings)
  • Execute BizTalk Backup SQL Agent Job
  • Verify BizTalk Administration Guidelines
    http://social.technet.microsoft.com/wiki/contents/articles/7234.biztalk-administrator-guidelines.aspx
  • Hand over environment

Disaster Recovery

  • Perform log shipping from SQL database
  • Install Enterprise Single Sign on to the new SQL Server or BizTalk Server
  • Mount BizTalk towards new Enterprise single sign on server
  • Verify solution by running a simple “pass thru” application.
  • Then fail back again.
  • Advice clients to do this once a year.

Set up environment ready for use

You can download the entire article as a PDF document.
Setting up a new BizTalk 2010 Environment.
  • Great list, Tord!

    Couple questions:
    * “…Then fail back again.” ??
    * “…Clean message box
    Clean Tracking database” – do you mean using the Terminator util?
    * “…Configure parallelism = 1” – BizTalk also installs db-s with this option. Do you mean to check it?
    * “…Delete all third-party testing tools” – do you mean delete MBV and PAL? not sure.
    * “…Run BizTalk Best Practice Analyzer” – MCS now is using MBV not BPA, all BPA features were moved to MBV, as I know.

    Again, it is a great list. I bookmarked it for the next projects.

    Cheers!
    Leo

    • Tord Glad Nordahl

      Well, I’ll go through it,
      1. Fail over: The reason I want you to fail back again is to double verify and to check both machines.
      2. Cleaning up the messagebox: can be done either by Terminator tool or Stored Procedures, you don’t want to hand over a “used” environment
      3. Parallelism: BizTalk does change this, but I’ve seen cases where the rule is “overwritten” later and you have to go in and change it again manually.
      4. Delete third-party tools: Yes, everything you installed, like MBV, PAL, BPA, BizTalk installation files etc.
      5: Run BPA and MBV: They give different results, go ahead and try it out!

      I know the list isn’t super explaining everything but that was never the intention I’d rather have it as a checklist, if you are uncertain about any of the points Google them or ask me! 🙂

  • Joakim Schütt

    Great list Tord,

    I too have questions. There is obviously a lot of different requirements from the customer that drives different choices in the list. It would be good to have a prerequisite in the beginning that you should have thoose requirements or to be part of the work digging them out!

    I also seen the same issues as Leonid have seen.

    But it is truly a great list and I have taken the liberty to translate it to swedish for our use here in Sweden! 😉

    /Joakim

    • Tord Glad Nordahl

      So, there is another paper that is related to this one, and that is the “prerequisites”. Basically making sure that our clients set up, and configure everything before we come. This may be SQL Cluster, Windows Cluster, NLB, users and NT-groups etc.

      Basically this is just to ensure that all steps during a configuration and installation is completed according to best practice, and to ensure that you are not missing any important steps, like configuring the SQL Agent jobs, or optimizing the registry on the machines.

      All of our clients have different demands, adapters, security etc. These settings are individual and we set them up accordingly, when I get new points or new bullets at clients I feel like I want to add to my document I do.

      I think it’s important that you use this as a baseline/guideline and just build it around your configuration and set up.

      – Tord

  • more detail would be interesting! Example: “•Move TEMP and TMP folders”… where to? 🙂

    • Tord Glad Nordahl

      Their own disks, not the windows disks.. Preferably fast disks.. 🙂

  • Tarun Garg

    Hello Tord,

    Great list…

    It really helps in planning BizTalk environment setup.

    Tarun…

  • Bharat

    Hi Todd
    Great List indeed .
    One small confirmation required…. when you say
    BizTalkDTADb – two separate disks
    BizTalkMsgBoxDb – Two separate disks
    BizTalkMgmtDb and SSO – Share two disks
    TempDb – two spearte disks, this database should be split into 10mb files

    Are we talking about a total of 2+2+2+2=8 separate disks ?
    If yes what size per disk you recommend ?
    It might be sometimes difficult to convince client to have these many disks. lets say we get 4 disk then what should be priority ?
    I believe BizTalkMsgBoxDb MDF and LDF are highest on priority ?
    Cheers

    • Tord Glad Nordahl

      Yeah, convincing is hard, usually you’ll end up getting what you want if you can argue good enough for it, remember diskspace is not expensive and it will simplify your life in the future if you have to migrate, move or swap around some disks to improve performance

One Platform Operations, Monitoring and Analytics Software
BizTalk360

microsoft biztalk

Learn more

Over 500 customers across 30+ countries depend on BizTalk360

ServiceBus360

Azure service bus

Learn more

Start managing your Azure Service Bus namespaces in minutes

One Platform - Operations, Monitoring and Analytics Software
BizTalk360

microsoft biztalk

Learn more

Over 500 customers across 30+ countries depend on BizTalk360

One Platform - Operations, Monitoring and Analytics Software
ServiceBus360

Azure service bus

Learn more

Start managing your Azure Service Bus namespaces in minutes

Back to Top