Checklist BizTalk Application Migration

Checklist BizTalk Application Migration V0.1

<Author>

Page 1

24-5-2012

Checklist BizTalk Application Migration Table of Contents:

1. GENERAL 2. HISTORY 3. PREPERATIONS BEFORE THE MIGRATION 4. DAY BEFORE THE MIGRATION 5. CHECK AND STOP THE BIZTALK APPLICATION 6. MIGRATE THE BIZTALK APPLICATION 7. START THE BIZTALK APPLICATION 8. AFTER THE INSTALLATION 9. APPENDIX
Hosts and Host instances

3 3 4 5 6 7 8 9 10
11

<Author>

Page 2

24-5-2012

Checklist BizTalk Application Migration

General
This document describes the steps which must be taken to perform a migration of a BizTalk application. Since each migration has its own specific matters, this document can be used as a template and can be modified for each specific migration. The document can be used for both Test as Live environments. However, since the server landscape can be different between these environments and file locations for all kind of migration scripts etc. might not be the same, any environment specific matters should be mentioned in the appendix of this document. Note: In case you have named your servers the same in both the Test and the Live environment, but you have scaled out in the Live environment, you can distinguish eventually non-existent servers in the Test environment by marking them with an asterisk in the column headers. File location of this document: C:\My Documents\Checklist BizTalk Application migration.docx

History
Date 13 March 2012 Version 0.1 Status Concept Description Initial version. Author(s) <Author(s)>

<Author>

Page 3

24-5-2012

Checklist BizTalk Application Migration

Preperations before the migration

Before the migration it might be necessary to create scripts which will be executed during the migration. You can think of scripts like database migration scripts etc. These scripts can be found in the location as mentioned in the appendix. Each script should contain the number of the step in this checklist when, during migration, the script must be executed, for instance by making that number part of the file name.
SQL Server Servers Internet Information Services Servers BizTalk Cluster Servers

BTS03(*)

0.1

Insert actions here Use bullets for keeping the overview Create script which does Store the script at the location mentioned in the appendix Make sure the script has a recognizable name Make sure to describe in this document when (or rather: at which step) the script has to be executed Place a capital X in the following columns to describe at which servers the script has to be executed

0.2

Insert actions here Use bullets for keeping the overview Prepare config files which have to change during the migration Store the file at the location mentioned in the appendix Make sure the file has a recognizable name Make sure to describe in this document when (or rather: at which step) the file has to be applied Place a capital X in the following columns to describe at which servers the script has to be executed

0.3

<Author>

Page 4

24-5-2012

BTS04(*)

IIS03 (*)

IS04(*)

BTS01

BTS02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

Day before the migration

The day before going live with a certain release, you can put installation files in place and want to make backups of binding files and all kind of configuration files. These backups will be stored at a pre-defined file location, which can also be written down in the appendix.

SQL Server Servers

Internet Information Services Servers

BizTalk Cluster Servers

BTS03(*) X X X

1.1

Copy the BizTalk installation files to the location from which they will be installed Copy the MSI(s) to C:\Temp\<Application + Version>

1.2

Make backups of the current configuration and store them to the location as written down in the appendix Make backups from: The BizTalk-config file (BtsNTSvc.exe.config) BizTalk Bindings BizTalk - The entire BizTalk Group and/or - Separate BizTalk applications X X X

1.3

Clean up any log file locations Especially the ones where the installation writes output

1.4

Resume any suspended messages or orchestrations Resume any suspended messages Resume any suspended orchestrations If they cannot be successfully resumed, fix the problem or terminate them

1.5

<Author>

Page 5

24-5-2012

BTS04(*) X X

IIS03(*)

IIS04(*)

BTS01

BTS02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

Check and stop the BizTalk application

The day of migration has arrived. When you are ready, you can start the migration by checking the environment. When everything is okay you proceed with stopping and undeploying the BizTalk application.
SQL Server Servers Internet Information Services Servers BizTalk Cluster Servers

BTS0 3(*) X

2.1

Check the state of BizTalk Full Backup If OK : continue with the migration If not OK : Make Full backup

2.2

Check the state of any singletons Check if any singletons have no more messages to process. Wait until they are processed or stop the Receive Location which receives the messages which are added to the queue of the singleton

2.3

Resume any suspended messages or orchestrations Resume any suspended orchestrations and/or messages

2.4

Stop the BizTalk Application Disable the Receive Locations Let BizTalk process running messages/orchestrations (until no more Active orchestratiions exist) Stop the host instances Unenlist the orchestrations Unenlist the Send Port and Send Port Groups

2.5

Resume any suspended messages or orchestrations Resume any suspended messages Resume any suspended orchestrations If they cannot be successfully resumed, fix the problem or terminate them

2.6

Undeploy the BizTalk application Stop (Full Stop) the BizTalk application and remove it

2.7

Uninstall the BizTalk application Uninstall the MSI (from the Control Panel) UnGAC the dlls

2.8

<Author>

Page 6

24-5-2012

BTS0 4(*) X

IIS03(*)

IIS04(*)

BTS01

BTS02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

Migrate the BizTalk application

Next the new BizTalk application will be installed. Make sure it is installed (and GAC-ed) and deployed on one BizTalk server and installed (and GAC-ed) on the remaining BizTalk servers.
SQL Server Servers Internet Information Services Servers BizTalk Cluster Servers

BTS03(*) X X

3.1

Import the MSI and install the MSI

3.2

Install the MSI

3.3

Make any needed modifications to the BizTalk config file Do this on all the BizTalk Servers

3.4

<Author>

Page 7

24-5-2012

BTS04(*) X

IIS03(*)

IIS03(*)

BTS01

BTS02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

Start the BizTalk application

After the BizTalk application is installed correctly, you can start it.
SQL Server Servers Internet Information Services Servers BizTalk Cluster Servers

BTS03(*) X

4.1

Start BizTalk Start the Host Instances Start the Send Ports Start the Send Port Groups Start the Orchestrations Start the Receive Locations

<Author>

Page 8

24-5-2012

BTS04(*) X

IIS03(*)

IIS04(*)

BTS01

BTS02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

After the installation

When the installation is completed and the BizTalk application is running smoothly, you might need to update your monitoring software.
SQL Server Servers Internet Information Services Servers BizTalk Cluster Servers

BTS03(*) X

5.1

Update monitoring software In case any infra changes have taken place, your monitoring software must be adapted to the new situation. You can think of matters like new/ changed/removed endpoints

<Author>

Page 9

24-5-2012

BTS04(*) X

IIS03(*)

IIS04(*)

BTS01

BTs02

DB01

DB02

IIS01

IIS02

Checklist BizTalk Application Migration

Appendix
Environment specific settings
In the table below you can write down any differences between your Test Environment and your Live Environment. You can think of things like file locations for backups or configuration files. Also any different End Point addresses can be mentioned here.
File location migrationscripts Location Backup config files, bindingfiles etc. BizTalk Send Ports URIs - <Name Send Port> - <Name Send Port> BizTalk Receive Location URIs - <Name Receive Location> - <Name Receive Location> Test Environment <File Location> <File Location> Live Environment <File Location> <File Location>

<address in Test Environment > <address in Test Environment>

<address in Live Environment > <address in Live Environment >

<address in Test Environment> <address in Test Environment>

<address in Live Environment > <address in Live Environment >

<Author>

Page 10

24-5-2012

Checklist BizTalk Application Migration

Hosts and Host instances

Part of the migration is stopping and starting your Host Instances. To remember which Host Instance runs on which Server, you can fill out the table below.

BTS03(*)

Host Name ReceiveHost

SendHost

ProcessingHost

TrackingHost

<Author>

Page 11

24-5-2012

BTS04(*) X X

BTS01

BTS02