Installing GroupWise WebAccess on SLES 10
This document (3248145) is provided subject to the disclaimer at the end of this document.
environment
Novell GroupWise 7
Novell SuSE Linux Enterprise Server 10 (SLES10)
Novell GroupWise WebAccess
Novell GroupWise Monitor
situation
Installing WebAccess Application on an existing Apache/Tomcat instance on SLES10.
Installing Monitor Application on an existing Apache/Tomcat instance on SLES10.
resolution
This solution assumes a new install of a SLES10 server and that the WebAccess Agent is running on a separate server. In the case of Monitor the agent will be running elsewhere also.
Make sure that the following RPM’s are installed:
apache2
tomcat5
Resolve any dependencies. Once the installation is complete go into YaST | Network Services | HTTP Server | Server Modules. Enable proxy
Then select Add Module. From the resulting list select proxy_ajp.
If you are not able to select proxy_ajp then you will need to manually enter it in the YaST Sysconfig Editor.
Select Finish.
Run the GroupWise install (by default this is /opt/novell/groupwise/software/install) and install the WebAccess Application (do not select the option to install with Apache and Tomcat). This simply installs the RPM.
Once the install is complete select Configure WebAccess Application.
When prompted for WebAccess agents gateway directory it is only actually needing the COMMGR.CFG file.
Copy this from the <domain>\wpgate\webac70a directory where GWINTER runs to a local directory on the SLES server and point the install at the directory it is in. The installation program then copies the file to /opt/novell/groupwise/webaccess.
When prompted for the paths to Apache and Tomcat make sure to change them from the defaults:
The installation program requires LDAP access to an eDirectory server so that it can create the application objects. If the server is in a DMZ it will be necessary to temporarily open the firewall for the installation. A common problem at this point is that the eDirectory LDAP server requires an SSL connection. It will be necessary to either supply the installation program with the LDAP servers SSL certificate, or disable the SSL/TLS requirement on the LDAP Group object in eDirectory.
Once the install is complete, LDAP access is no longer required.
SLES 10 no longer ships with the MOD_JK package like SLES 9 did. It is now necessary to use the MOD_PROXY modules instead, so some manual configuration is required at this point.
Edit /etc/apache2/conf.d/gw.conf
Remove the line:
“JkMount /gw/* ajp13”
Insert a line at the top:
ProxyPass /gw/ ajp://localhost:8009/gw/
For Monitor the line will be
ProxyPass /gwmon/ ajp://localhost:8009/gwmon/
Save the file.
Start Apache2 with
       /etc/init.d/apache2 start
Start Tomcat5 with:
      /etc/init.d/tomcat5 start
To ensure that these services start next time the SLES server restarts enter:
      chkconfig apache2 on
      chkconfig tomcat5 on
Access WebAccess using /gw/webacc instead of /servlet/webacc
additional notes
document
| Document ID: | 3248145 |
| Creation Date: | 2007-05-29 14:45:02.0 |
| Modified Date: | 2007-05-29 14:44:43.0 |
| Novell Product: | GroupWise |
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.