Configuring iFolder on a clustered volume
(Last modified: 21Jan2003)
This document (10066761) is provided subject to the disclaimer at the end of this document.
Novell NetWare 6.0
Novell iFolder 1.01
Configuring iFolder on a clustered volume
1. 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 will be made. For additional information on creating pools and NSS volumes refer to the product documentation for Novell Cluster Services (http://www.novell.com/documentation/lg/ncs6p/index.html).
2. Cluster enable the pool created in step 1. This will automatically cluster-enable the NSS volume created on the pool. This process also requires that an IP address be assigned to the clustered volume. Note the IP address as it will be needed later.
3. Once the cluster enabled volume has been created, create a folder on the clustered enabled volume. For example, if the cluster volume is called VOL1 create a folder on VOL1 called iFolder (VOL1:\iFolder).
4. Make sure iFolder is installed on each server within the cluster. Select one iFolder server and open the SYS:\APACHE\IFOLDER\SERVER\HTTPD_NW_ADDITIONS.CONF file with a text editor (like notepad).
5. There will be two areas within this file that must be modified. There is a section for a un-secured port (port 80, 51080, or 52080 by default) and then a second section for a secured port (port 443, 51443 or 52443 by default). First, in both the un-secured and secured sections change the VIRTUAL HOST setting to the IP address or DNS name assigned to the clustered volume. Next, in each area locate the LDAPHOST and change the DNS name or IP address to the IP address or DNS name assigned to the clustered volume. Finally, locate the IFOLDERSERVERROOT and change the directory path to the directory created in step 3 on the clustered volume (i.e. VOL1:\iFolder). Save the file then copy this conf file to each server in the cluster running iFolder.
6. On the same server open the SYS:\APACHE\IFOLDER\SERVER\HTTPD.CONF file with a text editor (like notepad).
7. Locate the listen statement (i.e. Listen 192.168.1.2:80) and change the IP address to the IP address of the clustered volume. Next, locate the SERVERNAME PARAMETER and change the DNS name to either the IP address of the clustered volume or the DNS name assigned to the clustered volume. Finally, at the end of the file locate the Secure Listen Statement (i.e. SecureListen 192.168.1.2:443 "SSL CertificateIP"). Again, change the IP address to match the IP address assigned to the clustered volume. Save the file then copy this conf file to each server in the cluster running iFolder.
8. Next, edit the AUTOEXEC.NCF file located in SYS:\SYSTEM and remark out the STARTIFOLDER line (i.e. # STARTIFOLDER).
9. From a workstation open ConsoleOne and browse to the cluster container object. Right-click the cluster volume resource and select Properties | IP Address. Verify that the IP address is the same as the address assigned to the cluster-enabled volume. Next, from the Properties dialogue box clic.k SCRIPTS | Cluster Resource Load Script. Add the following command to the end of the existing load script then select APPLY:
10. Next, click SCRIPTS | Cluster Resource Unload Script and add the following command to the beginning of the existing unload script then select APPLY:
This completes the necessary steps for enabling iFolder to work against a clustered volume.
For additional information on NetWare 6, please see the following solution. TID #10064501 - NetWare 6 Readme Addendum
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.
- Document ID:
- Solution ID: NOVL66054
- Creation Date: 12Dec2001
- Modified Date: 21Jan2003
Did this document solve your problem? Provide Feedback