Knowledge Base Home

Call Support


Search the Knowledge Base

Skip to end of metadata
Go to start of metadata

Environment

Netmail Archive 5.x and higher and GroupWise 2012 environments

Synopsis

This article applies to the following situations:

  • Installing the WebViewer after installing Netmail Archive
  • After upgrading to GroupWise 2012, the archive link/button disappeared from the WebViewer (see note below)
  • The automatic installation failed when trying to install the WebViewer
Note: Since GroupWise 2012 is supported by Netmail Archive but not M+Archive, environments still using M+Archive 2010 must be upgraded to Netmail Archive before the Archive button will function.

Solution

Before beginning the installation, the installation files for WebViewer should be available. They are located in the Netmail Archive installation package in the folder labelled WebViewer/program files/Messaging Architects/.

To copy the files between a Windows environment and the WebAccess server where the WebViewer will be installed, a Windows client such as WinSCP will be required. WinSCP is a free open source free SFTP, SCP, FTPS, and FTP client for Windows (current version at this time is available for download from  http://winscp.net/download/winscp555setup.exe).

To install the WebViewer, proceed as follows:

Note: The Paths used are based on a default installation of WebAccess and the paths shown below may differ if WebAccess was not installed in the default location.

1. Modify the webacc.cfg file

Modify the webacc.cfg file to add the correct section below after the end of file entry; the default location for webacc.cfg is /var/opt/novell/groupwise/webaccess/webacc.cfg.

If this is only a WebViewer update, it will be enough to verify that the section shown below is still in the webacc.cfg file (after some WebAccess updates, this section can end up missing some of the needed data):

###############################################################################
#TMA: Added for GWXML WebViewer Provider
###############################################################################
#------------------------------------------------------------------------------
#Specify the provider's class
#------------------------------------------------------------------------------
Provider.GWXMLV.class=com.novell.webaccess.providers.GWXMLV.GWANWP
#------------------------------------------------------------------------------
#Specify the provider's templates folder.
#------------------------------------------------------------------------------
Templates.GWXMLV.folder=GWXMLV
#------------------------------------------------------------------------------
#Specify the provider's configuration file.
#------------------------------------------------------------------------------
Provider.GWXMLV.Config.file=/var/opt/novell/groupwise/webaccess/gwxmlv.cfg
#------------------------------------------------------------------------------
#Specify super users. Separated by ';'
#------------------------------------------------------------------------------
Provider.GWXMLV.SuperUser.name=admin
#------------------------------------------------------------------------------
#setting for proxy, value: true or false
#------------------------------------------------------------------------------
Provider.GWXMLV.Proxy.disabled=false


2. Copy and modify the gwxmlv.cfg file

From the WebViewer installation files, modify the gwxmlv.cfg file and change the IP address section to point to the IP address of the server hosting the Remote Provider.

Next, check the port listed in this configuration file to make sure it points to the Remote Provider port. The default port is 6666.

After the file is updated, copy it to the WebAccess server, into the same folder that contains the webacc.cfg file (default is /var/opt/novell/groupwise/webaccess/).

 

3. Copy the WebViewer files to the WebAccess server

  • Create an empty GWXMLV folder under css, and copy all the files from the css folder to the GWXMLV folder.
  • Copy folder GWXMLV_CSS_gw2012 from the WebViewer installation folder to the WebAccess css folder. The locations will vary with the version of Tomcat:

    • With Tomcat5:      /srv/www/Tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css

    • With Tomcat6:     /srv/Tomcat6/webapps/gw/WEB-INF/classes/templates/webacc/css or /var/opt/novell/tomcat6/webapps/gw/WEB-INF/classes/templates/webacc/css

  • Rename the copied folder: remove the _CSS_gw2012 from the end so you end up with a file called GWXMLV.

  • Copy the files (*and read the note below before copying) from the CSS_gw2012 folder from the WebViewer installation to the WebAccess css folder; the location will vary with the version of Tomcat: 

    • With Tomcat5:      /srv/www/Tomcat5/base/webapps/gw/WEB-INF/classes/templates/webacc/css 

    • With Tomcat6:     /srv/Tomcat6/webapps/gw/WEB-INF/classes/templates/webacc/css or /var/opt/novell/tomcat6/webapps/gw/WEB-INF/classes/templates/webacc/css

*Note: Since this folder contains the caption.htt hypertext template file, it is a good idea to back up the original caption.htt file (or rename it to OLD) before copying these files over.  
  • Copy the sendjs.inc file from the WebAccess css folder to the GWXMLV folder. It will overwrite the existing sendjs.inc file copied from the WebViewer folder.

  • Copy the fldricon.inc file from the WebAccess css folder to the GWXMLV folder.

  • Upload the provider folder from the WebViewer installation source to WebAccess providers folder. The location will vary with the version of Tomcat:

    • With Tomcat5:      /srv/www/Tomcat5/base/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers

    • With Tomcat6:     /srv/Tomcat6/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers or /var/opt/novell/tomcat6/webapps/gw/WEB-INF/classes/com/novell/webaccess/providers

  • Rename the copied provider folder to GWXMLV

  • Copy the WebaccImages folders from the WebViewer installation source to the WebAccess images folder: note that the numbered folder will be different for every installation. The location will vary with the version of Tomcat:

    • With Tomcat5:      /srv/www/Tomcat5/base/webapps/gw/webaccess/200905140533/images

    • With Tomcat6:     /srv/Tomcat6/webapps/gw/webaccess/200905140533/images or /var/opt/novell/tomcat6/webapps/gw/webaccess/200905140533/images

  • Rename WebaccImages to GWXMLV

4. Restart Services

  • For the modifications to become active, Tomcat must be restarted:

    • For Tomcat5:    service tomcat5 restart

    • For Tomcat6:    service tomcat6 restart

  • Log in to GroupWise WebAccess. If the Archive button is not visible after logging in, it may be necessary to restart the server. If the button is still not visible after this, troubleshoot the communication between the server hosting the Remote Provider and the WebAccess server.
  • Start by checking the corresponding log files: refer to WebViewer - Log Files for the location of these files.

Once the plug-in is installed, SMTP relaying needs to be enabled on the GWIA so that messages can be forwarded to external domains. This is explained in the next section.

 

How to Allow Message Forwarding to External Domains from GroupWise WebAccess:

By default (and for security), GroupWise normally requires authentication to relay mail through the GWIA via SMTP. If this was not the case, the system could quickly become an Open Relay used by spammers for sending spam and lead to the server's IP address becoming blacklisted.  

To allow closed relaying, the properties of the GWIA can be modified to allow exceptions to the standard relay prevention rule. Such exceptions will allow specific systems to relay SMTP mail off of the GWIA without authentication (and preventing relaying by any host that is not on the exception list).

The attributes of the GWIA that allow closed relaying can be configured through ConsoleOne as follows:

  1. Log in to ConsoleOne and connect to the GroupWise domain where the GWIA resides.
  2. Locate the GWIA object and open the properties of the GWIA.
  3. Click the Access Control tab, and from the pull-down menu, select SMTP Relay Settings. Note that the SMTP Relay Default setting is Prevent Message Relaying. Do not modify this or the GWIA will act as an open relay
  4. The next step will create the exception list of IP addresses allowed to relay messages off of the GWIA.
  5. Click the Create button and enter the IP address of the server hosting the remote provider in the From field of the New Internet Address pop-up window, as shown in the screenshot below. 
  6. If the system has more than one remote provider, an IP address range may be entered if the addresses of the remote providers are contiguous. If they are not (usually the case), add as many exceptions to the list as needed. Do not use a wildcard in the FROM field or you risk creating an open relay.
  7. The To field may contain a asterisk (wildcard) to allow mail to be relayed anywhere.
  8. Click OK to populate the Allow list.



  9. When the configuration is complete, click the Apply button.
  10. The GWIA should restart automatically and write the new settings to the configuration. If the settings are not active within a few minutes, the GWIA may be restarted manually.

Notes

If the WebViewer does not load properly or you wish to revert back to the original WebAccess configuration, follow the steps below (the following applies to both tomcat5 and tomcat6):

  1. Rename the gw folder in the ...tomcat5/webapps/gw to ...tomcat5/webapps/gw.old
  2. Restart tomcat5 services
  3. A new gw directory will be created and WebAccess will load with the default configuration

 


Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?