Installing ELM Server into a Cluster

Windows Server 2003

This section provides instructions for installing the ELM Server into a Cluster. The basic steps involved in clustering the ELM Server are:

1.Either create a new cluster resource group, or plan to use an existing cluster resource group. This is the ELM Server resource group.

2.Install the ELM Server on one node, with the binaries on the drive representing the Disk Resource in the ELM Server resource group.

3.Move the ELM Server resource group to the other node.

4.Install the ELM Server on the second node using the same install path as the first node.

5.Add the ELM Server service as a generic resource to the ELM Server resource group.

6.Bring the ELM Server resource online.

7.During Setup, the following services (and any services dependent on the following services) will be stopped and restarted:

•ELM Server service (if upgrading only)

•ELM Report Scheduling Service (if upgrading only)

•TNT Agent service (if upgrading only)

Using Cluster Administrator or the CLUSTER.EXE command line utility, create the ELM Server resource group and add a Disk Resource, an IP Address Resource and a Network Name Resource. Size the Disk Resource accordingly, depending on whether or not you are using an ELM Server database that will also reside on this Disk Resource. For details on how to do this, please refer to the Windows Help File/Help & Support Center, Microsoft TechNet and MSDN. If you plan to add the ELM Server resource to an existing resource group, you are not required to create a new group. Figure 1 illustrates an example of an ELM Server Resource Group before an ELM Server is added as a resource.

Figure 1 - ELM Server Resource Group Ready for ELM Server Installation

Install the ELM Server

1.Double-click the ELM70_nnn.exe file you downloaded to execute it (where nnn is the build number). The Setup Wizard will launch.

2.Click Next to continue. The License Agreement screen will appear.

3.Select I accept the license agreement and click Next to continue. The ReadMe Information screen will appear.

4.Read the contents of the ReadMe file and click Next to continue. The Select Components screen will appear.

5.Select the ELM Server product you wish to install and click Next to continue.

6.Select the destination folder. Using Figure 1 as an example, an ELM Enterprise Manager Server will be installed into the E:\Program Files\ELM Enterprise folder.

7.Enter the Company Name and Serial Number as it appears on your SLA. If this is an evaluation version, enter the Company Name and leave the Serial Number field set to EVALUATION. If this is an evaluation version, the expiration date will be displayed when you click Next. If this is a non-eval version, a confirmation dialog will appear when you click Next. Click Next to continue, and click OK to clear the dialog message that appears. The Service Account Logon screen will be displayed.

8.In the Username field, enter the account to use for the service account. This account must have administrative rights on the ELM Server and on all Windows-based Virtual Agents. Enter the password for this account in the Password field. Click Next to continue.

Note
If the account specified in the preceding step does not already have Log on as a Service rights on the ELM Server, the Setup process will grant this right to the account.

9.The Database settings readme dialog is displayed. Read the information contained here and click Next to continue.

10. Complete the Primary Database settings dialog to configure the ELM Server primary database. If the database does not exist you will have the option to create it. Click Next to continue.

11. Complete the Failover Database settings dialog to configure the ELM Server failover database. The failover database is used when the Primary database is offline. If the database does not exist you will have the option to create it. Click Next to continue.

12. Complete the Virtual Directory settings dialog to configure the IIS virtual directory and click Next to continue.

13. The Ready to Install the Application screen will appear.

14. Click Install to start the installation. Setup will copy the files to the destination folder, register its components, install the ELM Server service and configure the IIS virtual directory.

15. Click Finish to complete Setup.

16. Stop the ELM Server service and set it to Manual startup.

17. Using Cluster Administrator or CLUSTER.EXE, move the ELM Resource Group to the other node.

18. On this node, execute the Setup MSI file. The Setup Wizard will launch. Complete an Installation identical to the setup on NODE1.

19. Stop the ELM Server service and set it to Manual startup.

Add the ELM Server to the ELM Server resource group

1.Right-click on the ELM Server resource group and select Configure Application. The Cluster Application Wizard will launch.

2.Click Next to continue. The Select or Create a Virtual Server screen will appear. Choose Use an existing virtual server and select the ELM Resource Group from the dropdown list.

3.Click Next to continue. The Create Application Cluster Resource screen will appear. Select Yes, create a cluster resource for my application now.

4.Click Next to continue. On the Application Resource Type screen, select Generic Service from the dropdown.

5.Click Next to continue. The Application Resource Name and Description screen will appear. In the Name field, enter ELM Enterprise Manager Server. Enter an optional description.

6.Click the Advanced Properties button. Select the Dependencies tab, then click the Modify button. Add the Disk, IP and Network Name resources as dependencies. If the ELM Server's database is a SQL Server virtual server that also exists in the ELM Server resource group, then you should also make the ELM Server resource dependent on the database virtual server.

7.Click Next to continue. The Generic Service parameters screen will appear. In the Service Name field, enter EEMSVR   .  Check the box that says Use Network Name for computer name.

8.Click Next to continue. The Registry replication screen will appear. Click the Add button. In the Root Registry Key field, enter the HKLM Software hive: SOFTWARE\TNT Software\ELM Enterprise Manager.

9.Click Next to continue, then click Finish to complete creation of the ELM Server resource.

10. Bring the ELM Server resource online in Cluster Administrator.

This completes the installation of the ELM Server in a cluster. We recommend testing failover prior to attaching to the ELM Server with an ELM Console. You can use the Move Group function in Cluster Administrator to manually failover the group.

If you have any questions about this procedure, of if you would like assistance performing this procedure, please contact the TNT Software Product Support Group.

Windows Server 2008 and Windows Server 2008 R2

1.Install the ELM Server on two nodes. Use the same databases – both Primary and Failover – for each installation.

2.In the Failover Cluster Manager, select Services and Applications under the cluster you’re installing to. Select “Configure a Service or Application” from the list of Actions in the right pane.

3.In the High Availability Wizard, on the Select Service or Application panel, select Generic Service and select Next.

4.On the Select Service panel, select the ELM Enterprise Manager 7 Server and select Next.

5.On the Client Access Point panel, enter the name that the ELM Console will use to connect to the Server and select Next.

6.On the Select Storage panel, select an available storage location and select Next.

7.On the Replicate Registry Settings panel, use one of the following paths under HKEY_LOCAL_MACHINE:

a. X86: SOFTWARE\TNT Software

b. X64: SOFTWARE\Wow6432Node\TNT Software

8.On the Confirmation panel, select Next. At this point, the ELM Server service will be configured for high availability.

To access the Server using the ELM Console, use the hostname specified on the Client Access Point panel. Note that the ELM Server service should now be set to start manually, as it’s controlled directly by the Cluster services. If Windows Cluster Service detects that the ELM Server Service has failed, it’ll automatically start the Server on the secondary node. Reconnecting to the Server with the ELM Console will be required.