Baan IVcx. Installation of the Baan software on Microsoft Cluster Server

Transcription

1 Baan IVcx Installation of the Baan software on Microsoft Cluster Server

2 A publication of: Baan Development B.V. P.O.Box AC Barneveld The Netherlands Printed in the Netherlands Baan Development B.V All rights reserved. The information in this document is subject to change without notice. No part of this document may be reproduced, stored or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Baan Development B.V. Baan Development B.V. assumes no liability for any damages incurred, directly or indirectly, from any errors, omissions or discrepancies between the software and the information contained in this document. Document Information Code: U7045A US Group: User Documentation Edition: A Date: April 1998

3 Table of contents 1 Introduction 1-1 Definitions 1-1 System requirements Installation instructions for BAAN IVc1 with Oracle Fail Safe on Microsoft Cluster Server Appendix A: Setup of a failover license daemon Appendix B: Setting up a job daemon in a clustered environment Appendix C: Optimal performance for Baan with Oracle FS on cluster 5-1 i

4 Table of contents ii

5 About this document This document contains 4 parts: n n n n Installation of Baan with Oracle Fail Safe on Microsoft Cluster Server Appendix A: Configuration of a licence daemon in the cluster Appendix B: Configuration of a job daemon in the cluster Appendix C: Optimimal performance on the cluster iii

6 About this document iv

7 1 Introduction Definitions In this document, the following names are used to identify the cluster, the Baan environment and the Oracle database. Of course, the user is free to use other names. srv_nld_wolf1 srv_nld_wolf2 srv_nld_wolf3 srv_nld_wolf4 srv_nld_wolf5 BAAN BAAN IVc Network name for the first node in the cluster Network name for the second node in the cluster Cluster alias network name Virtual network name for the database Virtual network name for the Baan software environment Oracle database instance name for the Baan Data Service name for the Fail Safe Baan database System requirements The cluster should fulfill the following requirements: n n n n n > 2 GB local disk space per cluster node. Windows NT 4.0/EE as well as Oracle will be installed on the local disk. Three or more shared disks. One disk will be used as quorum resource (should be as small as possible), one disk for the Baan environment (approximately 4 GB) and one or more disks for the database. Two cluster machines with enough memory and CPU power to serve the database server and/or Baan environment (in case that one node of the cluster is down, the other node should be able to serve both the database and the Baan environment with acceptable performance). Five IP addresses must be reserved for the cluster: Two IP addresses for the cluster nodes, one for the virtual machine name of the cluster, one for the virtual machine name of the Baan environment, and one for the database server. These IP addresses should be resolvable in the DNS. An external Windows NT primary domain controller must be configured. The Windows NT user baan must be known in the domain. 1-1

8 Introduction 1-2

9 2 Installation instructions for BAAN IVcx with Oracle Fail Safe on Microsoft Cluster Server 1 Install Windows NT 4.0/Enterprise Edition on node srv_nld_wolf1. Install Windows NT on the local disk. Do not install the PDC/BDC component. Add the node to a Windows NT domain. Install Service Pack 3 (automatically prompted after first logon to the node). Configure the shared disks by using Windows NT s Disk Administrator. At least one disk for the Baan environment, one disk for the database, and one disk as quorum resource. Shut down the system after installation completion. 2 Install Windows NT 4.0/Enterprise Edition on node srv_nld_wolf2 (same procedure as for step 1). 3 Start node srv_nld_wolf1, install Cluster Server. After logging on, the following screen is displayed: 2-1

10 Click Continue. The following screen will be displayed: Enable the checkbox next to Microsoft Cluster Server to install Microsoft Cluster Server. The installation of Microsoft Cluster Server will be started. In the following screen, choose to Form a new cluster. 2-2

11 Click Next and then specify the virtual name of the cluster: The next step is to specify a Windows NT domain account that will be used to manage the cluster. In this case, user baan is used. After clicking Next, specifying the IP address of the cluster, and configuring the network cards, this node is enabled for Microsoft Cluster Server. 2-3

12 4 Create cluster groups. Start Cluster Administrator, connect to the cluster s virtual machine name. Create a cluster group quorum, which contains the cluster s quorum disk. Create a group called baan, which contains the shared disk for the Baan environment. Leave all other groups intact. After completion, you can distinguish the following five cluster groups: n Cluster group, which contains the cluster s network name and IP address. n Quorum, which contains the quorum disk. n Baan, which contains a shared disk. n Two disk groups that will be used for the Oracle database. 2-4

13 5 Start node srv_nld_wolf2, install Cluster Server Server (automatically prompted after you log on to Windows NT). Select Join an existing cluster. Specify the cluster s virtual machine name: After clicking Next, and specifying the Windows NT domain account s password, this node is also part of the cluster. 2-5

14 6 Install Oracle on node srv_nld_wolf1 Install Oracle or higher on a local disk, as described in the Baan Installation on Oracle 7.3 manual. Install Oracle Fail Safe or higher in the same location as Oracle (or higher). Instructions on how to install Oracle Fail Safe can be found in the Oracle Fail Safe installation manual. 7 Install Oracle on node srv_nld_wolf2. Use the same installation procedure as for node srv_nld_wolf1. 8 Start Cluster Administrator, move cluster group baan to the first node in the cluster. 9 Add Windows NT domain user baan to the local Windows NT group Administrators on both nodes. 10 On srv_nld_wolf1, perform a fat client (User Interface + Logic) installation on the shared disk in the baan cluster group (for example, if disk G: is available in cluster group baan, perform an installation in g:\baan). Follow the usual steps to install a fat client, as described in the Baan Installation Manual. A few hints are given below to set up the Baan environment correctly on a cluster. 2-6

15 In the Choose Directory dialog box, specify a directory on the shared disk. 2-7

16 In the Setup Type dialog box, select User Interface and Logic. Click Next. 2-8

17 As database server, choose the current node s name. 11 After completing the installation, start REGEDIT on the first node and remove the registry value HKEY_USERS\.DEFAULT\Environment\BSE_REM. 2-9

18 12 Failover the cluster group baan and the cluster group(s) that contains the disk(s) for the database to node srv_nld_wolf2 using the Cluster Administrator In our example, Disk Group 2 (E:) and 3 (F:) will be used for the Oracle database. 13 Perform a full BAAN IV BackOffice installation (User Interface, Logic, application and database) on node srv_nld_wolf2. Carry out the installation in exactly the same location as was used for the fat client (in our case, g:\baan). For a detailed description of the Baan installation, see the Baan installation manual. To get a correct installation on a cluster, a few tips are given below. 2-10

19 In the Choose Directory dialog box, specify the same path as during the fat client installation (the directories created by the fat client installation must be visible). 2-11

20 As setup type, select Full installation. 2-12

21 In the Select Database to use dialog box, select Oracle

22 Create a new Oracle database instance, called BAAN. 2-14

23 Create the various tablespaces on the shared cluster disks (in our example disks E: and F:). Make sure the specified paths exist. If they do not exist, create them manually) As with the rollback, temporary, system, and redo datafiles, also create the index and tablespace on the shared disk(s). 2-15

24 2-16

25 After filling in all the dialog boxes, press Next in the Installation Overview dialog box to install Baan on the second node. This will approximately take two to three hours.. 14 After completing the Baan installation, start the Cluster Administrator. Add resource type IP address to the baan cluster group. 2-17

26 Add resource type Network Name to the baan group. 15 Bring the Baan resource group online. 16 On node srv_nld_wolf2, copy the initbaan.ora file from ORACLE_HOME\database to a shared disk which holds the Oracle database instance for Baan. In our example, we copy the c:\orant\database\initbaan.ora file to e:\orant\initbaan.ora. 2-18

27 17 Make the created Oracle instance Fail Safe. Go to Oracle Fail Safe Manager Go to Groups menu item, select Create. Create a fail safe group called baandb with a virtual network name for the database After creation of the fail safe group, add the new database instance BAAN to the fail safe group. In the previous dialog box, we added the database instance BAAN to the failsafe group baandb. The service ID has been supplied manually. The instance name and the database name refer to the newly created instance. The parameter file must be located on the shared disk. Memorize the service ID. You need this ID later on to connect to the database. 2-19

28 18 Refresh the Oracle TNS service information on both cluster nodes as follows: Start the Oracle Enterprise Manager Select Navigator, Service Discovery, discover new services Add the cluster nodes and the database s virtual network name to the list of nodes to discover. Click Next a couple of times and finally click Finish to discover/refresh all Oracle services. Without this, problems can arise when trying to connect to the Baan database service ID (BAAN IVc). 19 On node srv_nld_wolf2, open the file %BSE%\lib\tabledef6.1 using WordPad (in our example, the Baan BSE directory is g:\baan, thus file g:\baan\lib\tabledef6.1 should be opened). Replace ORACLE_SID=xxxx with LOCAL=BAAN IVc, where xxxx is the Oracle instance name and BAANIVc is the Baan database service ID. 20 Failover the Baandb and baan cluster groups to node srv_nld_wolf1 21 Run the following command to install Baan s support for MSCS on node srv_nld_wolf1: bmscsset install. 22 Follow the instructions given by the bmscsset command. 23 Start the Cluster Administrator. 24 In the baan cluster group, add the Baan Environment resource type. This resource must depend on the shared disk on which Baan has been installed (g: in our example). First, in the Resource Type field, select Baan Environment for the baan cluster group. 2-20

29 2-21

30 In the Dependencies dialog box, add the shared disk on which Baan is installed as a dependency. 2-22

31 NOTE In the Baan Environment Parameters dialog box, specify the parameters as specified in the next screen. A bug in Microsoft Cluster Server prevents the Baan Environment Parameters dialog box from being displayed. If this dialog box does not appear, delete the created resource and try to create the resource on the other node. If this also fails, reboot both nodes and try again. In most cases, the parameters should be left unchanged (the Environment field should be empty and Start Jobdaemon dialog box should be unchecked). The parameter environment is reserved for future use. For details about using a job daemon in a clustered environment, see Appendix B. 25 For instructions on how to enable the license daemon on a cluster, see Appendix A. 26 Reboot both cluster nodes. 27 After starting, verify that all cluster groups are up and running. 2-23

32 In the previous window, all cluster groups have the Online status. The database is served on node srv_nld_wolf1 and the Baan environment is served on node srv_nld_wolf2. 28 Try to set up a connection with the installed Baan environment using BW. Use the virtual machine name of the Baan Environment (srv_nld_wolf5) to establish the connection. All operations should work perfectly, irrespective of the machine where the database is being served and where the baan environment is being served! The following dialog box shows a possible configuration of BW. 2-24

33 After clicking RUN!, the BW welcome dialog box is displayed and the following window will appear: You have successfully installed Baan on Microsoft Cluster Server! 2-25

34 2-26

35 3 Appendix A: Setup of a failover license daemon To enable a Baan License Daemon in a Microsoft Cluster Server environment, perform the following steps. 1 Use Notepad to open the BSE\lib\licence6.1 file. 2 Replace the license string with the following one: <node1>, <node2> In accordance to the previous example, this would be: srv_nld_wolf1, srv_nld_wolf2 3 On the first node, start the Baan Service Manager. 4 Install the BaanLicencing component. LICD.EXE is located in the Baan subdirectory of the Windows installation directory. 3-1

36 Appendix A: Setup of a failover license daemon 5 Start Control Panel, double-click Services. Change the startup mode of the BaanLicencing service from Automatic to Manual. 6 Perform steps 4, 5, and 6 also for the second node. 7 Brand both cluster nodes. Use the standard procedure to license the Baan software. You must obtain a network license key from Baan: one for the first node and another one for the second node in the cluster. Note: the High Availablity option does not have to be specified on the License Request Form. This option will be enabled automatically by the software itself. 8 Add the license daemon to a cluster group. The easiest way is to add the licence daemon to the baan group. In general, every cluster group with a virtual machine name can be used. Start the Cluster Administrator, right-click the mouse, choose New, choose Resource. The following dialog box is displayed: In this case, a Baan Licensing resource type will be created in the cluster baan group. The name of the resource is Baan License daemon. 3-2

37 Appendix A: Setup of a failover license daemon 9 Use Notepad to open the BSE\lib\licence6.1 file. 10 Replace the license string with the following one: <virtual machine name> In accordance to the previous example, this would be: srv_nld_wolf5 11 Bring the resource online. 3-3

38 Appendix A: Setup of a failover license daemon 3-4

39 4 Appendix B: Setting up a job daemon in a clustered environment The next steps describe the process to set up a Job daemon in a Baan IV BackOffice on Microsoft Cluster Server environment. 1 On the first node, start the Cluster Administrator. 2 Failover the baan group to the first node (all users of the Baan environment will be disconnected!). 3 Install the BaanJobDaemon service by using the Baan Service Manager on the first node. 4 Go to Control Panel, Services. 5 Change the startup mode of the BaanJobDaemon from Automatic to Manual. 6 Failover baan group to the secon node by using the Cluster Administrator. 7 Perform steps 3, 4 and 5 for the second node. 4-1

40 Appendix B: Setting up a job daemon in a clustered environment 8 In the Baan installation directory (in our example, g:\baan), open the lib\user\jobd.bwc file by using the BW configuration tool. Adjust the following parameters: Hostname: <virtual machine name of the cluster Username: <domain>\baan Password: <password from user baan> BSE: <path to baan environment on the shared disk> An example of this is given in the following dialog box: Save the configuration file. 9 In Cluster Administrator, go to the baan group, select the Baan Environment resource, right-click the mouse and choose Properties. Click the Parameters tab 10 Select the Start jobdaemon check box. Then click OK. 4-2

41 Appendix B: Setting up a job daemon in a clustered environment 11 To enable the new setting, bring the Baan Environment resource offline and back online. 4-3

42 Appendix B: Setting up a job daemon in a clustered environment 4-4

43 5 Appendix C: Optimal performance for Baan with Oracle FS on cluster To get the most performance from the cluster, it is best to divide the workload over the two nodes: one node serving the database and the other one serving the Baan Environment. In the previous example, the Baan environment (group Baan) is served on srv_nld_wolf2 and the database (group Baandb) is served on srv_nld_wolf1. To establish this situation, the group properties in the cluster must be adjusted: n Right-click on the Baan group in Cluster Administrator and choose Properties. n n Select srv_nld_wolf2 as being the preferred owner of the group Right-click on the Baandb group in the Cluster Administrator and choose Properties. n Select srv_nld_wolf1 as being the preferred owner of the group Now you have accomplished a balanced Baan on MSCS solution. 5-1

44 Appendix C: Optimal performance for Baan with Oracle FS on cluster 5-2