C.3 Configuring an iFolder Server Cluster on NetWare 5.1 and 6.0

In NetWare 5.1 and 6.0, the iFolder 2.1 server software resides and runs on the primary server. Each server node must have its own copy of the software.

To configure Novell iFolder on Novell Cluster Services:

  1. Install iFolder on all NetWare servers in the cluster that you want to run iFolder.

    See Section 4.0, Installing iFolder 2.1 on NetWare.

  2. Stop the iFolder service on one of your iFolder servers in the cluster.

    This will be your passive-standby iFolder server that iFolder will fail over to.

  3. Create an NSS volume to use as the central repository of iFolder user accounts and data.

    The size of this volume will vary, based on the number of iFolder users you plan to support and the storage quota allocated per user.

    Do one of the following:

    • NetWare 5.1 Support Pack 5: Create a Novell Storage Service (NSS) volume on your shared storage disk system, commonly referred to as a storage area network or SAN.

    • NetWare 6 or later: Create an NSS volume on a pool. If a pool already exists, make sure there is enough space on the pool for the NSS volume that you plan to make.

  4. Enable the NSS volume for clustering by assigning an IP address or DNS name to the cluster-enabled volume.

    Do one of the following:

    • NetWare 5.1 Support Pack 5: Enable clustering on the NSS volume that you created in Step 3.

    • NetWare 6.0 or later: Enable clustering on the pool you created in Step 3. (Enabling clustering on the pool automatically enables clustering on its NSS volume.)

    Remember the IP address of the user-database volume; you will need it in Step 6.

  5. Create a directory on the cluster-enabled volume where you want to store the iFolder user database.

  6. On one of the active iFolder servers in the cluster, edit the sys:\apache\ifolder\server\httpd_additions_nw.conf file to set parameters for the LDAP Host, iFolderServerRoot, and Virtual Host. The parameters must be modified in the listings for the unsecured port (usually Port 80) and for the secured port (usually Port 443).

    Modify the following parameters:

    • LDAP Host: Set this (for Port 80 and Port 443) to the DNS name or IP address (such as ldap1.your-domain-name.com or 192.168.1.1) that you assigned to the cluster-enabled volume in Step 4.

    • iFolderServerRoot: Set this (for Port 80 and Port 443) to the directory that you created on the cluster-enabled volume in Step 5.

      For example, if your cluster-enabled volume was called sharedvol and you had created a folder on that volume called nifdir, you would set the iFolderServerRoot to sharedvol:\nifdir.

    • Virtual Host: Set this (for Port 80 and Port 443) to the DNS name or IP address (such as lnif1.your-domain-name.com or 192.168.1.1) that you assigned to the cluster-enabled volume in Step 4.

    When you are finished, save your edits.

  7. Copy the edited httpd_additions_nw.conf file to the passive-standby iFolder server that you set up in Step 2.

  8. On a different active iFolder server in the cluster, edit the sys:\apache\ifolder\server\httpd.conf file to set parameters for the Listen, ServerName, and SecureListen.

    Modify the following parameters:

    • Listen: Set this parameter to the IP address or DNS name of the cluster-enabled volume by either adding a new Listen parameter or modifying an existing one.

    • ServerName: By default, this parameter displays the IP address of the server. Replace this IP address with the IP address or DNS name of the cluster-enabled volume.

    • SecureListen: Change the IP address in the SecureListen ipaddress SSL CertificateIP parameter to the IP address or DNS name of the cluster-enabled volume.

    When you are finished, save your edits.

  9. Copy the edited httpd.conf file to the passive-standby iFolder server that you set up in Step 2.

  10. Turn off the automatic start on reboot of iFolder on the member servers in the cluster by editing the autoexec.ncf file on the following iFolder servers in the cluster:

    • The iFolder server that you chose to be the passive standby server in Step 2.
    • The iFolder server where you modified the httpd_additions_nw.conf file in Step 7.
    • The iFolder server where you modified the httpd.conf file.

    To modify the autoexec.ncf file, comment out the startifolder line. Adding a pound sign (#) in front of the line makes it a comment line. For example,

    #startifolder

    The startifolder command allows iFolder to start by default when you reboot your server. However, when you use iFolder in a clustered environment, iFolder is started by Novell Cluster Services.

  11. Verify that the IP address for your cluster volume resource is correct.

    To view the IP address from your workstation, launch ConsoleOne®, browse to your cluster container object, right-click the cluster volume resource, then click Properties > IP address.

  12. Set up Novell Cluster Services to start iFolder by default on reboot of the cluster.

    1. In the Properties dialog box, click Scripts > Cluster Resource Load Script.

    2. Add the following command to the end of the existing load script:

      startifolder

    3. Click Apply.

  13. Set up Novell Cluster Services to stop iFolder services by default on the server down command.

    1. In the Properties dialog box, click Scripts > Cluster Resource Unload Script.

    2. Add the following commands to the beginning of the existing unload script:

      stopifolder

      delay 2

    3. Click Apply, then click Close.

Novell iFolder is now configured for Novell Cluster Services.