How To Install BizTalk 2000 on Microsoft Cluster Server

This article describes how to cluster BizTalk 2000 on a clean configuration. BizTalk 2000 is not a "cluster aware" program, but it can be set up to run in an active or passive mode by using MSCS generic resource types.

When you cluster BizTalk 2000, you can cluster the following:

• Microsoft Distributed Transaction Coordinator (MSDTC)
• Microsoft Message Queuing (MSMQ)
• SQL Server 2000
• Internet Information Server
• BizTalk Messaging
• XLANG Scheduler Engine
• XLANG Scheduler Restart Service (optional)

Requirements

The information in this article is based on the assumption that a baseline installation of the operating system and the Microsoft Clustering Service (MSCS) has been has been accomplished and tested. For information about how to install MSCS, please see the following "Step-by-Step Guide to Installing Cluster Service" Microsoft Web site:

Create a BizTalk Group

1. Start the Cluster Administrator (Cluadmin.exe) tool.
2. On the File menu, point to New, and then click Group.
3. In the Name box, type BizTalk Group, and then click Finish.
4. Move one or more physical disk resources to the BizTalk group.
5. Create an IP address resource and network name in that group.

For additional information about a related topic, click the article number below to view the article in the Microsoft Knowledge Base:

Install MSDTC

1. Log on to node 1, and then start Cluadmin.exe.
2. Move the BizTalk Group to node 1, and then move all other groups to node 2.
3. Copy the DTCLog folder from the SystemRoot\system32 folder to the shared disk that is the BizTalk group.
4. Right-click the BizTalk group, point to New, and then click Resource.
5. In the Name box, type MSDTC. In the Resource type box, click Distributed Transaction Coordinator, and then click Next.
6. Include every computer on the cluster as a possible resource owner.
7. Add resource dependencies for the network name and physical disk, and then click Next.
   
   NOTE: Leave this resource in an offline state.
8. At a command prompt, type comclust.exe, and then press ENTER.
9. At a command prompt on node 2, type comclust.exe, and then press ENTER.
10. Verify that the MSDTC resource is online, and then test failover.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base:

Install MSMQ

NOTE: Depending on whether you have Active Directory configured in your environment, choose the appropriate installation option for message queuing. Without Active Directory, BizTalk Server must always use local queues that result in much faster performance. The use of public queues provides greater flexibility and functionality.

1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
2. Click Add/Remove Windows Components.
3. Click to select the Message Queuing Server check box, and then click Next.
4. Repeat these steps on all other nodes in the cluster.
5. Start Cluadmin.exe, and then click the BizTalk group.
6. Right-click the BizTalk group, point to New, and then click Resource.
7. In the Name box, type MSMQ. In the Resource type box, click Message Queuing, and then click Next.
8. Click Next, to make every node a possible owner.
9. Add resource dependencies for the following items:
   • Network name
   • Physical disk
10. Bring the resource online, and then test failover.

Install Microsoft Visio 2000 (Optional)

Visio 2000 Standard Edition SR-1 is required for the creation of XLANG schedules for BizTalk orchestration. A trial copy is included on the BizTalk Server CD-ROM.

Visio 2000 should be installed if XLANG schedules will be created or edited. If BizTalk orchestration will be used, Microsoft recommends that you install Visio on all nodes in the cluster.

Install SQL Server 2000

Microsoft recommends that you install SQL into a group other than the BizTalk group to allow for manual load balancing of SQL and BizTalk across the nodes in the cluster. It is very important that you do not install SQL into the cluster group.

1. Insert the SQL Server 2000 Enterprise CD-ROM into your CD-ROM drive, and then click SQL Server 2000 Components.
2. Click Install Database Server, and then click Next.
3. Click Virtual Server, and then type the name you want to use for the virtual SQL instance.
4. At the Failover Clustering dialog box, type the IP address that will be used exclusively for SQL, and connectivity to it. Select the correct network that is associated with that IP address from the list.
5. Select a group that has a disk resource in it. This group should be a different group than the one that is to be used for BizTalk.
6. Leave all nodes selected as configured nodes for cluster definition, and then click Next.
7. Type the user ID and password for an account that has administrative rights on all nodes.
8. Leave the check in the check box to create a default instance, and then click Next.
9. Leave the installation paths at the default settings, start a Typical installation, and then click Next. SQL Server 2000 installs the binaries to the local node, and the databases to the shared disk.
10. Click Use the same account for each service, and then type an account that will be used to start the SQL service. Note that this account needs to be a domain-level account that is a member of the local administrators group.
11. Select the appropriate authentication mode (Windows Authentication mode is the default), and then click Next.
12. After the installation has finished on all nodes, click Finish.
13. Start Cluster Administrator ,and then test failover of the SQL group.
14. Apply service packs as required.

For additional information about related topics, click the article number below to view the article in the Microsoft Knowledge Base:

Install BizTalk Server

1. Start Cluster Administrator, and then move the BizTalk group to node 1.
2. Insert the BizTalk 2000 Enterprise Edition CD-ROM into the node 1 computer, and then run Setup.exe from the root folder.
3. At the Welcome screen, click Next, accept the license agreement, and then type the CD key.
   
   NOTE: Make sure that the setting for "Install this application for" is set to Anyone who uses this computer (all users).
4. Leave the default local destination folder path, and then click Next.
   
   NOTE: Do not install the binaries to the shared disk.
5. Choose a Complete installation, and then click Next.
6. Click Next to create a local security group with the default names.
   
   NOTE: Do not confuse this with a cluster group as this is a local security group.
7. Click This account, and then type an account that is to be used to start the BizTalk service. Click to clear the Start service after setup completes check box, and then click Next.
   
   NOTE: Microsoft recommends that you use the same account as the Cluster service uses.
8. Verify the configuration, and then click Install.
9. At the Messaging Database welcome screen, click Next.
10. Click Create a new BizTalk Messaging Management database, and then under SQL Server connection parameters, type the SQL virtual server name (that was created previously in the SQL installation section) in the Server name box, and then click Next.
11. Click Create a new BizTalk server group (unless you already have an existing BizTalk server group), and then click Next
    
    NOTE: Do not confuse this with a group that is within the cluster. This is a grouping of independent BizTalk servers that can work together to service requests, not a cluster group for failover.
12. Click Create a new Tracking database, and then under SQL Server connection parameters, type the SQL virtual server name (that was created previously in the SQL installation section) in the Server name box, and then click Next.
13. Select the dialog "Create a new Shared Queue database", then under the "SQL Server connection parameters", enter in the SQL virtual server name that was created previously in the SQL install section, in the "Server name" field, and click Next.
14. Verify that the BizTalk configuration is correct, and click Next and then Finish
15. Click Create a new default Orchestration Persistence database, and then under SQL Server connection parameters, type the SQL virtual server name (that was created previously in the SQL installation section) in the Server name box, and then click Next.
16. Click Finish to complete the installation on node 1.
17. Click Start, point to Programs, point to Administrative Tools, and then click Services.
18. Double-click the BizTalk Messaging service, change the startup type to manual, and then click OK.
19. Apply BizTalk 2000 Service Pack 1 or later, and then reboot the node.

Install BizTalk to Node 2

1. Start Cluster Administrator, and then move the BizTalk Group to node 2.
2. Insert the BizTalk 2000 Enterprise Edition CD-ROM into the node 2 computer, and then run Setup.exe.
3. At the "Customer Information" screen, make sure that the "Install this application for" setting is set to Anyone who uses this computer (all users).
4. Leave the default local destination folder path, and then click Next.
5. Select a Complete installation, and then click Next.
6. Click Next to create a local security group with the default names.
7. Click This account, and then type an account that is to be used to start the BizTalk service. Note that this must be the same account that you used when you configured node 1. Click to clear the Start service after setup completes check box, and then click Next.
8. At the Messaging Database screen, click Select an Existing Database, type the SQL virtual server name under SQL Server connection parameters, and then click Next.
9. At the "Configure a BizTalk Server Group" screen, click Select an existing BizTalk server Group, and then click Next.
   
   NOTE: The first cluster node should already be listed in the group.
10. When you are prompted to configure an orchestration database, click Select an Existing Database, type the SQL virtual server name under SQL Server connection parameters, and then click Next.
11. Click Start, point to Programs, point to Administrative Tools, and then click Services.
12. Double-click the BizTalk Messaging service, change the startup type to manual, and then click OK.
13. Apply BizTalk 2000 Service Pack 1 or later, and then reboot the node.

Configure BizTalk Server

1. Click Start, point to Programs, point to Microsoft BizTalk Server 2000, and then click BizTalk Server Administration.
2. Remove all of the servers that appear under the BizTalk Server group. For each computer that is listed in the server group, perform the following steps:
   1. In the BizTalk Server group, right-click the computer name, and then click Delete. Repeat this process for each of the node's names.
   2. Right-click the BizTalk Server group, point to New, click Server, and then type the BizTalk virtual network name (the name you created at the very beginning of this article).

Create the Cluster Resource for BizTalk Messaging

1. Start Cluadmin.exe, right-click the BizTalk group, point to New, and then click Resource.
2. In the Name box, type BizTalk Messaging Service. For the resource type, click Generic Service, and then click Next.
3. Click Next to make every node a possible owner
4. Add resource dependencies for the following items:
   • Network name
   • Physical disk
   • MSDTC
   • MSMQ
5. In the Generic Service Parameters window, type BTSSvc, and then click to select the Use Network Name for computer name check box.
6. Add the System\CCS\Services\BTSSVC key for registry replication, and then click OK.For additional information about registry key replication in a cluster, click the article number below to view the article in the Microsoft Knowledge Base:
   174070  (http://support.microsoft.com/kb/174070/EN-US/ ) Registry Replication in Microsoft Cluster Server
7. Bring the resource online.

WebDAV IIS Repository Configuration

1. Start Cluster Administrator, and then move the BizTalk group to node 1.
2. Copy the SystemRoot\Program Files\Microsoft BizTalk Server\BizTalkServerRepository folder to the shared disk that is in the BizTalk group.
3. Right-click the BizTalk group, point to New, and then click Resource.
4. In the Name box, type IIS WebDAV. For the resource type, click IIS Server Instance, and then click Next.
5. Click Next to make every node a possible owner.
6. Add resource dependencies for the BizTalk network name, IP address and physical disk.
7. On the Parameters screen, click WWW, and then click Default Web Site.
8. Click Start, point toPrograms, point to Administrative Tools, and then click Internet Services Manager.
9. Expand the default Web site under the cluster node.
10. Right-click BizTalkServerRepository, and then click Properties.
11. On the Virtual Directory tab, change the path to the folder in which you copied the files on the shared disk in step 2.
    
    Important: Make sure to perform this step on each computer in the cluster. When you are finished, bring the IIS WebDAV resource online.
    
    It is a good idea to rename the original BizTalkServerRepository folder on each node so that you can easily distinguish them and avoid confusion.
12. Click Start, point to Programs, point to Microsoft BizTalk Server 2000, and then click BizTalk Messaging Manager. The BizTalk Messaging Manager program starts.
13. On the Tools menu, click Options. Make sure that the name of the BizTalk server to which to connect is the name of the BizTalk Messaging Group network name. Move the resource group to the other node and verify again that BizTalk Messaging Manager can successfully use the virtual IIS network name.

For additional information about related topics, click the article number below to view the article in the Microsoft Knowledge Base:

Security Identity for the XLANG Scheduler Engine COM+ Program

1. Click Start, point toPrograms, point to Administrative Tools, and then click Component Services.
2. Expand Component Services/Computer/NodeName/COM+ Applications, right-click XLANG Scheduler, and then click Properties.
3. On the Advanced tab, click to clear the Disable Changes check box, click OK, and then click Yes.
4. Right-click XLANG Scheduler, and then click Properties. On the Identity tab, click This User, specify the account that is used to start the BizTalk service, and then click OK.
   
   NOTE: This must be accomplished on each node before you test failover.

Create Cluster Resource for XLANG Scheduler Engine

1. Start Cluadmin.exe, right-click the BizTalk group, point to New, and then click Resource.
2. In the Name box, type XLANG Scheduler. For the resource type, click Generic Application, and then click Next.
3. Click Next to make every node a possible owner
4. Add resource dependencies for the following items:
   • Network name
   • Physical disk
   • MSMQ
5. In the Generic Application Parameters window:
   
   
   • Under Command Line type:
     dllhost.exe /ProcessId:{DFDE2592-40A4-42BC-A35E-FD0BF76CA4D5}
   • Under Current Directory, type the root of the shared disk where BizTalk resides, for example, "T:\".
   • Click to select the Use Network Name for computer name check box.
   • Click to select the Allow application to interact with desktop check box.
6. Bring the resource online.

Create a Cluster Resource for the XLANG Scheduler Restart Service

1. Start Cluadmin.exe, right-click the BizTalk group, point to New, and then click Resource.
2. In the Name box, type XLANG Scheduler Restart Service. For the resource type, click Generic Service, and then click Next.
3. Click Next to make every node a possible owner
4. Add resource dependencies for the following items:
   • Network name
   • XLANG Scheduler Engine
5. In the Generic Service Parameters window, type BTWSvcMgr, and then click to select the Use Network Name for computer name check box.
6. Click Next, and then leave the registry replication page blank.
7. Bring the resource online and test failover.

There are many components to BizTalk, and you can implement these in several different ways. Although this article outlines the most common configuration, you can customize this configuration to meet your business needs. Please see the following whitepaper for detailed information about the different ways to implement BizTalk: