Cluster Failover Systems & Technology Business Information Server for Microsoft Windows

Transcription

1 Cluster Failover Systems & Technology Business Information Server for Microsoft Windows

2

3 Contents. Introduction. 1 Information Common to All Installation Configurations. 2 Basic Cluster Configuration. 2 Sharing Tradeoffs for the Business Information Server 9.1 Application. 2 Preinstallation Cluster Configuration. 3 Common Procedures During Business Information Server 9.1 Installation. 8 Common Software Installation Procedures per Node. 8 Common Setup of the Database on the First Node. 10 Monitoring Web Page Availability. 13 Installing Interim Corrections in a Clustered Server. 14 Uninstalling Business Information Server 9.1 from a Clustered Server. 14 Sharing the Entire Installation. 15 Layout. 15 Description. 15 Installation. 16 Administration. 17 Sharing None of the Installation. 19 Layout. 19 Description. 19 Cluster Server Setup for Sharing None of the Installation. 20 Installation 20 Administration. 21 Sharing Only the Database Files of the Installation. 23 Layout. 23 Description. 23 Installation. 24 Administration. 28 Example. 29 Define the Cluster Group. 29 Preinstallation. 29 Software Installation per Node. 30 Set Up Database on First Node and Test. 30 Cluster Resources Setup. 30 Check Next Node. 31 Check Cluster Administration and Failover. 31 Appendix. 32

4 List of Figures Figure 1. Basic Cluster Configuration 2 Figure 2. Share Entire Installation Cluster Configuration 15 Figure 3. Share Nothing Cluster Configuration 19 Figure 4. Share Only the Database Cluster Configuration 23 List of Tables Table 1. Start Times Without Quick Start File 24

5 Introduction. This white paper describes several methods for using the Microsoft Cluster Server software to create a highly available installation of Business Information Server 9.1. Notes: This paper was written with the assumption that the reader has set up the Microsoft Cluster server and has a basic knowledge of Microsoft Cluster Server administration. It also assumes a good understanding of the installation and administration of Business Information Server. Some areas of this paper only apply to Business Information Server 9.1 with the ICE feature. If ICE is not installed, ignore references to Internet Information Server (IIS), Web site, Web browser, Gatetool, and Graphics Server. If ICE was not previously installed on your machine, do the upgrade to 9.1 first, and then repeat the installation process adding the ICE feature, which includes software and database changes. If you have a previous installation under MSWNT$1 (or equivalent) substitute your name for all references to BIS$1. Similarly MSWSITES correlates to BISSITES. Even though Business Information Server for Microsoft Windows 9.1 is not Microsoft Cluster Server (MSCS) aware, it is still possible to install Internet Commerce Enabler in a clustered environment. There are three basic configurations to choose from: Share the entire Business Information Server 9.1 installation Share none of the installation Share only the database files The recommendation is to share the entire Business Information Server 9.1 installation. This allows for the simplest administration environment and the most seamless integration with MSCS. This white paper includes the following sections: Information Common to All Installation Configurations Describes the basic cluster configuration and sharing tradeoffs. Preinstallation covers cluster restrictions and options, domain accounts, Business Information Server Application (BISA) cluster group, set up of MSDTC, and IIS with cluster failover. Common Procedures During Business Information Server 9.1 Installation Provides procedures common to all of the sharing configurations. Additional sections cover related installation issues. Share the Entire Business Information Server 9.1 Installation Lists the installation procedures and maintenance details. Share None of the Installation Lists the installation procedures and maintenance details. Share Only the Database Files of the Installation Lists the installation procedures and maintenance details. Example Provides a detailed example of the recommended installation. Appendix Provides optional procedures including material on detecting Web page availability. 1

6 Information Common to All Installation Configurations. Basic Cluster Configuration. The figure below shows a basic cluster hardware configuration. This is the basic layout that will be used for all configuration examples in this white paper. The cluster contains two nodes (A and B), with two local hard drives (one shown, labeled D), a heartbeat LAN connection and a shared disk subsystem with three hard drives (labeled Q, R, and S). Figure 1. Basic Cluster Configuration Sharing Tradeoffs for the Business Information Server 9.1 Application. Each configuration has both advantages and disadvantages. Share the Entire Business Information Server 9.1 Installation This is the recommended configuration for high availability Business Information Server 9.1. Advantages: Move or failover of the cluster group is both rapid and seamless. You only have to maintain one copy of software (one license required). You only have to maintain one database. Uses a single Business Information Server 9.1 site. Disadvantages: Only one node can operate the Business Information Server 9.1 Web site. Not possible to do a rolling upgrade. 2 Business Information Server for Microsoft Windows Cluster Failover

7 Share None This is not recommended because it has higher maintenance. Advantages: A node can operate independently as the sole possible owner. Multiple databases are possible. Multiple Business Information Server 9.1 Web sites are possible, but IIS must still match across the nodes. Rolling upgrade is possible. Disadvantages: Move or failover of the cluster group is rapid but incomplete; an inactive node will lose the IP connection and must be stopped manually. The common database must be manually synchronized. Maintenance cost of multiple copies of software with multiple licenses required. Share Only the Database Files This is not recommended. It has higher maintenance and inhibits high availability. Advantages: A node can operate independently as the sole possible owner. Multiple databases are possible. Multiple Business Information Server 9.1 Web sites are possible, but IIS must still match across the nodes. Rolling upgrade is possible. Disadvantages: Failover of the cluster group is not possible. Moving the cluster group requires a manual process. There is a maintenance cost of multiple copies of software with multiple licenses required. Preinstallation Cluster Configuration. Cluster Restrictions Do not install Microsoft Front Page Extensions with MSCS. Microsoft states that no Front Page Extensions can be used for clustering on Windows 2000 and If you want the.net framework, you must use Windows 2003, which has.net integrated. Do not install Microsoft.NET framework with MSCS on Windows Cluster Option Disk Write Through is required. Business Information Server 9.1 sites that participate in failover should have the Write-through to disk file on updates option selected. This will ensure that as many database updates as possible are written to disk prior to system failure. Cluster Network Setting See Recommended Private Heartbeat Configuration on a Cluster Server 3

8 IIS Domain Accounts for User-Ids and Groups Both IIS and Business Information Server 9.1 have user-id and security group requirements so that each processing node operates under domain accounts for all access rights. IIS needs two user-ids: IWAM_NETNAME and IUSR_NETNAME, where NETNAME represents the network name. Windows 2003 also has a built-in group, IIS_WPG, which does not need a domain group (this is addressed later). Business Information Server 9.1 installs the user-ids: MAPPERService, and MAPPERGuest and a group, MAPPER Users, into the local machine s account database. Access to database files and site information is restricted to administrators and the group account created at install time. In order for Business Information Server 9.1 to operate correctly in a shared environment, domain-based accounts will have to be created manually. If the machines in the cluster are domain controllers in the same domain, the accounts created by the installation are global to the domain to begin with, and these steps are not necessary. Following are the steps required to create the accounts: 1. Pick a domain for your accounts. The servers in the MS Cluster must be members of, or have a trust relationship with, the chosen domain. 2. Create two domain user-ids: IWAM_NETNAME and IUSR_NETNAME, where NETNAME represents the network name. These are used for IIS. Set Local Security Policy for IIS User-Ids Special user rights are needed for the domain user-id MAPPERService. Perform the following process on each node in the cluster: 1. Start Administrative Tools, Local Security Policy. 2. Select Local Policies, User Rights Assignment. 3. Modify every policy that has the local IWAM_NETNAME included. Each policy must be edited to include the domain form of domain-name\iwam_netname with the same rights. 4. Modify every policy that has the local IUSR_NETNAME included. Each policy must be edited to include the domain form of domain-name\iusr_netname with the same rights. Note: Be sure to perform this on each cluster node and policy. Set Up a Business Information Server Application Group Perform the following steps using the Cluster Administration tool: 1. Create one or more Business Information Server Application (BISA) cluster groups (either one per site or one per cluster, depending upon your sharing method). 2. Create an IP Address resource for each shared Business Information Server 9.1 object (either one per site or one per cluster, depending upon your sharing method). 3. Attach the IP Addresses to the appropriate resource groups. 4. Add the disk resource you used for your Business Information Server 9.1 installation to the Business Information Server 9.1 application resource group. 5. Add any other disk resources you may need for your Business Information Server 9.1 database files to the application group. 6. Create a directory on a shared disk resource for the Business Information Server 9.1 Web site home directory and in the directory, create a default.asp document. This is used later to check that IIS is properly installed for failover. It may be deleted later. 4 Business Information Server for Microsoft Windows Cluster Failover

9 Set Up MSDTC in a Cluster Group for Windows 2000 References How to Configure Clustered IIS Virtual Servers on Windows 2000 Advanced Server Failover Clustering Failover Clustering Dependencies Process Configure Computer Management, Services for Distributed Transaction Coordinator (MSDTC) to use a domain user account on both nodes. 1. Stop the service. 2. Configure the logon account (that is, MAPPER\MAPPERService). 3. Set Startup type to Manual. (Cluster services will start it.) 4. From C:\winnt\system32\, run comclust a Wait till it finishes and returns to a command prompt. 5. Repeat the steps above on each node, modifying the MSDTC service and running comclust. 6. On the node that owns the cluster group (and quorum disk) ensure there are no outstanding transactions and run msdtc resetlog 7. Check that you can perform Move Group on the cluster group to each owning node. At this point, you should be done with MSDTC setup. If you believe the MSDTC residing in the primary cluster quorum group is causing you problems, see the appendix section regarding the process of moving MSDTC outside the Cluster Quorum group. Set Up IIS for Cluster Operation for Windows 2000 References High-Availability Solutions Using Microsoft Windows 2000 Cluster Service Using IISSYNC to Synchronize Clustered Web Sites on Windows 2000 Advanced Server How to Configure Clustered IIS Virtual Servers on Windows 2000 Advanced Server 5

10 6 Business Information Server for Microsoft Windows Cluster Failover Process 1. Completely set up the IIS configuration and use the synchronization tool before adding it to the cluster. 2. Create the Business Information Server 9.1 Web site. For the Business Information Server 9.1 Web site, use domain user-ids so that the security is based on a common set of security ids. 3. Configure your IIS Web site(s) on one node of the cluster (that is, MAPCL1). 4. Go to drive C: and change the directory to C:\Inetpub\AdminScripts: Cscript //H:cscript (one time per node if never done, to set cscript as the host scripting engine.) adsutil SET W3SVC/WAMUserName domain\iusr_netname adsutil SET W3SVC/WAMUserPass "mapper" 5. Restart IIS. 6. Repeat on each node (that is, MAPCL2). 7. Add the Business Information Server 9.1 Web site on node 1 in IIS. Specify the cluster Web IP address and the shared drive information. For example, a home directory on shared disk R:\Web Stuff. Add a simple Web page that you can display to demonstrate that the Web site is working. 8. On the Business Information Server 9.1 Web site, change the anonymous user-ids to a domain user-id (MAPPER\IUSR_NETNAME). 9. Change the drive and directory to systemroot%\system32\inetsrv 10.Synchronize the Web sites on the other nodes in the cluster: iissync NODENAME (that is, MAPCL2) Even if you have Web sites that are only serviced by one node, IIS still must be synchronized to know all of the sites on all of the clustered nodes. 11.Check with a browser that you can view the Business Information Server 9.1 Web default page. 12.Add the new resource for the cluster IIS instance in the Cluster Administrator. 13.Enter the resource name (that is, Business Information Server 9.1 IIS). 14.Confirm the possible owner nodes MAPCL1 and MAPCL2. 15.Include the IP address, net name and disk(s) for the Web sites as resource dependencies. For parameters, check WWW and select the Web site by title (that is, Business Information Server 9.1 Web). 16.Bring the IIS resource online and then offline (test that it is unavailable) and then bring it online and test that the site works. 17.Move the ICE group to the other node and test that it works. 18.Move the group back to the first node and recheck that it works. 19.Check the failover policy.

11 Set Up MSDTC in a Cluster Group for Windows 2003 This step is done once for the cluster. No special instructions are needed. The default setup is sufficient. Set Up IIS for Cluster Operation for Windows 2003 References Under Setting up a new cluster in the Cluster Administration Help, see the topics New ways to do familiar tasks and Server cluster configuration. Also, see Checklist: Creating a clustered IIS Web or FTP service, which can be found online at Process 1. Create the Business Information Server Web site. For the Business Information Server 9.1 Web site, use domain\iusr_netname for security control. The location of the Web site default directory will depend on the sharing situation. If a Web site is going to be available for ownership by any node then it must reside on a shared physical disk. 2. Add a simple Web page to demonstrate that the Web site is working. 3. Configure the IWAM user-id for IIS as the domain IWAM_NETNAME. In Windows 2003, this is applied under the NETNAME, Application Pools (or one level deeper to DefaultAppPool) under Properties on tab sheet Identity. Stop and restart the DefaultAppPool. 4. Configure the IUSR user-id for the IIS Web site as the domain-name\iusr_netname. Go to the Properties of the Web site for your Business Information Server applications. Go to the Directory Security tab and click Edit in the Authentication and Access Control section. Enable Anonymous Access and then apply the domain-name\iusr_netname. If you are not using Anonymous Access then every authenticated user-id will have to be a member of the MAPPER Users group and have Local Security Policy privileges to match those assigned to domain-name\iusr_netname. Stop and restart the Web site. 5. Check with a browser that you can view the page you created in step Once the first node is working, you must synchronize the IIS configuration on all other nodes. In Windows 2003, you use IISCNFG.VBS /copy /ts NodeName /tu user-id /tp password to configure the IIS for each additional node. Even if you have Web sites that are only serviced by one node, IIS still must be synchronized to know all of the sites on all of the clustered nodes. 7. Add the new resource for the cluster IIS Web site resource to your Business Information Server Application group with the Cluster Administrator. In Windows 2003, you add Business Information Server 9.1 Web site as a Generic Script resource clusweb.vbs this does not refer to a specific Web site in Windows See the references at the top of this section for more information. 8. Move your Business Information Server application group to the other node and test that it works. 9. Move the group back to the first node and recheck that it works. 10.Check the failover policy. 7

12 Common Procedures During Business Information Server 9.1 Installation. The steps in this section are referred to by the installation procedures for each sharing configuration. Business Information Server 9.1 installation is designed for a single server installation. Software running in a cluster server must allow for sharing and movement of resources so extra steps are required to install Business Information Server 9.1 within a MSCS cluster group. Common Software Installation Procedures per Node. Revert Targeted Web Site Anonymous User-Id Before Installation Modify the IIS Web site you will be installing into. You must revert the anonymous userid from the domain IUSR_NETNAME back to the non-domain IUSR_NETNAME during the installation. 1. Install Business Information Server Create a domain user-id IWAM_NETNAME (with your network name) for IIS configuration. This will be used by IIS for all Web sites. 3. Create a domain user-id IUSR_NETNAME (with your network name) for IIS Anonymous user-access and place it in the domain MAPPER Users group. 4. Windows 2003 has an additional built-in IIS Worker Process Group named IIS_WPG, which has IWAM_NETNAME as a member as well as several built-in accounts. The group should not be added to the domain, but the domain account for IWAM_NETNAME should be added to the IIS_WPG group on each node. Without this step, the BIS Graphics Server will not function on both nodes. 5. Configure the IWAM user-id for IIS as the domain IWAM_NETNAME. For Windows 2000, this is applied at the NETNAME under Properties. For Windows 2003, this is applied under the NETNAME, Application Pools (or one level deeper to DefaultAppPool) under Properties on tab sheet Identity. 6. Configure the IUSR user-id for the IIS Web site as the domain-name\iusr_netname. Go to the Properties of the Web site for your Business Information Server applications. Go to the Directory Security tab and click Edit in the Authentication and Access Control section. Enable Anonymous Access and then apply the domain-name\iusr_netname. 7. Special user rights are needed for the domain user-id IWAM_NETNAME. Modify the Local Security Policy with the following process on each node in the cluster. a. Point to Start, Programs, Administrative Tools, and click Local Security Policy. b. Select Local Policies and then User Rights Assignment. c. Modify every policy that has the local IWAM_NETNAME included. It must be edited to include the domain-name\iwam_netname with the same rights. d. Modify every policy that has the local IUSR_NETNAME included. It must be edited to include the domain-name\iusr_netname with the same rights. e. Modify every policy that has the local MAPPERService included. It must be edited to include the domain-name\mapperservice with the same rights. 8 Business Information Server for Microsoft Windows Cluster Failover

13 f. Modify every policy that has the local MAPPERGuest included. It must be edited to include the domain-name\mapperguest with the same rights. g. Modify every policy that has the local MAPPER Users group included. It must be edited to include the domain-name\mapper Users group with the same rights. Isolating and Moving to a Node in an ICE Web Site Anytime you install on the next node, you must prevent failover during Business Information Server 9.1 installation so that all resources return to the installation target node after a reboot. 1. Using the cluster administration tool, open the BISA cluster group. All resources in the group should allow all nodes as possible owners. 2. Choose one resource to inhibit failover in the BISA cluster group. 3. Set the resource properties Possible Owner list to include the target node. 4. Move the BISA cluster group to the target node. 5. Set the resource properties Possible Owner list to exclude all other nodes. Do not allow the BISA cluster group to fail over until all participating nodes have been upgraded. Depending on your sharing option, you may be able to test an upgraded database on one node and still run the production database on the other node. However, failover must be prevented. To minimize the time you are running without failover of your BISA cluster group, it is recommended that you do upgrade testing on a different host server. Upgrading with Shared Database Files Upgrading the database is an integral part of installing the software, so never run upgraded Business Information Server software against a database that is not upgraded. As of level 9.1, the installation program will try to upgrade the database for each site belonging to the installation instance. The program cannot upgrade a site if the site database is not available. Failing to upgrade a site database is a nonfatal error and the installation proceeds to upgrade the other sites if they exist. If you have one BISA cluster group, performing the database upgrade a second time on a database does no harm when you upgrade the subsequent node(s). If you have more than one BISA cluster group, isolate each BISA cluster group as described above in Isolating and Moving to a Node in an ICE Web Site. For each BISA cluster group, chose one resource and set a single possible owner, the target node, for immediate upgrade or a different node for subsequent upgrade. Defer New Database Installation 1. When the installation prompts to select the site letter, be sure to clear Install Database. Business Information Server 9.1 software is installed normally on each node of the cluster. Database files and shared Business Information Server 9.1 sites will be added administratively after the domain account and file security steps have been taken. 2. Depending on whether the default Web site was deleted, you could get installation error messages. Click OK through them and the installation will complete. 3. During installation, answer No to the request to reboot. You will have to reboot later. 9

14 Common Setup of the Database on the First Node. Setting Up the Domain and Group for Business Information Server 1. Ensure that domain-name\mapperguest is a member of the domain-name\mapper Users group. Use the same password specified for this user-id during the Business Information Server 9.1 installation. 2. Ensure that domain-name\mapperservice is a member of the domain-name\mapper Users group. Use the same password specified for this user-id during the Business Information Server 9.1 installation. The password at the time of installation is used to set up the MPR controller; it can be configured by performing the following steps: a. Point to Start, Programs, Administrative Tools, and then click Services. b. Select MPR Controller, right-click, and then click Properties. c. In the Properties dialog box, click the Logon tab. 3. Check domain-name\mapper Users group. This group will have access to the application and database files. Members will include the domain user-ids MAPPERService, MAPPERGuest, IUSR_NETNAME, and any other user-ids that use Business Information Server 9.1 software. 4. Edit the system registry so that the Business Information Server 9.1 software uses the correct domain and user-ids. a. Run REGEDIT.EXE on node 1 of the cluster. b. Move to HKEY_LOCAL_MACHINE\SOFTWARE\Unisys\MAPPER System\Services. c. Modify the DomainName key to specify the domain of the new accounts. d. Modify the GroupName key to specify the group account (if not MAPPER Users). 5. Place the domain-name\mapperservice in the Administrators group on each server in the cluster. 6. If you are using a different user-id for Business Information Server 9.1 administration, create a domain user-id and place it in the MAPPER Users group. It should be a member of the MAPPER users group. This user-id is intended for use by Business Information Server 9.1 Administration program (under Start menu, Programs) but is not needed for the ICEADMIN run. Both IIS and Business Information Server 9.1 have user-id and security group requirements so that each processing node operates under domain accounts for all access rights. IIS needs two user-ids: IWAM_NETNAME and IUSR_NETNAME, where NETNAME represents the network name. For Windows 2003, an additional built in group IIS_WPG is not added to the domain (this is discussed below). Reset Services and Components for Business Information Server 1. Point to Start, Run, and then enter cmd. Go to the installation directory (X:\BIS$1) and at the prompt, enter the following lines: cd shared..\cisesctl.exe service mpr_svc.exe service mdllhost.exe regserver..\utrace.exe regserver..\bisworkshopsvr.exe -regserver 2. Close the command prompt. 10 Business Information Server for Microsoft Windows Cluster Failover

15 Component Services Changes for User-Id and Group-Id Modifications You need to configure the component access rights by pointing to Start, Programs, Administrative Tools, and then selecting Component Services to regulate access for the domain\mapper Users group instead of the local MAPPER Users group. For Windows 2000 you run dcomcnfg for DCOM Config changes, and then Component Service under the Adminstrative Tools for COM+ Applications. For Windows 2003, both DCom and COM+ are combined in the Component Services tool. In COM+ Applications, check these applications: IIS Out-of-Process Pooled Applications IIS-{Web site//root/cisystem/gatetool} IIS-{Web site//root/ice/examples} IIS-{Web site//root/ice} For each of these applications, go to the Properties dialog box, click the Identity tab, and change the account under which the application will run to domain-name\iwam_netname. In DCOM Config, you need to correct the following three components: mdllhost, Utrace, and BISWorkshopSvr. For each one, go to the Properties dialog box, click the Security tab, and then edit the launch and access permissions to Allow Launch and Allow Access for the domain-name\mapper Users. For more information, see COM Client Security and Modifying Launch Permissions in the Business Information Server Administration Guide. You must allow or deny launch permissions for the Business Information Server software as your business site security policy dictates. The topics in the Business Information Server Administration Guide will identify the process for selectively or broadly permitting COM access for the domain\mapper Users group. Launch permissions also implies that the domain\mapper Users group is able to read the file containing the allowable COM application (.dll or.exe). File Access Modifications All files associated with the Business Information Server 9.1 database and site information storage are created such that casual users of the server have no access. Administrators of the machine (or domain) and members of the MAPPER Users group are given access appropriate to their usage of the Business Information Server 9.1 software. For clustered installations, permissions must be modified on some of the files created by the installation. The newly created domain MAPPER Users group should be added to the security descriptors for the files specified below. The permissions granted need to be the equivalent to those for the local machine MAPPER Users group. Note: The drive letter X:\BISSITES represents your database installation directory. Subdirectory A reflects site A as the default site. Your drive, directory, and site letter could be different for your installation. X:\BISSITES Add MAPPER Users group read (and execute) access with inheritance to this folder and all subfolders. X:\ BISSITES\A\ioerrlog.txt Add MAPPER Users group and allow write access to this file. X:\ BISSITES\TMP Add MAPPER Users group and allow full access with inheritance to this file and any subfolders. 11

16 Load the Database on the First Node 1. Stop and then restart the MPR Controller service. 2. Start the Business Information Server Administration application. 3. Create the database files needed and load the database from your backup (current *.pur) file or the installation copy on the CD image at \Install\Server\Purge. If you installed Business Information Server 9.1 without the Internet Commerce Enabler, then use MAP9R1.pur. If you included the Internet Commerce Enabler feature, then use CI9R1.pur. Ignore the ICE9R1.pur file as it is used for upgrade processing. Close the Business Information Server Administration program when you are done. Confirm Access to the Business Information Server on the First Node 1. Start the Business Information Server Graphical Interface. Create a session using the domain user-id MAPPERGuest. Test that you can log into the Business Information Server 9.1 services. 2. Perform any database upgrade at this time. 3. Close the Business Information Server Graphical Interface when you are done. Confirm Access to the Business Information Server 9.1 Web Site on the First Node 1. Go to IIS and change the Anonymous user to the domain user-id IUSR_NETNAME. 2. Restart the Business Information Server 9.1 Web site using IIS. 3. Bring the IIS instance in the BISA cluster group online. 4. Start the Cool ICE Controller on the node. Confirm Access to the Business Information Server 9.1 Gatetool on the First Node 1. Test access to the CISYSTEM/Gatetool. 2. Test start the Gateway Configuration Tool. Synchronize IIS on All Nodes from the First Node Once the first node is working, you must synchronize the IIS configuration on all other nodes. For Windows 2000, use IISSYNC NodeName to configure the IIS on each additional node. For Windows 2003, use IIScnfg.vbs /copy /ts NodeName /tu user-id /tp password to configure the IIS on each additional node. Return to the database setup process specific to your sharing configuration. 12 Business Information Server for Microsoft Windows Cluster Failover

17 Monitoring Web Page Availability. Applications, not hardware, are a large reason for failures. One option is to monitor the availability of one or more Web pages. The Microsoft Resource kits provide tools to facilitate monitoring. A VB Script in combination with HTTPCMD.EXE can be used to do simple monitoring. The TryICE.vbs script repeats Web page access using HTTPCMD.EXE and checks the output stream until a limiting number of failures occur without success, which simply causes the script to terminate. As a cluster resource, a generic application has not failed if it continues to run; when it terminates that constitutes failure. The output of HTTPCMD.EXE is written to a file identified by the variable OutputFile and is named WebPgResult.txt in the current directory. A status code constructed from each Web reply is one of the following: Http response code (200 is normal) Blank if there is no http response Set status to the error code from a modified CIErrorHandler-HTML.asp. Example: Error B occurs when the Business Information Server 9.1 site is down. This status is a reasonable indicator of page availability. The TryICE.vbs script, listed in the appendix, samples the Business Information Server 9.1 home page and expects the normal 200-response code. Anything else, like timeout or a Business Information Server 9.1 error, is one failure. After enough successive failures occur, the generic application terminates. When this application is registered as a generic application cluster resource, it can trigger failover of the BISA cluster group. The generic application must be set with the advanced option for Restart as Yes and marked to affect the group. This triggers cluster failover when the cluster configured retry count occurs. If you take this resource offline, it does not automatically stop the BISA cluster group. The CScript is terminated and HTTPCMD.EXE terminates when it completes, however long that takes. See the appendix section, Details for Monitoring Web Page Availability for the details of this example of checking Web page availability. Other options can be created with some software development as seen in the Microsoft Windows 2000 Server Resource Kit or Microsoft Internet Information Server Resource Kit. 13

18 Installing Interim Corrections in a Clustered Server. Avoid Failover During Business Information Server 9.1 Installation Take the following resources offline (with Cluster Administration): Cool ICE Controller MPR Controller Business Information Server 9.1 IIS instance Install IC Install the IC on the Business Information Server 9.1 software on the node that owns the BISA cluster group. Restore Node Operation Bring the following resources online (with Cluster Administration): Cool ICE Controller MPR Controller Business Information Server 9.1 IIS instance Upgrade the Business Information Server 9.1 Database Follow the database process for Interim Correction on the Business Information Server 9.1 software on the node owning the BISA cluster group. This doesn t need to be done on the other nodes unless you are using the share none configuration. If you have multiple Business Information Server 9.1 sites, run the database upgrade procedure for each database, as described in the IC README.DOC file. Recheck Operability on Each Node To check operability on each node, test moving the BISA cluster group to ensure proper operation on all nodes. Uninstalling Business Information Server 9.1 from a Clustered Server. To uninstall on all nodes, you must start with a copy on one node. If you discover you can t uninstall from the second node, reinstall on the clean node (without the database), and then proceed with these directions. 1. On the node owning the ICE group, copy the installation directory ( X:\ Cool _ICE ); you will restore from this copy to uninstall each node. 2. Take the following resources offline (with Cluster Administration): Cool ICE Controller MPR Controller Business Information Server 9.1 IIS instance 3. Uninstall Business Information Server 9.1 on the node that owns the BISA cluster group. 4. Move the BISA cluster group to another node. 5. Restore the installation directory from the copy of the first step. 6. Uninstall Business Information Server 9.1 on the node. 7. Repeat steps 4-6 for each additional node. 14 Business Information Server for Microsoft Windows Cluster Failover

19 Sharing the Entire Installation. Layout. This choice places all of the pieces of a Business Information Server 9.1 installation on shared mass storage and switches the mass storage and Business Information Server 9.1 application between clustered server nodes. The figure below is a description of the Business Information Server 9.1 software and database layout on disk when sharing the entire Business Information Server 9.1 installation. Figure 2. Share Entire Installation Cluster Configuration Description. This sharing configuration allows the MS Cluster software to completely manage the Business Information Server 9.1 configuration data and all application moves between nodes of the cluster. It helps to prevent unintentional violations of the Business Information Server 9.1 licensing scheme that can occur when either of the other sharing methods is chosen. In fact, because only one server is active with Business Information Server 9.1 at any time, only one Business Information Server 9.1 license is required. Administration of the Business Information Server 9.1 system is simplified because updates only need to be made in one place, and the Cluster system transmits them everywhere else. Note: Unless applications other than Business Information Server 9.1 are used on the second cluster server node, that node of the cluster will be idle. 15

20 Unlike the other configurations, it is not possible to install a local site for each node of the cluster when sharing the entire Business Information Server 9.1 installation. The big benefit is the high availability of the application. References Installing Internet Commerce Enabler 3.0 Outside of the Default Web Site Internet Commerce Enabler 3.0 Cluster Failover for Microsoft Windows 2000/NT Installation. Complete the steps in Preinstallation Cluster Configuration. Confirm that IIS is working and failover works. The domain user-ids will be needed. Installing Business Information Server 9.1 Software per Node Follow the steps listed in Common Software Installation Procedures per Node. Set Up the Business Information Server 9.1 Database Follow the steps listed in Common Setup of the Database on the First Node. Set Up Cluster Controls for Share the Entire Installation In Cluster Administration, create two generic service resources: 1. Create a Generic Service type resource for BISA cluster group, MPR Controller, whose dependencies must include the disk resources and the IP address resource created in previous steps. The service name is MPR Controller and it has no start parameters. 2. Set the logon to the correct domain user-id for service logon. 3. Under the Advanced tab sheet, select Do not Restart. Change this later, after testing. 4. Specify the registry keys SOFTWARE\Unisys\MAPPER System\Services SOFTWARE\Unisys\MAPPER System\Sites on the Registry Replication page in order to have administrative changes to Business Information Server 9.1 software propagated correctly. 5. Bring the MPR Controller online. 6. Create a Generic Service type resource for BISA cluster group, Cool ICE Controller, whose dependencies must include the disk resources and the IP address resource created in previous steps. The service name is Cool ICE Controller (and it has no start parameters). 7. Under the Advanced tab sheet, select Do not Restart. Change this later, after testing. 8. Set the logon to the correct domain user-id for service logon. 9. Specify the registry keys SOFTWARE\Unisys\Cool ICE\Configs SOFTWARE\Unisys\Cool ICE\ConnectionPools SOFTWARE\Unisys\Cool ICE\Gateways on the Registry Replication page in order to have administrative changes to Business Information Server 9.1 software propagated correctly. 10.Bring the Cool ICE Controller online. 16 Business Information Server for Microsoft Windows Cluster Failover

21 Confirm Access to Each Node 1. Move the Business Information Server cluster group and log on to the next node. 2. Check under Component Services that the MPR Controller is using the correct domain user-id, the service logon. 3. Run the Internet Commerce Enabler Administration program. Connect to the site, check the status, and then close. 4. Run the Business Information Server Graphical Interface. Check that the logon works. 5. Use a browser to test that the home page is available. 6. Use a browser to test the Gatetool configuration. Move the BISA cluster group with Cluster Administration to each additional node. If you have additional nodes, go back to Confirm Access to Each Node, and repeat the procedure. If you have to correct the IIS configuration, use one node as primary, making corrections there, and use synchronize the IIS configuration to synchronize the other nodes. Confirm Cluster Administration Operation 1. When the Business Information Server 9.1 site shows an ICE Web page and the Gatetool displays in a browser, then return to the Cluster Administration and adjust the properties of resources for the MPR Controller and Cool ICE Controller to Restart instead of not restart. 2. Test the BISA cluster group to make sure that you can move the group to the alternate node and back. 3. Test that failover policies are working. Triggering Failover Based on Web Page Availability (Optional) For an explanation of triggering failover based on Web page availability, see Monitoring Web Page Availability under the shared Business Information Server 9.1 installation procedures, and Details of Monitoring Web Page Availability in the appendix. Administration. Moving the Site Use the Cluster Administration client to move the BISA cluster group resources from one cluster node to the other. No special steps are required. Failing the Site Failover is one of the main reasons for installing Business Information Server 9.1 in a clustered environment. Therefore, testing failover is very important. Data safety is also important, so this phase of testing should be performed very carefully. Only use a minimal number of databases during testing. 17

22 Site Administration The Internet Commerce Enabler Administration program cannot be installed on the same node independently from the server software. You can run it at the console of the node that owns the Business Information Server Group or preferably install it on a workstation and use it from there. Site administration is performed with the Internet Commerce Enabler Administration Client as with normal Business Information Server 9.1 installations. The exception in a clustered environment is the need to keep the two nodes of the cluster consistent with regard to the Business Information Server 9.1 configuration. When you share an entire Business Information Server 9.1 installation, the MS Clustering software keeps the local copies of the registry up to date when the application is configured. No special steps are required. Client Usage Clients attach to Business Information Server 9.1 software in a clustered environment by specifying the IP address registered with the shared application. Moving the site from one node to the other (either by failover or administrative action) will cause the connected users to experience a disconnection. However, as soon as the site is available on the other node, they will be able to connect again. This disconnection will also affect all background activities on the site. 18 Business Information Server for Microsoft Windows Cluster Failover

23 Sharing None of the Installation. This configuration choice places one complete copy of Business Information Server, the site configuration data, and the database on each node of the cluster. The only resource that is shared as far as the MS Clustering software is concerned is the IP address that is assigned to the active Business Information Server 9.1 Web site. Layout. The figure below is a description of the Business Information Server 9.1 software and database layout on disk when sharing nothing. Figure 3. Share Nothing Cluster Configuration Description. This sharing method allows you to utilize at least some of the resources of the inactive server node by having additional Business Information Server 9.1 sites installed that are not shared. Note: Administrative changes must be made on both nodes of the cluster to keep the shared site in sync on both nodes. The database must also be synchronized on both nodes. 19

24 Cluster Server Setup for Sharing None of the Installation. After you have installed Business Information Server 9.1 on both nodes of the cluster, follow the steps listed in Cluster Server Setup common to all configurations. You will be creating one IP address resource in this configuration. Now you can create the database files for your Business Information Server 9.1 sites, using the Internet Commerce Enabler Administration Client. Installation Complete the steps in Preinstallation Cluster Configuration. Confirm that IIS is working and failover works. The domain user-ids will be needed. Installing Business Information Server 9.1 Software per Node Follow the steps listed in Common Software Installation Procedures per Node. Set Up the Business Information Server 9.1 Database Follow the steps listed in Common Setup of the Database on the First Node. Lack of Cluster Controls for Share None The Share None of the Installation configuration has minimal cluster resources in the BISA cluster group. There is nothing to indicate that the software is operational. Failover can be performed on the cluster-controlled resources. The Business Information Server group on the failed node loses connection and must be stopped by a manual process. In the Share None of the Installation configuration, it is assumed that Cool ICE Controller and MPR Controller continue to support other sites. Similarly the accepting node must be ready to respond. A later section offers an optional method for triggering failover based on Web page availability. Confirm Access to Each Node Follow the steps listed in Common Set Up of the Database on the First Node. If you have to correct the IIS configuration, use one node as primary, making corrections there, and use synchronize the IIS configuration to synchronize the other nodes. Confirm Cluster Administration Operation Test the Business Information Server group to make sure that you can move the group to the alternate node and back. Note how the node you fail continues to operate. Test whether failover policies are working. Triggering Failover Based on Web Page Availability (Optional) For an explanation of triggering failover based on Web page availability, see Monitoring Web Page Availability under the shared Business Information Server 9.1 installation procedures, and Details of Monitoring Web Page Availability in the appendix. 20 Business Information Server for Microsoft Windows Cluster Failover

25 Administration. Business Information Server 9.1 Gateway Configuration This configuration must be manually maintained so that both nodes see the same virtual directories. All sites do not have to be operational on all nodes, just on the nodes that can run the site. Moving the Group Make sure that the Business Information Server 9.1 database on the backup cluster node is up to date, and then use the Cluster Administration client to move the Business Information Server 9.1 resources. Failing the Group Unless you use an optional trigger for failover, failover only occurs when the operating system fails. You determine any administrative action to monitor the Business Information Server 9.1 system. Site Administration Site administration is performed with the Internet Commerce Enabler Administration Client, as with normal Business Information Server 9.1 installations. The clustered group needs to keep the two nodes of the cluster consistent in regards to the Business Information Server 9.1 configuration. Note: The node that owns the Business Information Server group performs the administration of the Business Information Server group with the Business Information Server 9.1 Network name (or Business Information Server 9.1 IP address). When you share nothing, all updates must be made manually on both nodes of the cluster. Updates to configuration parameters can be transferred using the REGEDIT.EXE program to export and import the updated Registry section, or the updates can be performed on each node separately. Updates to database files must be performed manually on each node. In addition to the general administration issues, this configuration requires special handling so that the Business Information Server group database files are kept current on both nodes. This task will be easier if the volatile data in the database is well segregated from system data and nonvolatile user data. There are several ways that this could be handled. See the sections below for suggestions. Networked RUNs In this configuration, a network-based run checks for updates to data that must be kept current on both nodes of the cluster and passes the updated reports from one node to the other. The run executes on the active node of the cluster and pushes data to the inactive node. This run has to be activated during failover and site move operations. It is also possible to have selected parts of your application system participate in the data move operation by signaling that an important database update has occurred. 21

26 Partial Administrative Backups A procedure to run incremental database backups on a scheduled basis on the active node of the cluster allows the inactive node of the cluster to load these updates. Scheduling of the backup activity can be handled manually using the TPRG script. On the inactive server, a check would be made on the existence of a new Backup file and the data could be loaded. Daily Backups/Restores of Selected Cabinets This option is very similar to the previous option, with the exception that the inactive server is only updated overnight with data from the active server. Client Usage Clients attach to Business Information Server 9.1 in a clustered environment by specifying the IP address registered with the shared application. Moving the site from one node to the other (either by failover or administrative action) will cause the connected users to experience a disconnection. However, as soon as the site is available on the other node, they will be able to connect again. This disconnection will also affect all background activities on the site. In this configuration it is actually possible to connect to both the active and inactive hosts at the same time, using the IP addresses assigned directly to the cluster hosts. This is not recommended. Users should be instructed to connect to the IP address that is assigned to the cluster application group. 22 Business Information Server for Microsoft Windows Cluster Failover

27 Sharing Only the Database Files of the Installation. This choice calls for installing Business Information Server 9.1 on each of the cluster nodes separately. The only information that is placed on shared mass storage are the database files associated with shared Business Information Server 9.1 sites and some utility files. Layout. The figure below is a description of the Business Information Server 9.1 software and database layout on disk when sharing only the database files. Figure 4. Share Only the Database Cluster Configuration Description. This setup allows one or more Business Information Server 9.1 sites to be active on each node of the cluster. Doing this spreads out the possible user disruption due to administrative or maintenance changes on one node of the cluster. For example, if Site A is on node one and Site B is on node two, maintenance on node two only affects Site B users, and the disruption is limited to the time required to switch Site B from node two to node one. Note: Since only the database files are shared, moving a site from one node to the other requires a Z2 Business Information Server 9.1 start. When the database reaches 86,000 reports, the time required for this type of start is greater than 5 minutes and grows from there (see the following table). This issue can be avoided when a Business Information Server 9.1 site is moved gracefully by also moving the quick start file. 23

28 DB Size/Percent Used # Reports Time (min) DB Size/Percent Used 8 GB/9% GB/9% 8 GB/17% GB/17% 8 GB/26% GB/26% 8 GB/35% GB/35% 14 GB/35% GB/35% 14 GB/50% GB/50% 14 GB/90% GB/90% Table 1. Start Times Without Quick Start File Use of the Terminal Services Client for Administration can be problematic. Most Business Information Server 9.1 management functions work well when run in this environment. However, certain manual functions that must be executed do not work when run manually in this environment, and the errors you receive do not point you toward the environment as the cause for the error. Installation. Complete the steps in Preinstallation Cluster Configuration. Confirm that IIS is working and failover works. The domain user-ids will be needed. Installing Business Information Server 9.1 Software per Node Follow the steps listed in Common Software Installation Procedures per Node. Set Up the Business Information Server 9.1 Database Follow the steps listed in Common Setup of the Database on the First Node. Lack of Cluster Controls for Sharing Only the Database Sharing Only the Database configuration has minimal cluster resources in the BISA cluster group. There is a minimum indicator that the software is operational. Failover cannot be performed on the cluster-controlled resources. The BISA cluster group is downed or moved to a different node by the command scripts shown later. In Sharing Only the Database configuration it is assumed that Cool ICE Controller and MPR Controller continue to support other sites. Similarly, the accepting node must be brought up after the quick start recovery files have been moved to the new owning node before it is ready to respond. A later section offers an optional method for monitoring Web page availability, but you must modify it to run the down or move command script. You still cannot use Cluster Administrator to move the group. Taking a resource offline terminates the resource; it does not trigger any transitional tasks. Cluster Server Setup for Sharing Only the Database Files After you have installed Business Information Server 9.1 on both nodes of the cluster, follow the steps listed in Set Up a Business Information Server Application Group under Information Common to All Installation Configurations. Make sure that the resource groups for your Business Information Server 9.1 sites are active on node A of the cluster and then follow the steps below to complete your cluster set up. You need to follow these steps for each site you wish to share between the two cluster nodes. 24 Business Information Server for Microsoft Windows Cluster Failover

29 Note: The steps are based on the following information: D is the disk drive that Business Information Server 9.1 software was installed on. This disk exists on both servers and is local to the servers. Business Information Server 9.1 was installed in the default (BIS$1) directory. Z is the Business Information Server 9.1 site letter chosen for the shared site. S is the shared disk drive that contains site Z s database files. You have the Win2K resource kit installed so that the SLEEP.EXE program is available. Node A of the Cluster 1. Use the Internet Commerce Enabler Administration Client to create a new site (for example, Z). 2. Add database files to the site, making sure that you specify the shared disk resource you allocated to this site and that the site does not start automatically at boot time. 3. Initialize the database using the default database purge file on the Business Information Server 9.1 release CD. 4. Repeat steps 1-3 for any other sites in your environment. Remember that the Business Information Server 9.1 license is for a specific maximum number of users per server. If you expect to run all of your sites on the same node of the cluster at any time, the maximum number of users for each site must be set appropriately. 5. Create and register a system RUN named WAITFORDOWN. This script will be used to hold an Business Information Server 9.1 session open so that the Cluster server software will believe Business Information Server 9.1 is still up. The script should contain the following Create a script called Site-Z-UP.CMD, where the Z should be replaced with your site letter. This script should be located on the shared drive allocated to your Business Information Server 9.1 site. This script will be registered as the application resource for site Z in your cluster configuration. It should have the following contents: if %computername% == NODE1 goto node1 set foreignsitesdrive=\\node1\d$ set BISSITESdrive=D: goto configdone :node1 set foreignsitesdrive=\\node2\d$ set BISSITESdrive=D: :configdone D: cd \BIS$1\shared echo starting Site-Z-UP.CMD >out-z 2>&1 copy %foreignsitesdir%\bissites\z\qs_info %BISSITESdir%\BISSITES\z >>out-z 2>&1..\maputil.exe mapstart sz z2 >>out-z 2>&1 echo MAPSTART Z2 COMPLETE >>out-z 2>&1 echo error level is:%errorlevel% >>out-z 2>&1..\mapper.exe sz tqlmapcoord,2,,waitfordown >>out-z 2>&1 echo MAPPER TQL complete >>out-z 2>&1 25

30 echo error level is:%errorlevel% >>out-z 2>&1 sleep.exe 5 7. Use the Cluster Administrator program to create a generic application resource. Call it Site-Z-UP and add it to the site resource group created above. The command line for the application should be S:\Site-Z-UP.CMD and the current directory should be S. This assumes that you placed the script from step 6 at the root of the shared disk drive. 8. Use the REGEDIT tool to export the HKEY_LOCAL_MACHINE\SOFTWARE\Unisys\MAPPER System key. 9. Create a script called Site-Z-MOVE.CMD and place it in the \BIS$1\shared directory. This script is used to move a Business Information Server 9.1 site from one node of the cluster to the other. It should have the following contents: Cluster resource Site-Z-UP /offline /wait d:\bis$1\shared\moveout-z 2>&1 d: cd \BIS$1\shared..\maputil ii mapper z down >>moveout-z 2>&1 cluster group Site-Z /move /wait >>moveout-z 2>&1 cluster group Site-Z /status >>moveout-z 2>&1 cluster resource Site-Z-UP /online /wait >>moveout-z 2>&1 cluster resource Site-Z-UP /status >>moveout-z 2>&1 10.Repeat steps 5-9 for each additional site that is to be shared. Node B of the Cluster 1. Make sure that the MPR Controller service is stopped. 2. Use the REGEDIT tool to import the file created in step 8 above. 3. Use the Cluster Administrator tool to take each Site-Z-UP application resource offline. 4. Use the Cluster Administrator tool to move each Site-Z resource group to this node of the cluster. 5. Place a copy of the Site-Z-MOVE.CMD script created in step 9 above into the \BIS$1\shared directory on this node. 6. Use the Cluster Administrator tool to bring each Site-Z-UP application resource online. Confirm Access to Each Node Start the MPR Controller. You may want to recheck under Component Services that the MPR Controller is using the correct domain user-id, the service logon. Moving the Site Moving an active Business Information Server 9.1 site from one node to the other in this environment requires a multi-step process. Each step must be performed in the correct order for the process to work properly. Step 9 above describes a script, which will properly perform the site move operation. One copy of this script should be created for each Business Information Server 9.1 site and placed on each node of the cluster in the BIS$1\SHARED directory. To move a Business Information Server 9.1 site, execute the appropriate script. The script must be run from a session that has appropriate privileges (Administrative or SYSTEM) and is running in the correct context. Note: This script cannot be executed from a Terminal Services Remote Administration session. Using the Task Scheduler to start the script is a good alternative. 26 Business Information Server for Microsoft Windows Cluster Failover

31 If you must move the site manually, perform the following steps: 1. Use the Cluster Administration client to take the site resource offline. 2. Use the Internet Commerce Enabler Administration client to stop the site. 3. Use the Cluster Administration client to move the resource group. 4. Use the Cluster Administration client to bring the site resource online. Note: Executing steps 1 and 2 out of order will cause the resource to fail and restart on the current node. Accessing Each Node 1. Check under Component Services that the MPR Controller is using the correct domain user-id, the service logon. 2. Run the Internet Commerce Enabler Administration program. Connect to the site, check the status, and then close. 3. Run the Business Information Server Graphical Interface. Check that the logon works. 4. Use a browser to test that the home page is available. 5. Use a browser to test the Gatetool configuration. Move the BISA cluster group with Cluster Administration to each additional node. If you have additional nodes, go back to Confirm Access to Each Node and repeat the procedure. If you have to correct the IIS configuration, use one node as primary, making corrections there, and use synchronize the IIS configuration to synchronize the other nodes. Confirm Cluster Administration Operation Use the command script to make sure that you can move the Business Information Server group to the alternate node and back. Failover Based on Web Page Availability (Optional) For an explanation of failover based on Web page availability, see Monitoring Web Page Availability under the shared Business Information Server 9.1 installation procedures, and Details of Monitoring Web Page Availability. Note: You cannot trigger failover without modification to execute the move command script. 27

32 Administration. Most of the Business Information Server 9.1 and cluster administration functions can be performed from a Terminal Services for Remote Administration session. The only exception is to move a Business Information Server 9.1 site from one node to the other. Moving the Site See Moving the Site under Share Only the Database Files in the Installation section. Failing the Site Failover is one of the main reasons for installing Business Information Server 9.1 in a clustered environment. Therefore, testing failover is very important. However, data safety is also important, so this phase of testing should be performed very carefully. Use only a minimal number of databases during testing. It is important to remember that stopping a site that is shared in this configuration will cause the application to fail. Depending on the advanced configuration of the application, the site will be brought back up on the original node. Default configuration allows three failures within 15 minutes before failover will occur. Site Administration Site administration is performed with the Internet Commerce Enabler Administration Client as with normal Business Information Server 9.1 installations. The exception in a clustered environment is the need to keep the two nodes of the cluster consistent with regard to the Business Information Server 9.1 configuration. Administration in this configuration is a combination of the other configurations. If you install a local site on each node, you must manually update the database files for the local site to keep them identical on both nodes. Updates to shared database files only need to be made on the active node for the given site. Changes will be propagated when the sites are moved or failed. All configuration updates require that the registry be updated using the REGEDIT.EXE Export/Import procedure for the HKEY_LOCAL_MACHINE\SOFTWARE\Unisys\MAPPER System key. This includes adding, changing, and deleting database files, since they are tracked in the registry. Client Usage Clients attach to Business Information Server 9.1 in a clustered environment by specifying the IP address registered with the shared application. Moving the site from one node to the other (either by failover or administrative action) will cause the connected users to experience a disconnection. However, as soon as the site is available on the other node, you are able to connect again. This disconnection also affects all background activities on the site. If configured as described in this document with a local site on each cluster node in addition to the shared sites, clients may connect to the local site using the IP addresses for each cluster node. Connections to the shared sites are through the IP address assigned to the Cluster application group and are subject to the disconnection criteria described above. 28 Business Information Server for Microsoft Windows Cluster Failover

33 Example. The following is a more detailed example of how to set up the recommended installation, Share the Entire Installation, cluster configuration. Define the Cluster Group. Define your cluster as follows: Cluster ID = ICE Group Node 1 = MAPCL1 Node 2 = MAPCL2 Business Information Server 9.1 IP Address 1 = MAPCL3 Drive R is the shared physical disk that will contain the following two directories: R:\BIS$1 holds the program space R:\BISSITES holds the database Note: MAPCL1 will be the primary node for initial installation. Any IIS network configuration is performed there, and then use the iissync operation on the other node. Preinstallation. 1. For IIS, create domain user-ids: IWAM_MAPCL3 and IUSR_MAPCL3. 2. For Business Information Server 9.1 create domain user-ids, MAPPERService, and MAPPERGuest, all as members of the domain group, MAPPER Users. Passwords will be entered during the installation of Business Information Server 9.1 software. 3. Adjust the Local Security Policy for MAPPERService. Make the user-id MAPPERService a member of the Administrators group. 4. Set up the cluster resource group ICE Group with resources shared disk R, Network Name MAPCL3, IP address resource (in the form xxx.xxx.xxx.xxx) for MAPCL3. 5. On node MAPCL1, set up MSDTC with a manual start and service logon of domain\mapperservice. Use comclust a. Repeat for each node. 6. Reset MSDTC log with msdtc resetlog, and then test failover to each node. 7. On node MAPCL1, configure WAMUserName for IIS as domain\iwam_mapcl3. 8. Restart IIS. Repeat for each node. 9. Set up IIS (nondefault) Web site for ICE Group with the directory and default page. 10.Configure an anonymous user-id for the Web site as domain\iusr_mapcl3. Confirm that the Web site works with the default page. 11.Perform iissync MAPCL2. 12.In cluster administration, configure the IIS instance resource IIS ICE site and add to ICE Group. 13.Bring the IIS ICE site online to link up with IIS and then take it offline. Verify if the site is not available. 14.Bring the IIS ICE site online and then verify that the site is now available. 15.Move ICE Group to MAPCL2; all resources should move as well. Verify that the site is available. 16.Test failover policy. By default three failures cause the ICE Group to move to MAPCL1. Verify availability after movement back to MAPCL

34 Software Installation per Node. 1. Move the ICE Group to MAPCL1 as owner of Drive R. 2. Begin the SETUP.EXE program from the Business Information Server 9.1 CD image. When the welcome screen appears, perform the modification installation changes described in Installing Internet Commerce Enabler 3.0 Outside of the Default Web Site. 3. When the installation prompts for the file locations, change the drive letter to shared disk drive R, so R:\BIS$1 and R:\BISSITES hold the program and database. 4. When the installation prompts to select the site letter, use site A. Clear the Initial Database box. 5. Finish the changes described in Installing Internet Commerce Enabler 3.0 Outside of the Default Web Site to set up the virtual directories. 6. Perform the section Critical Windows Registry Adjustment and reboot the node. 7. Use the Services administration applet, stop the Cool ICE Controller and MPR Controller services, and set both as manual start services. 8. Move the ICE Group to MAPCL2. Repeat steps 1 to 7, answering all prompts the same. Set Up Database on First Node and Test. 1. Move the ICE Group to MAPCL1 as owner of Drive R:. 2. Stop the Cool ICE Controller and MPR Controller services. 3. Perform the steps in section Business Information Server Component Services Changes for User-Id and Group-Id Modifications. 4. Perform the steps in section File Access Modifications. 5. Start the MPR Controller. 6. Run the Internet Commerce Enabler Administration program. Add all of the needed files and load the initial database. 7. Run the Business Information Server Graphical Interface. Check that the logon works. Perform the database upgrade now if needed. 8. Start the Cool ICE Controller. 9. Use a browser to test that the home page is available; for example, 10.Use a browser to test the gateway configuration; for example, 11.Stop the Cool ICE Controller and MPR Controller services. Cluster Resources Setup. 1. Under ICE Group, create generic resource types for MPR Controller and Cool ICE Controller. 2. Enter the registry keys specific to each service. 3. Select the Advanced tab and set Do not restart until we confirm readiness to fail over. 4. Using Cluster Administration, bring the MPR Controller and Cool ICE Controller online. 30 Business Information Server for Microsoft Windows Cluster Failover

35 Check Next Node. 1. Move the ICE Group to the next node, MAPCL2. 2. Move to the MAPCL2 console and log on to the MAPCL2 server. 3. Run the Internet Commerce Enabler Administration program. Connect to the site, check the status, and then close. 4. Run the Business Information Server Graphical Interface. Check that the logon works. 5. Use a browser to test that the home page is available; for example, 6. Use a browser to test the Gatetool configuration; for example, Check Cluster Administration and Failover. 1. Check that the ICE Group can be moved between nodes and accessed successfully as MAPCL3. Verify availability after movement to MAPCL2 and again when moving it back to MAPCL1. 2. Under ICE Group, modify the resources for MPR Controller and Cool ICE Controller. Select the Advanced button and set Restart to affect the whole group. 3. Test failover policy. By default, three failures cause ICE Group to fail over. ICE Group Installation is now complete. Back up the system and proceed to any other production tests. 31

36 Appendix. Details of Monitoring Web Page Availability Cluster failover due to software hang conditions may be detected based on the repeated inability to satisfy a request from your Web site. The following VB Script uses a tool called HTTPCMD.EXE from either the Microsoft Windows 2000 Server Resource Kit or Microsoft Internet Information Server Resource Kit. Note: Another tool in the same kit called HTTPMON is useful and may be worth reviewing. It was designed for Network Load Balancing (NLB) and not for cluster failover. However, it is an interesting model of what can be done with additional tooling. Modify CIErrorHandler-HTML.asp Modify X:\BIS$1\Default Gateway\CIErrorHandler-HTML.asp at the start of the file to insert a response header that reflects Business Information Server 9.1 error conditions in the response header. <SCRIPT RUNAT=SERVER Language="VBScript"> Dim ErrMsg Dim ErrLink Dim LinkFlag Sub ErrorHandler(errNumber, errdescription) Response.AddHeader "Object-Error", Hex(errNumber) ' (added line) ErrLink = "<p><a HREF='default.asp?Category=DWizard&S... Using HTTPCMD.EXE To use HttpCmd, you need to create an HTTP request file for the page you want to test for accessibility. Create file ChkWebPg.req in R:\test\c HEAD /CICE/ HTTP/1.0 (blank line) (end of file) Note: CICE is the name of the virtual directory identified at Business Information Server 9.1 installation. Copy the HttpCmd.exe tool from the resource kit into the same directory as ChkWebPg.req and, assuming your Business Information Server group network name was MAPCL3, you can check the Web page using the command prompt with HTTPCMD MAPCL3 ChkWebPg.req 32 Business Information Server for Microsoft Windows Cluster Failover

37 Success HTTP/ OK Server: Microsoft-IIS/5.0 Date: Tue, 14 Jan :24:50 GMT Connection: Keep-Alive Content-Length: 3307 Content-Type: text/html Set-Cookie: CISESSIONID= c734b6ba87d56356e3a06e39ICE159; path=/ Set-Cookie: ASPSESSIONIDASTCDBTC=GGJHLKKBGKPMHNFLGDIPPEHN; path=/ Cache-control: private Failure with the IIS Instance Down connect() failed, error Failure with the MAPPER Site Down Note: The HTTP response is 200, but the actual response header reflects the Business Information Server 9.1 error returned. HTTP/ OK Server: Microsoft-IIS/5.0 Date: Tue, 14 Jan :23:42 GMT Object-Error: B Connection: Keep-Alive Content-Length: 1048 Content-Type: text/html Set-Cookie: ASPSESSIONIDASTCDBTC=FGJHLKKBKIIAKJMHFAKPLGCL; path=/ Cache-control: private Failure to Use the Correct Machine HTTP/ Object Not Found Server: Microsoft-IIS/5.0 Date: Tue, 14 Jan :27:59 GMT Content-Type: text/html Content-Length: 111 Monitoring An application using Visual Basic or C++ and Internet Transfer Protocol can be constructed for more sophisticated tooling, like HttpMon, in the resource kit. However, the documentation for HttpMon illustrates that it was constructed to assist in network load balancing and not for triggering cluster failover. A Microsoft VB Script in combination with HttpCmd can be used to do simple monitoring. This solution makes it easy to describe in this paper. This script repeats Web page access using HttpCmd and checks the output stream until the maximum number of failures occur without success. A generic application in a cluster resource has not failed if it continues to run. Termination constitutes failure. If you take this resource offline, then CScript will be terminated and the HttpCmd will terminate when it completes, however long that takes. The output of HttpCmd is written as a file identified by the variable OutputFile and is named WebPgResult.txt in the current directory. The Status code 33

38 constructed from each GetWebReply is the http response code (200 is normal), blank if there is no http response, or set to the value of the Object-Error B when the MAPPER site is down. For this example, 200 is success and anything else, like Object- Error value, is a failure. If the identified number of successive failures occur, then this generic application resource terminates. If the generic application resource Advanced options: Restart was yes and it was flagged to affect the group and resource failure count was satisfied, then cluster failover will occur. VB Script: TryICE.vbs ' ' Use as a generic application resource in the Cluster group ' to monitor the health of the ICE site ' ' Use wscript.exec to drive HttpCmd.exe to explore a Web site ' and check the output stops after a given number of failures. ' otherwise it runs forever or until aborted (that is, Ctrl-C) ' ' ' TryWeb.vbs WebServer HTTPRequestFile [-rretrycount] [-swaitseconds] ' ' Example: ' TryWeb.vbs MAPCL3 ChkWebPg.req -r3 -s30 ' Assumes CSCRIPT is set as default scripting engine ' Uses HttpCmd to go to MAPCL3 using http packet in ChkWebPg.req ' Retrying until 3 successive failures occur at 30 second intervals ' ' where ChkWebPg.req contains ' HEAD /CICE/ HTTP/1.0 ' ' (end of file) ' ' Force declaration of variables. Option Explicit Const ForReading = 1, ForWriting = 2, ForAppending = 8 DIM objfso, objtextfile Dim Retries, SleepSec Dim Successes, Failures Dim oargs, ArgNum Dim WWWServer, HTTPReqFile, OutputFile, StatusCode Retries = 1 ' default retry count if failure SleepSec = 3 ' seconds to sleep between retries Failures = 0 ' counts failures, reset to 0 if success 34 Business Information Server for Microsoft Windows Cluster Failover

39 WWWServer = "MAPCL3" HTTPReqFile = "ChkWebPg.req" OutputFile = "WebPgResult.txt" On Error Resume Next Set oargs = WScript.Arguments ArgNum = 0 if oargs.count >= 2 Then WWWServer = oargs(0) HTTPReqFile = oargs(1) End if ArgNum = 2 While ArgNum < oargs.count Select Case Left(LCase(oArgs(ArgNum)),2) Case "-r": Retries = 0 + Right(oArgs(ArgNum),Len(oArgs(ArgNum))-2) Case "-s": SleepSec = 0 + Right(oArgs(ArgNum),Len(oArgs(ArgNum))-2) End Select ArgNum = ArgNum + 1 Wend Set objfso = CreateObject("Scripting.FileSystemObject") Set objtextfile = objfso.opentextfile _ (OutputFile, ForWriting, True) objtextfile.close WriteOut("Web Server = " & WWWServer) WriteOut("HTTP RequestFile = " & HTTPReqFile) WriteOut("Sleep interval = " & SleepSec) WriteOut("Retry count = " & Retries) Successes = 0 Failures = 0 Do While TRUE ' WScript.Echo "loop starts" StatusCode = GetWebReply(WWWServer,HTTPReqFile) ' WScript.Echo "check Web reply" Select Case StatusCode ' only succeeds if expected status received Case "200": Failures = 0 Successes = Successes + 1 If Successes = 1 Then WriteOut("Success Web page access") WriteOut(" with StatusCode: " & StatusCode & " & Now) WriteOut(" Now waiting only for failures.") 35

40 End If ' ' Anything else is a failure. Show status code and time ' Examples are ' " B" IIS Site down ' "800423A6" ICE down Case Else: Failures = Failures + 1 Successes = 0 WriteOut("StatusCode: " & StatusCode & " & Now) WriteOut("Failure count = " & Failures) End Select If Failures >= Retries Then Exit Do End IF WScript.Sleep (SleepSec * 1000) Loop WriteOut("TryICE done") WScript.Quit Sub WriteOut(Output) WScript.Echo Output Set objtextfile = objfso.opentextfile _ (OutputFile, ForAppending, True) objtextfile.writeline(output) objtextfile.close End Sub Function GetWebReply(WebServer,ReqFile) Dim WshShell, oexec Dim ShellCmd, LineOut Dim Reply, ValueAt, LOLen, Checked Dim ErrorCode Reply = 0 ' WScript.Echo "GetWebReply()" ShellCmd = "httpcmd.exe " & WebServer & " " & ReqFile ' WScript.Echo ShellCmd Set WshShell = CreateObject("WScript.Shell") ' WScript.Echo "WshShell Created" Set oexec = WshShell.Exec(ShellCmd) ' WScript.Echo "ShellCmd executed. Now check result." Checked = 0 ' loop through all the output lines Do While Not oexec.stdout.atendofstream 36 Business Information Server for Microsoft Windows Cluster Failover

41 LineOut = oexec.stdout.readline LOLen = Len(LineOut) ' Warning! This produces extensive output. ' Enable next line to show the httpcmd result. ' WScript.Echo LineOut If (Checked = 0) AND (InStr(LineOut, "HTTP/") <> 0) Then Checked = 1 ValueAt = InStr(LineOut, " ") Reply = Left(Right(LineOut, LOLen - ValueAt),3) Else If (InStr(LineOut, "Object-Error: ") <> 0) Then ValueAt = InStr(LineOut, " ") ErrorCode = Right(LineOut, LOLen - ValueAt) ErrorCode = Left(ErrorCode,8) Reply = ErrorCode End If End If Loop ' WScript.Echo " End of output stream" GetWebReply = Reply End Function VB Script as a Cluster Resource Configure a new cluster resource in the Business Information Server group as a Generic Application to monitor the availability of a Web site. 1. Name: Web Page Check 2. Dependencies: Business Information Server Internet Commerce Enabler IIS Web site resource 3. Advanced: Select Do not restart until tested for your particular adjustments. This allows you to test failure conditions to match your expectations. 4. For parameters use the following: Command line: cscript TryIce.vbs HostMachine ChkWebPg.req -s5 -r5 (Example: cscript TryIce.vbs MAPCL3 ChkWebPg.req -s5 -r5) Current directory: R:\Datafiles\C 5. The options on the Parameters tab sheet are not needed. 6. Do not select Allow application to interact with the desktop or Use the Network name as the computer name. 7. You can test this script by impairing the target page. 8. Change the earlier file ChkWebPg to a different page to better fit your needs. 9. Once you are satisfied, modify the cluster resource to restart and affect the group. Then when a hang occurs, failover will move the application to the other node. 37

42 To learn more about Cluster Failover, contact Unisys today at ext. 621 or , ext. 621, or visit us on the Web at Specifications are subject to change without notice Unisys Corporation All rights reserved. Unisys is a registered trademark of Unisys Corporation. All other brands and products registered herein are acknowledged to be trademarks or registered trademarks of their respective holders. Printed in US America 9/04 * *