The information in this Readme file pertains to Novell® GroupWise® 6.5 for Linux Support Pack 2. This Support Pack contains updates for all components contained in the GroupWise 6.5 for Linux product. However, this Support Pack does not contain updates for GroupWise Messenger. GroupWise Messenger 1.0 for Linux Support Pack 2 is a separate download.
The primary purpose of GroupWise 6.5 for Linux Support Pack 2 is to add support for the following 10 languages in the GroupWise Cross-Platform client:
- Arabic
- Chinese-Simplified
- Chinese-Traditional
- Czech
- Hebrew
- Hungarian
- Japanese
- Korean
- Polish
- Russian
Some additional improvements have also been made.
For information on the latest Support Pack issues, see the Consolidated Support Pack Readme Addendum, where issues for GroupWise 6.5 for Linux Support Pack 2 are available along with issues for GroupWise 6.5 Support Pack 2.
GroupWise 6.5 for Linux Support Pack 2 must be applied to the following GroupWise version in your software distribution directory:
The GroupWise 6.5 for Linux software distribution directory must already exist in order to install Support Pack 2. When you update the software distribution directory, all GroupWise components should be updated to keep them at the same version level.
Do not apply GroupWise 6.5 for Linux Support Pack 2 to any non-Linux software distribution directory such as GroupWise 6.5 or GroupWise 6.5 Support Pack 1.
GroupWise 6.5 for Linux Support Pack 2 is available as compressed tar files. You can download the full Support Pack as a single download. You can also download the GroupWise Cross-Platform clients for Linux* and Macintosh* as separate downloads.
The full Support Pack includes both administrative and client files.
Download the compressed tar file (gwlinux652.tar.gz) to a temporary directory on your Linux server.
In a terminal window at your Linux server, change to the temporary directory, then use the following commands to uncompress and untar the downloaded file:
gzip -d gwlinux652.tar.gz
tar -xvf gwlinux652.tar
The result is a directory named gwlinux652.
Change to the gwlinux652 directory.
Enter the following command:
xhost + localhost
In the same window, become root by entering su and the root password.
Start the GroupWise Installation Advisor:
./install
Click Create or Update a GroupWise System.
Follow the on-screen instructions to update the software distribution directory and the administration, agent, and client software that is in production.
For more information, see the GroupWise 6.5 Installation Guide located in the /docs/us subdirectory of the Support Pack.
Download the compressed tar file (gw652clnx.tar.gz) to a temporary directory on your Linux workstation.
In a terminal window at your Linux workstation, change to the temporary directory, then use the following commands to uncompress and untar the downloaded file:
gzip -d gw652clnx.tar.gz
tar -xvf gw652clnx.tar
The result is a directory named gw652clnx.
Change to the gw652clnx directory.
Start the GroupWise Setup Advisor:
./install
To start the Cross-Platform client after installation, click the GroupWise icon on your Linux desktop.
Download the StuffIt file (gw652cmac.sit) to a temporary directory on your Macintosh workstation.
At your Macintosh workstation, browse to the gw652cmac.sit file.
Double-click the gw652cmac.sit file to uncompress the downloaded file.
The result is a directory named gw652cmac.
Change to the gw652cmac directory.
Double-click the GroupWise.app.sit file to install the GroupWise Cross-Platform client software.
To start the Cross-Platform client after installation, click the GroupWise icon on your Macintosh desktop.
After you have installed the GroupWise 6.5 for Linux Support Pack 2 versions of the POA and the MTA, any existing Internet Agent, WebAccess Agent, or Monitor Agent installed on the same server no longer runs. You must update all agents on the same server to GroupWise 6.5 for Linux Support Pack 2 in order for the agents to run correctly.
The WebAccess Application, WebPublisher Application, and Monitor Application share a common library. If you plan to run these applications on the same Web server, you must update all three before any of them can work properly.
The GroupWise® WebAccess and Monitor software included in GroupWise 6.5 for Linux Support Pack 2 supports the following wireless devices:
We are continually evaluating and adding support. As we add support for additional devices, we post the updates at the Novell GroupWise Wireless Web site. We encourage you to check this site frequently for updates and news.
Installation issues for individual GroupWise components are located under the heading for each component.
Because of long-standing file lock issues with NFS, you cannot use an NFS mount to mount a server file system where your GroupWise system is located to a workstation where you are running ConsoleOne®. We recommend using an SMB mount instead.
All directory names in paths to GroupWise domains and post offices should consist of lowercase letters. Filenames should also consist of lowercase letters.
When filling in a UNC Path field in ConsoleOne, you must specify the server name. You cannot use an IP address or DNS host name. On Linux*, ConsoleOne translates UNC paths into Linux paths.
If you run ConsoleOne on SUSE® LINUX 9 with Ximian® Desktop 2 installed, the label text on the property tabs does not display. As a workaround, click the tab to select it, then use the up-arrow and down-arrow keys to display each property page until you reach the one you want.
GroupWise 6.5 for Linux does not include the following administration features that are available in GroupWise 6.5:
On Red Hat* Enterprise Linux 3 and Red Hat Advanced Server 3, starting the POA or MTA might result in a "floating point exception" error. If this occurs, you must enter the following prior to starting the POA or MTA:
export LD_ASSUME_KERNEL=2.4.0
If you start the POA or MTA using the grpwise startup script in /etc/init.d, this error does not occur because the script sets the LD_ASSUME_KERNEL environment variable for you.
If you try to start the POA or MTA on a server where The X Window System* and OpenMotif are not running, you receive the following error:
libXm.so.3: cannot open shared object file
: no such file or directory
To resolve the error, start The X Window System and OpenMotif before starting the POA or MTA with the --show switch. If you start the POA or MTA without the --show switch, you can use the agent's Web console to monitor the agent from your Web browser.
On Red Hat 8, you cannot use the main GroupWise Installation Advisor (the install executable at the root of the Support Pack) to install the Cross-Platform client. Instead, you can run the install executable located in /client/linux or you can install the novell-groupwise-gwclient-6.5.2 RPM located in the same directory.
For best performance, run the Cross-Platform client in Caching mode. It is noticeably faster than Online mode.
If you run the Cross-Platform client in Caching mode as root on Linux, you might encounter synchronization problems with your master mailbox when you next run as a regular user. If pending requests from the root session remain when you log in as a regular user, regular user requests get backed up behind the root requests, which cannot be processed while you are logged in as a regular user. To resolve any problems, run the client as root again so that all messages get synchronized, then run as a regular user thereafter to prevent further problems.
Some HTML-formatted messages are not rendered correctly in the Cross-Platform client.
In Online mode, custom column sort settings are not saved unless the Cross-Platform client is connected to a GroupWise 6.5 for Linux POA or later. The problem will be resolved for NetWare® and Windows* POAs in a future Support Pack.
This is a Java* error. A newer version of the JVM* resolves it. The print jobs prints successfully in spite of the error message.
The Cross-Platform client does not recognize the mailbox size limits set in ConsoleOne (Tools > GroupWise Utilities > Client Options > Send > Disk Space Management).
If you have installed Microsoft* Office or Internet Explorer on your Macintosh, new messages might not display as bold in your mailbox. To resolve the problem, disable your user fonts, which are typically duplicates of your system fonts, or update to JVM 1.4.2 Update 1 or later.
The GroupWise Cross-Platform client does not currently provide some functionality that is available in the GroupWise Windows client, including:
Additional functionality will be available in future releases of the Cross-Platform client.
During installation, the Internet Agent Installation program requires access to Novell® eDirectoryTM by way of LDAP authentication. The LDAP Group object includes an option named Require TLS for Simple Binds with Password, which is enabled by default. With this option enabled, you must provide the LDAP server's Trusted Root Certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of the Internet Agent.
Unless you already have SSL set up, an easier alternative is to disable Require TLS for Simple Binds with Passwords in ConsoleOne, which allows LDAP authentication to take place using clear text (typically on port 389), during installation of the Internet Agent. After disabling the option, restart eDirectory, install the Internet Agent, then re-enable Require TLS for Simple Binds with Password and restart eDirectory again.
On Red Hat Enterprise Linux 3 and Red Hat Advanced Server 3, starting the Internet Agent might result in a "floating point exception" error. If this occurs, you must enter the following prior to starting the Internet Agent:
export LD_ASSUME_KERNEL=2.4.0
If you start the Internet Agent using the grpwise-ia startup script in /etc/init.d, this error does not occur because the script sets the LD_ASSUME_KERNEL environment variable for you.
If you try to start the Internet Agent on a server where The X Window System and OpenMotif are not running, you receive the following error:
libXm.so.3: cannot open shared object file
: no such file or directory
To resolve the error, start The X Window System and OpenMotif before starting the Internet Agent with the --show switch. If you start the Internet Agent without the --show switch, you can use the Internet Agent Web console to monitor the Internet Agent from your Web browser.
In GroupWise 6 and its Support Packs, there was a problem with the address format used for sending to distribution lists and resources if you set Internet Addressing to one of the following formats (which are not appropriate for distribution lists and resources):
Messages to distribution lists and resources were initially undeliverable and were sent to the Internet Agent. The Internet Agent then successfully resolved the addresses and sent the messages back into the GroupWise system. Users did not notice the problem, but some administrators noticed unnecessary traffic through the Internet Agent.
In GroupWise 6.5 and GroupWise 6.5 for Linux, the address format problem for sending to distribution lists and resources was corrected. However, users who originally used GroupWise 6 have the erroneous address format for distribution lists and resources in their Frequent Contacts address books. If unnecessary traffic through the Internet Agent is a continuing problem, have users delete distribution lists and resources from their Frequent Contacts address books so that the correct address format is used for name completion in the future.
GroupWise 6.5 for Linux includes a Novell distribution of Apache and Tomcat that you can install along with the WebAccess Application if you do not already have Apache and Tomcat running on that server. The Novell distribution is installed in the following directories:
Apache: /var/opt/novell/http and /etc/opt/novell/http
Tomcat: /var/opt/novell/tomcat4 and /etc/opt/novell/tomcat4
and is started using the following customized commands:
Tomcat: /etc/init.d/novell-tomcat4 start
Apache: /etc/init.d/novell-httpd start
The WebAccess Installation program lets you choose whether you want to install the Novell distribution. During installation, select Install WebAccess Application with Apache and Tomcat if you want to install the Novell distribution. Select Install WebAccess Application if you do not want to install the Novell distribution of Apache and Tomcat because you have an existing Apache and Tomcat installation that you want to use with WebAccess.
If you install the Novell distribution on a server where a standard distribution of Apache and Tomcat is already installed and running, you will encounter a port conflict on port 80. You can resolve the port conflict by choosing to run one distribution or the other, or you can reconfigure one distribution or the other.
To reconfigure the Novell distribution to use a different port number, edit the httpd.conf file in the /etc/opt/novell/httpd/conf directory. Locate the following line:
Listen 80
Change the port number to a something that is not already being used on the server, then save and exit the file.
On slower machines, if you select Install WebAccess Application with Apache and Tomcat, your machine might appear to hang on the "Please Wait" message. Apache and Tomcat are being installed while the "Please Wait" message is displayed, before the WebAccess Application installation begins.
During installation, the WebAccess Installation program requires access to Novell® eDirectoryTM by way of LDAP authentication. The LDAP Group object includes an option named Require TLS for Simple Binds with Password, which is enabled by default. With this option enabled, you must provide the LDAP server's Trusted Root Certificate, which must be exported from the LDAP server, in order for LDAP authentication to take place (typically on port 636) during installation of the WebAccess.
Unless you already have SSL set up, an easier alternative is to disable Require TLS for Simple Binds with Passwords in ConsoleOne, which allows LDAP authentication to take place using clear text (typically on port 389), during installation of WebAccess. After disabling the option, restart eDirectory, install WebAccess, then re-enable Require TLS for Simple Binds with Password and restart eDirectory again.
If you install WebAccess in an eDirectory context where the WebAccess objects already exist, a message informs you that you can "use the existing objects." In actuality, the objects are deleted and re-created, so if you have customized the properties of the existing objects, you must customize the objects again after installing WebAccess.
On Red Hat Enterprise Linux 3 and Red Hat Advanced Server 3, starting the WebAccess Agent might result in a "floating point exception" error. If this occurs, you must enter the following prior to starting the WebAccess Agent:
export LD_ASSUME_KERNEL=2.4.0
If you start the WebAccess Agent using the grpwise-wa startup script in /etc/init.d, this error does not occur because the script sets the LD_ASSUME_KERNEL environment variable for you.
After you have updated the WebAccess and WebPublisher Applications to GroupWise 6.5 for Linux Support Pack 2, the GroupWise version number on the login page and under Help > About still displays 6.5.1. To correct the version number:
In a text editor, open the following configuration files:
/opt/novell/groupwise/webaccess/webacc.cfg
/opt/novell/groupwise/webpublisher/webpub.cfg
Change the setting for Application.Display.version from 6.5.1 to 6.5 to reflect the major version number on the login page.
Change the setting for Application.Module.version from 6.5.1 to 6.5.2 to reflect the Support Pack release number under Help > About.
Save and exit each configuration file.
Restart Tomcat to put the version changes into effect.
Existing users of the WebAccess are accustomed to accessing the following URLs:
Web Services page: Default index.html file of the Web server
WebAccess: http://web_server_address/servlet/webacc
WebPublisher: http://web_server_address/servlet/webpub
On Linux, use the following URLs:
GroupWise-specific Web Services page: http://web_server_address/gw/index.html
WebAccess: http://web_server_address/gw/webacc
WebPublisher: http://web_server_address/gw/webpub
As an added benefit, GroupWise 6.5 for Linux configures SSL for you, so that the following URLs provide SSL security without additional configuration on your part:
GroupWise-specific Web Services page: https://web_server_address/gw/index.html
WebAccess: https://web_server_address/gw/webacc
WebPublisher: https://web_server_address/gw/webpub
The first time you use the WebAccess spell checker, it downloads a speller plug-in. If Mozilla 1.6 is not configured correctly, you are repeatedly prompted to download the plug-in but the download never succeeds. The following URL might be of assistance in configuring Mozilla 1.6 so that the plug-in can be downloaded successfully:
http://www.mozilla.org/releases/mozilla1.6/installation-extras.html#extras_java
The WebAccess Installation program does not configure WebPublisher for you. Some manual configuration is required. For instructions, see the GroupWise 6.5 Installation Guide (/docs/us/GroupWiseInstallationGuide.pdf).
Changes to the settings on the Templates page of the GroupWiseWebPublisher object in ConsoleOne are not saved to the webpub.cfg file. To work around this, after making changes on the Templates page, select a different property page on the GroupWiseWebPublisher object, then click OK or Apply to save the template settings correctly.
If the WebAccess login page appears in one or more of the frames (for example, the Folder list or the Item list) after a WebAccess user has successfully logged in, the user is probably accessing WebAccess through one or more proxy servers.
To prevent this problem:
In ConsoleOne, right-click the WebAccess Application object (GroupWiseWebAccess), then click Properties.
On the Security page (located on the Application tab), deselect the Use Client IP in Securing Sessions option.
For information about this option, click Help on the Environment page.
Click OK to save the change.
If you are using the Tomcat servlet engine with GroupWise WebAccess, the maximum memory allocation (heap size) for Tomcat should be at least 128 MB. The maximum memory allocation is set by using the -Xmx parameter when starting Tomcat (for example, -Xmx128m).
Monitor and WebAccess share a substantial amount of functionality. The following WebAccess issues pertain to Monitor as well:
2.5.1 Novell Distribution of Apache and Tomcat
2.5.2 Prolonged "Please Wait" Message during Installation
2.5.3 Installation Security
2.5.4 Re-installation Issue
2.5.5 Floating Point Exception Error
2.5.6 Version Number Update
If you've used Monitor on Windows, you are used accustomed to accessing the following URLs:
Web Services page: Default index.html file of Web server
Monitor Web Console: http://web_server_address/servlet/gwmonitor
On Linux, use the following URLs:
GroupWise-specific Web Services page: http://web_server_address/gw/index.html
Monitor Web Console: http://web_server_address/gwmon/gwmonitor
If you encounter problems starting the Monitor Agent on Red Hat 3 AS, set the LC_ALL environment variable using one of the following commands:
export LC_ALL=C
export LC_ALL=POSIX
Monitor settings are stored in the monitor.xml file in the Monitor installation directory. If you reinstall the Monitor software, the monitor.xml file is backed up as monitor.001. To restore previous Monitor settings, remove the newly installed monitor.xml file and rename monitor.001 to monitor.xml.
Do not use extended characters in pathnames for domains, post offices, libraries, software distribution directories, and so on. Do not use extended characters in filenames such as agent startup files.
If you are using the WebAccess client in the Konqueror browser, you cannot attach files that have names including accented characters. Konqueror does not send the filenames back in UTF-8 format.
Do not use double-byte characters in directory names and filenames.
Do not use double-byte characters in users' passwords.
The Change GroupWise Password dialog box in ConsoleOne currently allows entry of double-byte characters. However, the GroupWise client login does not allow entry of double-byte characters in passwords, so a user who was assigned a password with double-byte characters in ConsoleOne cannot type the double-byte characters when attempting to log in to GroupWise.
When you use a Russian keyboard, the Linux environment variables that provide language and locale information are typically set to ru_RU. Typically, this setting implies the Russian character set ISO-8859-5. However, on some distributions of Linux, the ISO-8859-5 character set must be set explicitly in order for your Russian keyboard to work with the GroupWise Cross-Platform client. Use the following command to specify the character set along with the language and locale information:
export LANG=ru_RU.ISO-8859-5
In most cases, setting the LANG environment variable also sets all LC_* environment variables and resolves all Russian keyboard problems. If you set the LANG environment variable and your Russian keyboard still does not work, use the following command to view the current settings for the LANG and LC_* environment variables:
locale
If any of the LC_* environment variables have not inherited the ISO-8859-5 specification, export them individually.
Keyboard mnemonics for menu items work for characters a-z and A-Z, but not for other characters.
The Linux GroupWise agent user interfaces display correctly if the Linux environment is using the ISO-8859-1 character set, which is the default for the GroupWise administration languages and locales.
French: fr_FR
German: de_DE
Portuguese: pt_BR
Spanish: es_ES
If the Linux environment is using a different character set encoding such as UTF-8 (for example, fr_FR.UTF-8), the localized agent user interfaces do not display correctly.
Unicode* support using UTF-8 encoding has been implemented in WebAccess to provide better support for international character sets. Unicode support enables users to intermix characters within the same message and have all character sets display correctly.
For Support Pack 2, Unicode support is not fully implemented for double-byte character set languages (DBCS languages). In order to correctly compose in a DBCS language, users need to set their browser accept language to the desired DBCS language. Also in Support Pack 2, intermixing two different DBCS languages is not supported. These limitations will be removed in the next version of WebAccess.
If you will update to Support Pack 2 in stages, update the WebAccess Agent first throughout your system, then update the WebAccess Application. If the update to Unicode support causes undesirable side effects for your particular language or combination of languages, you can turn it off using the /utf8off startup switch with the WebAccess Agent. Then comment out the Charset.default setting in the webacc.cfg and webpub.cfg files. This procedure will not be necessary after Unicode support is fully supported for DBCS languages.
Auto-detection of character encoding for the WebAccess/WebPublisher index.html page does not work for some Web browsers. If you do not see the localized languages in the drop-down menu on the Web services page (index.html), set your browser's character encoding to UTF-8 (for example, click View > Encoding).
You might also encounter character encoding problems when reading HTML-formatted messages. In this case, set your browser's character encoding for the new message window to UTF-8. You can do this by right-clicking in the message and then setting the encoding or using View > Encoding.
Languages that display right-to-left display right-justified rather than left-justified.
The link from the ConsoleOne help to the Novell GroupWise documentation Web site does not work. This problem will be addressed in a future version of ConsoleOne. In the meantime, you can copy the URL from the ConsoleOne help topic into your browser window in order to access the GroupWise documentation Web site.
If you display help from an agent Web console on a server where Novell iChain® is installed, and if iChain is configured to use the Path-Based Multihoming option, the image at the top of the help topic does not display.
For information on the latest Support Pack issues, see the Consolidated Support Pack Readme Addendum, where issues for GroupWise 6.5 for Linux Support Pack 2 are available along with issues for GroupWise 6.5 Support Pack 2.
For detailed installation and update instructions, see the GroupWise 6.5 Installation Guide at the Novell Documentation Web site. It has been updated to correspond with GroupWise 6.5 for Linux Support Pack 2.
For additional GroupWise 6.5 documentation, see the GroupWise 6.5 Administration Guide at the Novell Documentation Web site. It has been updated to correspond with GroupWise 6.5 for Linux Support Pack 2.
For Readme information about specific GroupWise 6.5 components, see the following additional Readme files that shipped with the original release of GroupWise 6.5:
Administration: \admin\readmeus.txt
Agents: \agents\readmeus.txt
Client: \client\win32\readmeus.txt
WebAccess: \internet\webaccess\readmeus.txt
Internet Agent:\internet\gwia\readmeus.txt
Monitor: \admin\monitor\readmeus.txt
These Readme files do not contain Support Pack information.
In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.
You may not use, export or re-export this product in violation of any applicable laws or regulations including, without limitation, U.S. export regulations or the laws of the country in which you reside.
U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; 5,963,938; 6,081,804; 6,138,170; 6,167,393; 6,192,405; 6,216,123; 6,546,433; 6,584,458; D393,457; and Patents Pending.
Copyright © 2004 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.
GroupWise and Novell are registered trademarks of Novell, Inc. in the United States and other countries.
All third-party trademarks are the property of their respective owners.