Configuring Novell NetWare 6 WebAccess for a clustered volume

(Last modified: 03Mar2004)

This document (10066481) is provided subject to the disclaimer at the end of this document.

goal

fact

Novell NetWare 6.0

Novell NetWare 6 WebAccess

cause

When installing NetWare WebAccess, several objects are created in NDS. These objects are created in the webaccess container. The WebAccess_pco object contains server specific information about the installing server. This information is contained in the WebAccess_pco object and in the portalservlet.properties file in the sys:/webapps/WebAccess/WEB-INF directory. The GUID attribute in the pco object needs to match the GUID contained in the portalservlet.properties file. Since you will need to install NetWare WebAccess on more then one server, the pco objects attributes will change during the second install making it necessary to modify the portalservlet.properties file on the first server to match the new GUID found in the pco object.

Novell NetWare 6 Webaccess runs against the Apache web server which is installed by default during the NetWare 6 installation. To configure WebAccess to run against a clustered volume you must re-define the IP address that the Apache web server is using.

fix

The correct GUID will be found in the portalservlet.properties file on the server where the most recent install of WebAccess was performed. The portalservlet.properties file is located in the sys:/webapps/WebAccess/WEB-INF directory. In order to load WebAccess on the servers where WebAccess was previously installed, you will need to copy the portalservlet.properties file from the last server where WebAccess was installed and paste it in the sys:/webapps/WebAccess/WEB-INF directory of the server where WebAccess was previously installed. This will update the GUID to match the new GUID found in the pco object from the latest install.

portalservlet.properties file:

System.DirectoryAddress=TSEDEV.provo.novell.com:636
System.PortalConfigurationObjectDN=cn=WebAccess_pco,ou=WebAccess,o=Report
System.GUID={B2E02D9F-0000-00FA-D368-51698941D716}
System.Password=nwwaPass

System.Logging=false
System.Logging.Priority=low
System.Logging.Output=err

System.DirectorySSL=true
System.SessionManager.Render=true
System.SessionManager.RenderOverride=true

If you're not sure which GUID is correct it will be necessary to use a 3rd party LDAP browser to check the WebAccess_pco object attributes and confirm which GUID is correct. Softerra LDAP browser can be downloaded at http://www.ldapadministrator.com/download/index.php. Once a connection to the server is made with the LDAP browser, browse to the ou=WebAccess then to the cn=WebAccess_pco object. Once the object is highlighted, find the bhObjectGUID attribute. That attribute will contain the correct GUID needed in all the portalServlet.properties files.

From a workstation, open the SYS:\APACHE\CONF\ADMINSERV.CONF FILE. Look for the following entry:

# Start Apache Services Port Configuration
Port 51080
Listen 192.168.1.1:51080
<IfModule mod_tls.c>
SecureListen 192.168.1.1:51443 "SSL CertificateDNS"
</IfModule>
# End Apache Services Port Configuration

The LISTEN and SECURE LISTEN IP addresses must be changed to reflect the IP address that is assigned to the clustered volume. For example, if you cluster is defined to use 192.168.2.1 then change the ADMINSERV.CONF file to read:

# Start Apache Services Port Configuration
Port 51080
Listen 192.168.2.1:51080
<IfModule mod_tls.c>
SecureListen 192.168.2.1:51443 "SSL CertificateDNS"
</IfModule>
# End Apache Services Port Configuration

Once the changes have been made stop the web manager by typing NVXADMDN at the server console, then re-load the administrator by typing NVXADMUP. At this point Novell NetWare 6 WebAccess will be listening on the cluster IP address. Repeat this step for each server in the cluster that will be running WebAccess.

For additional information on NetWare 6, please see the following solution. TID #10064501 - NetWare 6 Readme Addendum

document

Document Title:	Configuring Novell NetWare 6 WebAccess for a clustered volume
Document ID:	10066481
Solution ID:	NOVL65016
Creation Date:	30Nov2001
Modified Date:	03Mar2004
Novell Product Class:	Groupware NetWare

disclaimer

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.